Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

Bug description

When the backend API responds with 500 error code then the loader on charts section loads infinitely

Expected behavior

Charts should show No Data like in trace table.

Version information

I think I've had about a 10% success rate with markdownlint since it seems to get throttled by GitHub. I've heard this was an issue that should have improved, but it doesn't seem to have been and I can't find any context for that in this repo.

Perhaps switching markdownlint to a GitHub Action would work around the throttling "for free" (actions automatically have GitHub creds for the repo). Jus

Describe the bug
During the lifetime of my application, everything is working properly.
Once I closed it, I have a "warning" in the collector:

warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:4317->[::1]:64933: wsarecv: Une connexion existante a dû être fermée par l’hôte distant. {"grpc_log": true}

"Une co

Bug Report

If you use the B3 propagator with e.g. the Grpc.Core instrumentation then it fails to connect the parent spans to the new server spans because gRPC headers are always lower case.

The issue is that the B3 propagator does not store the headers as lower case and then this line in the Grpc.Core instrumentation does not do case-insensitive comparison: https://github.com/open-telemetry/

In the doc page https://opentelemetry.io/docs/java/manual_instrumentation/, it would be nice if a layer could be added, using the latests dependencies, bom and inner project dependencies(api, sdk, and opentelemetry-exporters-otlp) to use the provided code.

It would be nice if the sample could provide the gradle/maven, etc. dependencies as a block to copy/paste int the https://opentelemetry.io/

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

Intake API

Extend transaction Intake API to accept transaction.dropped_spans_stats.service_target_type and transaction.dropped_spans_stats.service_target_name.

Aggregated Metrics Calculation

Extend transaction.DroppedSpanStats to contain the service_target_* fields. For calculating related span m

The opentelemetry-api package, exporting opentelemetry doesn't successfully import into vscode.

1. In vanilla VSCode, the import opentelemetry is white

2. In VSCode with mypy / pylance enabled with strict mode:
   <img width="383" alt="image" src="https

See #9782

See the spec change for details open-telemetry/opentelemetry-specification#1269

每Pipeline实现多Sink存在的问题在于：
1 多Sink时，如何解决单个Sink写下游失败时的重试的问题？
2 多Sink时，如何解决不同Sink的不同拦截器配置的问题？业务侧可能会想要不同Sink下游的数据中有不同的Intercepter配置呢？

从代码看已经实现了 sink.Interceptor可以与Sink关联 这个特性。
是否借助这个特性其实就可以解决以上两个问题了？

问题1 的解法
retry interceptor 与特定的Sink关联，这样就可以在不同的Sink间做独立的重试。
此时比如2个Sink其中有一个的下游阻塞了，则重试行为是同一个pipeline的不同sink应该都阻塞。
Roadmap计划是做成这个效果吗？

问题2的解法
为不同的Sink指定不同的拦截器，这样就可以解决不同数据下游需要不同处理

Hello,

I am trying to deploy opentelemetry-operator in GKE Autopilot (v1.21) and I am finding a weird behavior when I create a collector, the control-plane operator seems to start to create new replicaSets out of control.

1. First I installed the latest cert-manager
2. Enable firewall in GKE
3. Installed the latest release of opentelemetry-operator
4. Created a collector.

I noticed t

The method formatStackTrace should be moved from Span into a dedicated Util/Formatter class in the SDK\Common namespace since formatting stack traces is not the responsibility of a Span.

• Move logic in formatStackTrace from Span into a dedicated Util/Formatter class
• Add Backward compatib

Use Case

• Provide a sample application to test DBs, messaging systems and HTTP, GRPC backend resolution and call view.

Proposal

• A simple app where backend can be swapped or we can use multiple backends.

There are many places to add tests with ”gtest_add_tests“, But gtest_add_tests is a new feature of Cmake 3.9 version, When I try to compile with 3.8.5, it doesn't compile the test code anyway, this confused me for a while.

We have a sprinkling of otel.foo kinds of tags being used throughout the codebase:

opentelemetry-ruby on  ahayworth/add-dropped-counts-zipkin-jaeger via 💎 v3.1.1
zsh ❯ git grep 'otel\.' | egrep -v '\/test\/'
exporter/jaeger/lib/opentelemetry/exporter/jaeger/encoder.rb:          tags << encoded_tag('otel.dropped_attributes_count', dropped_attributes_count) if dropped_attributes_count.p

Currently (as of 0.7.0) NEOS tutorial that is opening up next to Cloud Shell window has 9 pages. 6 of them look similar but shorter versions of what's available in the user guide.
We want to shorten the NEOS tutorial and move details into the user guide. (Hugo static website under /website folder)

During the release process the script bump-version-and-create-release-note is used to generate a new version doc which release notes are generated from. Currently this generates notes for ALL closed issues including stale ones and closed PRs. An audit should be done on how t

This line does not work for me in Powershell:
./bin/otelcorecol_* --config ./examples/local/otel-config.yaml

Error message: "./bin/otelcorecol_* : The term './bin/otelcorecol_*' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

• .