feat(metrics): Add trace sampling metrics for traffic visibility #16241
+41
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Track sampling decisions with Sentry.metrics.count to provide visibility into traffic patterns hitting the docs site. Each sampling decision now emits a docs.trace.sampled metric with attributes for traffic_type (ai_agent, bot, user, unknown), the specific bot/agent matched, and the sample rate applied. This enables querying in Sentry to understand: - Volume breakdown by traffic type - Which bots are hitting the site most frequently - Which AI agents are consuming docs content - How much traffic is being filtered vs sampled Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Sentry metrics to the tracesSampler to provide visibility into traffic
patterns hitting the docs site.
Each sampling decision now emits a
docs.trace.sampledmetric with attributes:traffic_type: ai_agent, bot, user, or unknownagent_match/bot_match: the specific pattern that matched (e.g., "claudebot", "googlebot")sample_rate: the sampling rate applied (0, 0.3, or 1)This builds on #16213 which added the tracesSampler for bot filtering. With
these metrics, we can now query in Sentry to understand volume breakdown by
traffic type, which bots hit the site most, and which AI agents are consuming
docs content.