open-telemetry / opentelemetry-proto

OpenTelemetry protocol (OTLP) specification and Protobuf definitions

https://opentelemetry.io/docs/specs/otlp/

open-telemetry/opentelemetry-proto Issues

Retryable HTTP Statuses should be configurable
Closed 4 months ago3
SPAN_FLAGS_TRACE_FLAGS_MASK is not defined
Closed 4 months ago3
Supporting JSON as-is encoding in OTLP
Updated 4 months ago2
Fail to push limit
Closed 5 months ago5
How to use Java service to receive data in the OpenTelemetry (Otel) protocol?
Closed 5 months ago4
Why TraceID and SpanID are defined []byte type?
Closed 5 months ago4
Improve metrics.proto by mentioning Resource Attributes and Scope
Updated 6 months ago1
Generated OpenAPI files wrongly encode enums
Updated 6 months ago
Allow consumers to use map<string, AnyValue> instead of repeated KeyValue
Updated 6 months ago3
Clarify meaning of *DNS name prefix* in protobuf code comment for metric name
Closed 7 months ago
Fix releasing notes
Updated 8 months ago3
Unclear whether Span.flags represents span's parent or own flags
Updated 9 months ago10
Clarify whether OTLP/gRPC codes should cover both client and server
Updated 9 months ago1
The comment of schema_url doesn't describe it's purpose.
Closed 10 months ago
optional keyword in sum field breaks build on Ubuntu 20.04
Closed 2 years ago10
AnyValue diverging from spec on website
Closed a year ago2
Add checks for markdown files as we have in the spec repo
Closed a year ago1
Difference between proto and SDK
Closed a year ago2
Mention 1.0.0 in CHANGELOG.md?
Closed a year ago3
Mark opentelemetry-proto repo 1.0
Closed a year ago17
Question about ResourceSpans
Closed a year ago1
Schema support for span with key-value attributes
Closed a year ago2
Conflicting requirements in OTLP JSON field names
Closed a year ago14
Enum element naming consistency
Closed a year ago1
Helper enums ZERO value is incorrectly used
Closed a year ago12
Move examples out of spec into an examples folder
Closed a year ago1
Add ability for OTLP to indicate which records were rejected for retryable reasons
Updated a year ago5
Add examples to OTLP/JSON
Closed a year ago7
Add version identification to the opentelemetry-proto tar archive
Updated a year ago1
Clarify in otlp.md that timestamps in JSON are also fixed64
Updated a year ago1
Decide Conditions on Symbolic Stability to Declare OTLP 1.0
Closed a year ago18
Just for maintainers information
Updated a year ago6
#![feature]` may not be used on the stable release channel
Closed a year ago2
metrics.proto will cause compilation errors when the protobuf version is less than 3.15.0
Closed a year ago
实现export方法时 traceid 字段编码无法直接解码
Closed a year ago1
Add optional `zero_threshold` to ExponentialHistogramDataPoint.
Closed a year ago
20-
Closed a year ago1
Inconsistent Span status field name: message in OTLP vs description in API
Closed 2 years ago12
Do we intend to support non-number values for Gauges?
Closed 2 years ago5
Does Gauge's value type has to be number data point?
Closed 2 years ago5
Clarify OTLP/JSON behavior when receiving unknown message fields (not enum fields)
Closed 2 years ago1
Do NOT guarantee string enum values backwards compatibility in JSON
Closed 2 years ago16
Removal of InstrumentationLibrary-related fields and messages violates "stable" maturity level
Closed 2 years ago3
LogRecord.flags name is unclear.
Closed 2 years ago1
OTLP metrics export partial success - structure, semantic conventions and beyond
Closed 2 years ago
Enable health-check in the proto
Closed 2 years ago2
Consider adding short keys for JSON encoding
Closed 2 years ago3
[Doc] Is TraceConfig still relevant?
Closed 2 years ago
[Doc] Number of root spans per trace
Closed 2 years ago4
Metrics proto didn't support back-compatibility when metric double value is 0.0 (v0.28->v0.31)
Closed 2 years ago12