Zhongyang Wu
Zhongyang Wu
As point out in #155. It would be nice to have some control on the order of the output field. Add example on how to custom field's order.
Backport dashmap change in #818 to v0.17.0
Out of all [available formats](https://www.jaegertracing.io/docs/1./apis/#protobuf-via-grpc-stable) in Jaeger the _protobuf over grpc_ support is missing. This format is generally used by agents to send spans to collectors and should probably be...
Add support for all configurations in [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md#opentelemetry-protocol-exporter) - [ ] Endpoint (OTLP/HTTP) - It was partially supported with #773 missing - [x] Endpoint (OTLP/gRPC) - [ ] Insecure - [...
The [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#onstart) noted that we should allow span processor to keep a reference to the span passed as the parameter of `on_start` method > It SHOULD be possible to keep...
Follow up on the discussion from #451, we should decide the name convention of environment variable constants
Hi, so we are have some discussion around how should the tracing context handle the situation where the debug is also a implicated sampled decision. We have a bitmask to...
### Affected Repository https://github.com/open-telemetry/opentelemetry-rust https://github.com/open-telemetry/opentelemetry-rust-contrib ### Requested changes - Grant `read:org` access to me for `cargo.io` OAuth applicaion ### Purpose Cargo is the Rust's package manager and we are trying...
In order to increase our confidence when releasing a new version. We should have integration tests for important exporters(OTLP, jager, etc). Currently we have limited integration test for jaeger, and...
Presently, an internal logging mechanism is in place that leverages eprintln! to alert users of errors within the Opentelemetry pipeline. Users have the option to customize this logging by introducing...