Skip to content

Commit

Permalink
Fix access to separate OTLP signal statuses
Browse files Browse the repository at this point in the history
  • Loading branch information
chalin committed Nov 21, 2024
1 parent f1885df commit 3e3b200
Showing 1 changed file with 17 additions and 7 deletions.
24 changes: 17 additions & 7 deletions content/en/docs/specs/status.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,11 +54,12 @@ support for specific features can be found in the
Note that, for each of the following sections, the **Collector** status is the
same as the **Protocol** status.

### [Tracing][]
### Tracing

- [Specification][tracing]
- {{% spec_status "API" "otel/trace/api" "Status" %}}
- {{% spec_status "SDK" "otel/trace/sdk" "Status" %}}
- {{% spec_status "Protocol" "otlp" "Status" %}}
- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*trace" %}}
- Notes:
- The tracing specification is now completely stable, and covered by long term
support.
Expand All @@ -67,20 +68,22 @@ same as the **Protocol** status.
- OpenTelemetry clients are versioned to v1.0 once their tracing
implementation is complete.

### [Metrics][]
### Metrics

- [Specification][metrics]
- {{% spec_status "API" "otel/metrics/api" "Status" %}}
- {{% spec_status "SDK" "otel/metrics/sdk" "Status" %}}
- {{% spec_status "Protocol" "otlp" "Status" %}}
- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*metric" %}}
- Notes:
- OpenTelemetry Metrics is currently under active development.
- The data model is stable and released as part of the OTLP protocol.
- Experimental support for metric pipelines is available in the Collector.
- Collector support for Prometheus is under development, in collaboration with
the Prometheus community.

### [Baggage][]
### Baggage

- [Specification][baggage]
- {{% spec_status "API" "otel/baggage/api" "Status" %}}
- **SDK:** stable
- **Protocol:** N/A
Expand All @@ -90,12 +93,13 @@ same as the **Protocol** status.
keys and values to a transaction, so that downstream services may access
them. As such, there is no OTLP or Collector component to baggage.

### [Logging][]
### Logging

- [Specification][logging]
- {{% spec_status "Bridge API" "otel/logs/api" "Status" %}}
- {{% spec_status "SDK" "otel/logs/sdk" "Status" %}}
- {{% spec_status "Event API" "otel/logs/event-api" "Status" %}}
- {{% spec_status "Protocol" "otlp" "Status" %}}
- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*log" %}}
- Notes:
- The [logs data model][] is released as part of the OpenTelemetry Protocol.
- Log processing for many data formats has been added to the Collector, thanks
Expand All @@ -112,9 +116,15 @@ same as the **Protocol** status.
the Event API is intended to be called by end users. The Event API is under
active development.

### Profiles

- [Specification][profiles]
- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*profiles" %}}

[baggage]: /docs/specs/otel/baggage/
[event semantic conventions]: /docs/specs/semconv/general/events/
[logging]: /docs/specs/otel/logs/
[logs data model]: /docs/specs/otel/logs/data-model/
[metrics]: /docs/specs/otel/metrics/
[profiles]: /docs/specs/otel/profiles/
[tracing]: /docs/specs/otel/trace/

0 comments on commit 3e3b200

Please sign in to comment.