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 known limitations and spans documentation for tracing
- Corrected links in the known limitations section to point to the appropriate security model documentation.
- Updated span and attribute references to reflect changes in the Durable Object Storage API, including renaming and correcting links for various methods.
Copy file name to clipboardExpand all lines: src/content/docs/workers/observability/traces/known-limitations.md
+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
@@ -13,7 +13,7 @@ To provide more feedback and send feature requests, head to the [Workers tracing
13
13
14
14
### Non-I/O operations may report time of 0 ms
15
15
16
-
Due to [security measures put in place to prevent Spectre attacks](workers/reference/security-model/#step-1-disallow-timers-and-multi-threading), the Workers
16
+
Due to [security measures put in place to prevent Spectre attacks](/workers/reference/security-model/#step-1-disallow-timers-and-multi-threading), the Workers
17
17
Runtime does not update time until I/O events take place. This means that some spans will return a length of `0 ms` even when the operation took longer.
18
18
19
19
The Cloudflare Workers team is exploring security measures that would allow exposing time lengths at milisecond-level granularity in these cases.
0 commit comments