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
Update observability documentation to enhance clarity on OpenTelemetry data export links and improve the descriptions of spans and attributes. This includes correcting links for exporting OpenTelemetry data, refining the section on missing instrumentation, and updating references to the Durable Object Storage SQL and KV APIs for better user guidance.
Copy file name to clipboardExpand all lines: src/content/docs/workers/observability/traces/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ Or if you have already set `observability.enabled = true` in your wrangler confi
53
53
Workers tracing follows [OpenTelemetry (OTel) standards](https://opentelemetry.io/), making it compatible with popular observability platforms while requiring zero development effort from you.
54
54
If your observability provider has an available OpenTelemetry endpoint, you can export traces (and logs!)
55
55
56
-
Learn more about exporting OpenTelemetry data from Workers to your provider of choice [here](workers/observability/exporting-opentelemetry-data/index.mdx).
56
+
Learn more about exporting OpenTelemetry data from Workers to your provider of choice [here](workers/observability/exporting-opentelemetry-data/).
Copy file name to clipboardExpand all lines: src/content/docs/workers/observability/traces/known-limitations.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,8 @@ One of the key aspects of distributed tracing is ensuring trace context flows ac
14
14
15
15
Without trace context propagation, you will also see an additional trace whenever your Worker is making a call to another Worker via service bindings or to a Durable Object.
16
16
17
-
### Support for more spans and attributes
18
-
We are adding more automatic instrumentation for every part of the Workers platform. While we first want to give you visibility into the duration of every operation within your request, we also planning to add more detailed attributes on each span. You can find a complete list of what is already instrumented [here](link). Your [feedback](link) on what’s missing will help us prioritize accordingly.
17
+
### Missing instrumentation for some spans and attributes
18
+
We are adding more automatic instrumentation for every part of the Workers platform. While we first want to give you visibility into the duration of every operation within your request, we also planning to add more detailed attributes on each span. You can find a complete list of what is already instrumented [here](/workers/observability/traces/spans-and-attributes). Your feedback on what’s missing will help us prioritize accordingly.
19
19
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.
0 commit comments