Carlos Alberto Cortez
Carlos Alberto Cortez
Similarly to OTEL_SERVICE_NAME, I was wondering if we _could_ add this one as well (for context, we at Lightstep leverage this and currently have to use our own custom env...
Currently we have supplementary guidelines in a few places (namely, under each signal and also as a top level directory). Let's come with an actual guideline, one way or another....
Opening this issue to mainly get the ball rolling, as I have had users asking for metrics around processed/dropped/exported data (starting with traces, but following up with metrics/logs). I'd like...
The OT Shim layer needs to be updated to include the latest changes as introduced by https://github.com/open-telemetry/opentelemetry-specification/pull/1101 Making OpenTelemetry Python compatible with OpenTracing means implementing several things. As suggested by...
Define **human readable vs storage space** guidelines for semantic conventions. This came from open-telemetry/opentelemetry-specification#1495 regarding choosing between `availability_zone` (easier to read) and `zone` or `az` (optimizing storage space). We should...
Tracking issue for https://github.com/open-telemetry/oteps/pull/266 in order to *fully* complete the migration. - [x] Migrate OTEPs along with their history (#4288) - [x] Move issues from the OTEPs repository (to either...
Have SpanContext support the new [W3C random flag](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#traceid-randomness).
Have SpanContext support the new [W3C random flag](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#traceid-randomness).