ref(develop): Define client report quantity instead of discarded envelope section

[sentry-junior]

DESCRIBE YOUR PR

#19854 added a "Quantity of Discarded Envelopes" section under Network Failure Recording to make clear that batched logs, metrics, and spans count their contained items, not 1 per envelope item. The rule is right, but the section makes it harder to follow:

• The rule isn't specific to network failures. It applies to every discard reason.
• Its bullets restate MUSTs that the log byte, metric byte, and span outcome sections already define.
• "record a client report entry for every telemetry item" reads as one entry per item, which conflicts with the (reason, category) → quantity aggregation map.

This PR replaces the section with a short Quantity definition under Concepts, and the quantity field in the payload table now links to it. The definition says quantity counts telemetry items, not envelopes or envelope items; each entry in a container item's items array counts as one; and byte categories use bytes. The links from the logs, metrics, and spans specs now point to the new definition. Spec version is bumped to 1.26.0.

cc @szokeasaurusrex

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

via @szokeasaurusrex.

--

View Junior Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Oct 14, 2026 9:06am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-docs	Ignored	Preview	Oct 14, 2026 9:06am UTC

[cursor]

Rollouts skipped this pull request: The pull request is documentation-only changes (MDX and spec docs) in an application repo, matching the criterion to skip Markdown that does not ship to a depl…

Mention @change-monitor in a comment to monitor it anyway.

[Lms24]

Thanks for cleaning this up!