opentelemetry-rust
opentelemetry-rust copied to clipboard
open-telemetry
The Rust OpenTelemetry implementation
Currently, the `Key` values in the semantic conventions crate cannot be used as conditions inside of a match expression because the inner `Cow` does not derive PartialEq and Eq. While...
The example program external-otlp-tonic-tokio fails under Windows OS. Error at console is: `OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error Unknown error` I...
Many of the newcomers and possible contributors to Opentelemetry are often looking first into the community repository to get a sense about the structure of the project and the "vibe"...
I'm trying to use the `opentelemetry-otlp` crate together with `tracing`, and I'm wondering how the `with_endpoint` part of the builder works. This is how I'm initializing the tracer: ``` let...
See the spec change for details https://github.com/open-telemetry/opentelemetry-specification/pull/748
See the spec change for details https://github.com/open-telemetry/opentelemetry-specification/pull/1269
Follow up on the discussion from #451, we should decide the name convention of environment variable constants
Should this be added to `opentelemetry` or `opentelemetry-contrib`? Unless anyone else wants to implement this, I will do it. Go implementation for opencensus: https://github.com/census-instrumentation/opencensus-go/blob/v0.22.5/exporter/stackdriver/propagation/http.go
Currently it is tedious to manually run fmt, test, clippy, etc when developing locally. Consider adding another script to ./scripts that runs all and update contributing docs.
See the spec change for details https://github.com/open-telemetry/opentelemetry-specification/pull/890