OpenTelemetry

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

Header in Top Endpoint section overflows in browser with reduced width

Expected behavior

Header shouldn't overflow

How to reproduce

1. Go to SigNoz dashboard metrics page with reduced browser window width
2. Open any application
3. Top Endpoint panel header appears overflowing

Version information

• Signoz version: v0.7.1
• *Browser version

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

See the idea open-telemetry/opentelemetry-collector#4108 (comment)

It looks like a good amount of time is spent on nuget restore. And majority of them from the example projects, which are not required for all the build/test pipelines. We may benefit, if examples are built in a dedicated pipeline, and ignored by other pipelines.

We currently have AttributesBuilder.removeIf but no ResouceBuilder.removeIf. I think our intention was the latter to have equivalent functionality to the former as a shortcut, so this seems to be something we should add.

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

A followup to the discussion in #2321:

Based on the attribute specification, it looks like the list should just be converted to its JSON representation.

Originally posted by @codeboten in open-telemetry/opentelemetry-python#2321 (comment)

Describe the bug
If I have a tag http.status_code >=400 and a tag error=false on my Span, a tag error=true gets added (so I now have two attributes error with one true and one false) and the overall status of the span switches to error with a tag otel.status_code = ERROR
Short story: In my app, I don't want client errors to popup as span errors, I want that only for server errors, so I s

The TracerProvider::force_flush method is part of the sdk spec but not the api spec.

The SdkBundle documentation could use same be improvements in regards of the configuration.

• Show how to enable/disable the SDK or parts of it in different environements (dev, staging, prod, etc.)
• Show how to configure Resource Limits and Attributes.
• Show how to configure different Span Samplers, especially the ParentBased Sampler and how to reference custom Samplers.
• S

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

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)

Our Rack instrumentation allows configuration of a URL quantization function https://github.com/open-telemetry/opentelemetry-ruby/blob/1c37b00dc82d490dace1f92739977aa4674d7039/instrumentation/rack/lib/opentelemetry/instrumentation/rack/middlewares/tracer_middleware.rb#L122-L137

We should add the same functionality to the Sinatra instrumentation. @genebean reported this requirement in Gitter:

This would be eventually required for

• To support async interface between span/log processor and exporters.
• Async IO while exporting the spans.
• Timers to poll for Spans in BatchSpanProcessor, and metrics in PeriodicMetricReader.
• Asynchronously collect metrics for all the instruments across all the meters ( this would be a costly operation sequentially or even using threads).

Re

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.

Describe the bug
During the release process a release/v* and main branch are updated within a very close window. With the currently concurrency rules defined in CI.yml both CI workflows will run concurrently. Since both workflows utilize resources in the same integ-test account, such as the adot-op-cluster there can be collisions which causes jobs to fail. Rerunning the workflows afte