opentelemetry-rust
opentelemetry-rust copied to clipboard
open-telemetry
The Rust OpenTelemetry implementation
I'm regularly getting an error when sending traces: `OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (Unknown error): , detailed error message: transport...
Hey, I was wondering if it was possible to get a crate published for the `opentelemetry-proto`. We ([Vector](https://vector.dev)) are starting to add support for OpenTelemetry - both receiving and sending...
When I check the span in jeager I only get `process_orderbook_operation`, shouldn't it be `root` with a child `process_orderbook` then its child `process_orderbook_operation`. Also the span `process_orderbook_operation` have an warning...
I am using opentelemetry-jaeger 0.16.0 with tracing-opentelemetry 0.17.4 on Linux along with the latest Jaeger binary (non-docker) release. I did see the old tickets on this issue (#648 #676 and...
``` OpenTelemetry trace error occurred. cannot send span to the batch span processor because the channel is closed ``` Default and custom client both does not work. same error message...
While using the Go SDK I noticed an inconsistency in how `OTEL_RESOURCE_ATTRIBUTES` baggage values are encoded and decoded. This was due to a difference in the version of the W3C...
Backport dashmap change in #818 to v0.17.0
The Jaeger exporters all bind to INADDR_ANY ([opentelemetry-jaeger/src/exporter/runtime.rs](https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-jaeger/src/exporter/runtime.rs#L26)) which means that you are unable to connect to Jaeger agent collectors hosted on IPv6 address ranges, such as `[::1]:6831`. It would...
* Sampling should always defer to the existing sampler. The logic before this patch reflected something similar to what is described in the ParentBased sampler. Relates #800
