You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance observability documentation by adding detailed information on OpenTelemetry destinations, including common OTLP endpoint formats for various providers. Update Grafana Cloud setup instructions for clarity and include a new section on known limitations regarding metrics export and OTLP support. Additionally, refine the spans and attributes section to indicate that names may change during the beta period, ensuring users are informed of potential updates.
Copy file name to clipboardExpand all lines: src/content/docs/workers/observability/exporting-opentelemetry-data/grafana-cloud.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,13 +29,15 @@ Before you begin, ensure you have:
29
29
4. Select **Quickstart** then select **JavaScript**
30
30
6. Click **Create a new token**
31
31
7. Enter a name for your token (e.g., `cloudflare-workers-otel`) and click **create token**
32
+
8. Click on **Close** without copying the token
33
+
9. Copy and Save the value for `OTEL_EXPORTER_OTLP_ENDPOINT` and `OTEL_EXPORTER_OTLP_HEADERS` in the `Environment variables` code block as the OTel endpoint and as the Auth header value respectively
32
34
33
35
34
36
## Step 2: Set up destination
35
37
1. Navigate to your Cloudflare account's [Workers Observability](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/pipelines) section
36
38
2. Click **Add destination** and configure a destination name (e.g. `grafana-tracing`)
37
39
3. From Grafana, copy your Otel endpoint, auth header, and auth value
38
-
* Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces for tracing and `/v1/logs` for logs)
40
+
* Your OTEL endpoint will look like `https://otlp-gateway-prod-us-east-2.grafana.net/otlp` (append `/v1/traces` for traces and `/v1/logs` for logs)
Below are common OTLP endpoint formats for popular observability providers. Refer to your provider's documentation for specific details and authentication requirements.
|**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.
38
+
39
+
:::note[Authentication]
40
+
Most providers require authentication headers. Refer to your provider's documentation for specific authentication requirements.
41
+
:::
24
42
25
43
## Setting up OpenTelemetry-compatible destinations
26
44
To start sending data to your destination, you'll need to create a destination in the Cloudflare dashboard.
@@ -91,3 +109,7 @@ This includes the following limits and pricing:
91
109
|**Workers Free**| Not available | Not available | - |
92
110
|**Workers Paid**| 10 million events per month included | 10 million events per month included | $0.05 per million additional events |
93
111
112
+
## Known limitations
113
+
OpenTelemetry data export is currently in beta. Please be aware of the following limitations:
114
+
-**Metrics export not yet supported**: Exporting Worker infrastructure metrics and custom metrics via OpenTelemetry is not currently available. We are actively working to add metrics support in the future.
115
+
-**Limited OTLP support from some providers**: Some observability providers are still rolling out OTLP endpoint support. Check the [Available OpenTelemetry destinations](#available-opentelemetry-destinations) table above for current availability.
Copy file name to clipboardExpand all lines: src/content/docs/workers/observability/traces/known-limitations.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,4 +20,7 @@ We are adding more automatic instrumentation for every part of the Workers platf
20
20
### Support for custom spans and attributes:
21
21
While automatic instrumentation covers the platform interactions, we know you need visibility into your own application logic too. We're working to support the [OpenTelemetry API](https://www.npmjs.com/package/@opentelemetry/api) to make it easier for you to instrument custom spans within your application.
22
22
23
+
### Span and attribute names subject to change
24
+
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.
0 commit comments