Trask Stalnaker
Trask Stalnaker
[The spec says](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/README.md#attribute): > For protocols that do not natively support non-string values, non-string values SHOULD be represented as JSON-encoded strings. but it looks like the Prometheus exporter calls only...
See discussion in https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/9000
Currently, the logging spec's [Trace Context in Legacy Formats]( https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/README.md#trace-context-in-legacy-formats) says: > the following field names should be used in legacy formats: > > "trace_id" for [TraceId](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#field-traceid), hex-encoded. "span_id" for...
**What are you trying to achieve?** Stability of [Instrument advisory parameter: Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md#instrument-advisory-parameter-attributes) **Additional context.** Java Instrumentation is relying heavily on this feature, e.g. emitting HTTP span attributes on HTTP metrics...
### Description Get the HTTP semantic conventions across the finish line to stability, and afterwards update existing HTTP instrumentation across all OpenTelemetry repositories to conform with the stable conventions. ###...
TODO need to manually test old actuator instrumentation, because I haven't been able to get old spring boot versions to work since [upgrading to Gradle 8.1.1](#3046). Resolves #2806 and https://portal.microsofticm.com/imp/v3/incidents/incident/409304026...
cc @lmolkova moved to draft to reconsider approach. there's also `db.cassandra.*`, `db.redis.*`, etc