Skip to content

docs(client-reports): fix reason inconsistency #16152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Flash0ver merged 1 commit into from
Jan 28, 2026
Merged

docs(client-reports): fix reason inconsistency #16152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion develop-docs/sdk/telemetry/client-reports.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ an envelope item, for example, with the response 429, the client SDK must not re
this as the server already does. Still, the SDK must record lost envelope items
when dropping them itself, for example, caused by an active rate limit. SDKs can put
a simple optional check for HTTP status codes in place where any code `>= 400` except
`429` will be recorded as `network_error`. The client SDKs can assume that client
`429` will be recorded as `send_error`. The client SDKs can assume that client
reports never get rate limited. The server is minimizing the possibility of client
reports getting rate limited, but the SDKs shouldn't worry about this edge case as
this feature is best-effort.
Expand Down