opentelemetry-specification
opentelemetry-specification copied to clipboard
Specifications for OpenTelemetry
Currently we define `scheduledDelayMillis`, `maxQueueSize`, and `maxExportBatchSize`. https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/sdk.md#batching-processor It's not clear to me whether `scheduledDelayMillis` is supposed to be time in between exports of chunks of size `maxExportBatchSize`, or if...
### Proposal I would like to propose that OTel defines a semantic convention for feature flagging. This will provide the ability to split traces and metrics by the attributes for...
https://github.com/open-telemetry/opentelemetry-specification/pull/2404 updated the requirements to construct a metric reader: > https://github.com/open-telemetry/opentelemetry-specification/blob/v1.12.0/specification/metrics/sdk.md#metricreader > > To construct a MetricReader when setting up an SDK, the caller SHOULD provide at least the following:...
We need to finally do some work to make OTLP http/json stable. From https://github.com/open-telemetry/opentelemetry-proto/issues/230#issuecomment-775307405 we need to: - [x] #2796 - [x] Agree to no longer use the deprecated delimiter...
The specification does not tell what happens when exporting to a format that is not capable of representing attributes separately for the Resource, for the Scope and for Span/Metric/LogRecord. The...
**What are you trying to achieve?** Set an attribute to all spans in a trace **What did you expect to see?** Writeable spans on SpanProcessor's OnEnd(Span) **Additional context.** What I...
**What are you trying to achieve?** I'm trying to adapt open telemetry to the Apache NiFi cluster through their UI. By giving users access to processors (start, stop, addattribute, addevent),...
_Originally posted by @tigrannajaryan in https://github.com/open-telemetry/opentelemetry-specification/issues/2479#issuecomment-1092923011_ >> every section will need a README. I'm available to help here: e.g., I submit a first PR that adds a README (with only...
A follow up to #1751 and #1130 (which we decided to go ahed with), as pointed out by @tigrannajaryan * Proliferation of environment variables, and whether this can end up...
With #2602 `net.app.protocol.name` and `net.app.protocol.version` would be a standard way to describe protocol and `http.flavor` can be removed. > `http.flavor` has the following list of well-known values. If one of...