search

open-telemetry / oteps

OpenTelemetry Enhancement Proposals
https://opentelemetry.io
Apache License 2.0
337 stars 164 forks source link

Define Mapping of Arbitrary Data to OTLP AnyValue #178

Closed tigrannajaryan closed 2 years ago

tigrannajaryan commented 3 years ago

The mapping is necessary to correctly implement Logging Library SDKs such that values mapped are unambiguous, consistent across languages and implementations.

tigrannajaryan commented 3 years ago

@jkwatson @zenmoto PTAL.

tigrannajaryan commented 3 years ago

@open-telemetry/specs-approvers Please review. This is needed by Logging SDK for now but there is no reason this cannot be extended to Span, Resource or SpanEvent attributes in the future if we decide so. It is best that we make it future-proof and ensure it is reasonable for all signals (even if we don't need it now).

tigrannajaryan commented 2 years ago

@open-telemetry/specs-approvers Please review.

tigrannajaryan commented 2 years ago

@open-telemetry/specs-logs-approvers please review.

tigrannajaryan commented 2 years ago

Lint failures will be fixed by https://github.com/open-telemetry/oteps/pull/196 which needs to be merged before this PR.

tigrannajaryan commented 2 years ago

@open-telemetry/specs-approvers please review.

tigrannajaryan commented 2 years ago

@open-telemetry/specs-trace-approvers please review.

tigrannajaryan commented 2 years ago

@zenmoto please review.

tigrannajaryan commented 2 years ago

@open-telemetry/specs-metrics-approvers please review.

tigrannajaryan commented 2 years ago

@open-telemetry/specs-approvers last chance to review/comment/object before I merge this and start moving to the spec. This is going to apply to all signals.