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
Copy file name to clipboardExpand all lines: develop-docs/sdk/telemetry/telemetry-buffer/backend-telemetry-buffer.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
@@ -93,7 +93,7 @@ Each telemetry category maintains a store interface; a fixed-size circular array
93
93
-`batchSize`: Number of items to combine into a single batch (1 for errors, transactions, and monitors; 100 for logs).
94
94
-`timeout`: Maximum time to wait before sending a partial batch (5 seconds for logs).
95
95
-**Bucketed Storage Support**: The storage interface should satisfy both bucketed and single-item implementations, allowing sending spans per trace id (required for Span First).
96
-
-**Observability**: Each store tracks dropped item counts for client reports. Depending on implementation we can either send reports by adding them to existing events or on a timeout basis (Consult [Client Reports](https://develop.sentry.dev/sdk/telemetry/client-reports) for more details). In both cases our source of truth is the dropped counter.
96
+
-**Observability**: Each store tracks dropped item counts for client reports. Depending on implementation we can either send reports by adding them to existing events or on a timeout basis (Consult [Client Reports](/sdk/telemetry/client-reports/) for more details). In both cases our source of truth is the dropped counter.
0 commit comments