Skip to content

Commit 1c55146

Browse files
committed
Refine OpenTelemetry documentation by updating common OTLP endpoint formats for Grafana Cloud, Axiom, Datadog, and Sentry. Enhance the known limitations section with additional details on metadata applicability across spans and logs, ensuring users are better informed about current bugs and trace visibility.
1 parent 63bb181 commit 1c55146

File tree

2 files changed

+7
-12
lines changed

2 files changed

+7
-12
lines changed

src/content/docs/workers/observability/exporting-opentelemetry-data/index.mdx

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -25,16 +25,10 @@ Below are common OTLP endpoint formats for popular observability providers. Refe
2525
| Provider | Traces Endpoint | Logs Endpoint |
2626
|----------|----------------|---------------|
2727
| [**Honeycomb**](/workers/observability/exporting-opentelemetry-data/honeycomb/) | `https://api.honeycomb.io/v1/traces` | `https://api.honeycomb.io/v1/logs` |
28-
| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/) | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`[^1] | `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
29-
| **Axiom** | `https://api.axiom.co/v1/traces` | `https://api.axiom.co/v1/logs` |
30-
| **Datadog** | Not yet available. Pending release from Datadog[^2] | Not yet available. Pending release from Datadog[^2] |
31-
| **Sentry** | Not yet available. Pending release from Sentry[^3] | Not yet available. Pending release from Sentry[^3] |
32-
33-
[^1]: Replace `{region}` with your Grafana Cloud stack region (e.g., `prod-us-east-0`)
34-
35-
[^2]: Datadog's OTLP endpoints are currently being rolled out and may not be available for all accounts. Contact Datadog support to enable OTLP ingestion for your account.
36-
37-
[^3]: Sentry's OTLP endpoints are currently being rolled out and may not be available for all accounts. Contact Sentry support to enable OTLP ingestion for your account.
28+
| [**Grafana Cloud**](/workers/observability/exporting-opentelemetry-data/grafana-cloud/) | `https://otlp-gateway-{region}.grafana.net/otlp/v1/traces`| `https://otlp-gateway-{region}.grafana.net/otlp/v1/logs`[^1] |
29+
| [**Axiom**](/workers/observability/exporting-opentelemetry-data/axiom/) | `https://api.axiom.co/v1/traces` | `https://api.axiom.co/v1/logs` |
30+
| **Datadog** | Not yet available. Pending release from Datadog | Not yet available. Pending release from Datadog |
31+
| **Sentry** | Not yet available. Pending release from Sentry | Not yet available. Pending release from Sentry |
3832

3933
:::note[Authentication]
4034
Most providers require authentication headers. Refer to your provider's documentation for specific authentication requirements.

src/content/docs/workers/observability/traces/known-limitations.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,5 +23,6 @@ While automatic instrumentation covers the platform interactions, we know you ne
2323
### Span and attribute names subject to change
2424
As Workers tracing is currently in beta, span names and attribute names are not yet finalized. We may refine these names during the beta period to improve clarity and align with OpenTelemetry semantic conventions. We recommend reviewing the [spans and attributes documentation](/workers/observability/traces/spans-and-attributes) periodically for updates.
2525

26-
### Call outs
27-
*
26+
### Known bugs and other call outs
27+
* There are currently are a few pieces of metadata that only apply to spans (e.g.`service.name`, `faas.name`), however, some may apply across all events. For example, when filtering/grouping on the Worker name across traces and logs, use `$metadata.service` as it will apply consistently across all event types.
28+
* While a trace is in progress, the event will show `Trace in Progress` on the root span. Please wait a few moments for the full trace to become available

0 commit comments

Comments
 (0)