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

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

confighttp.HTTPClientSettings.ToClient takes an id-extension map while configgrpc.HTTPServerSettings.ToServer and all the configrpc.*.To* methods take a component.Host, in all cases to support authentication.

Ideally all would be consistent by passing component.Host to all of them, although I don't want to assume this is the best solution just because it's the most used one.

cc @j

Today our AspNetCore metrics instrumentation captures a small subset...

https://github.com/open-telemetry/opentelemetry-dotnet/blob/96b043e35fcf407147a9ad9c4fae2b6915f3a9ab/src/OpenTelemetry.Instrumentation.AspNetCore/Implementation/HttpInMetricsListener.cs#L58-L61

...of the attributes defined in the [spec semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/bl

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/

As we're adding support for OpenTelemetry API bridges, it would be useful to know how much they're being used so we know whether to prioritize additional features in the bridge spec.

We can use otel.span_kind for this telemetry. All spans from the otel bridges should have otel.span_kind set. The APM Server is inferring this field for non-otel spans

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)

Schema should be defined as part of resource in metadata.yaml. The filed should be required

resource:
  schema: v1.8.0

Doing that make wrapBySchemaURLSetterConsumer function redundant.

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

看到输入支持文件，输出利用sink和pipeline可以灵活定制 ，还能限流 ，是否能充当一个pod to pod的文件传输工具？

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.

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

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

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:

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.

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

The current Getting Started guide includes a demo that use Zipkin, Jaeger and Prometheus. I am looking for a more simpler guide. Something that would show how to send a metric(s) using a utility like CURL and seeing the metric being recorded in a local file. This would help confirm that the installation of OTEL Collector is working normally.