docs(explore): Add practical guides for logs, metrics, and traces #16239
+625
−0
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
…cs, and traces Add four new documentation pages that bridge the gap between SDK setup and getting value from Sentry's observability features: - what-to-log.mdx: High-value logging patterns with search and alert examples - what-to-track.mdx: Metric patterns for counters, gauges, and distributions - querying-traces.mdx: How to query auto-instrumented trace data - custom-spans.mdx: When and how to add custom instrumentation Each guide follows a consistent "5 things to add" structure with code examples, query patterns, and alert recommendations. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds four new documentation pages that help users get value from Sentry after initial SDK setup. These fill the gap between "I set up the SDK" and "I'm getting debugging value."
New pages:
docs/product/explore/logs/what-to-log.mdx- High-value logging patterns (auth, payments, external APIs, background jobs, feature flags) with search queries and alert examplesdocs/product/explore/metrics/what-to-track.mdx- Metric patterns for counters, gauges, and distributions with exploration guidancedocs/product/explore/trace-explorer/querying-traces.mdx- How to query auto-instrumented data (pageloads, fetch, long animation frames, navigation, resources)docs/product/explore/trace-explorer/custom-spans.mdx- When and how to add custom instrumentation for business flows, third-party APIs, and background jobsEach guide follows a consistent structure:
The content was reviewed against the technical-docs and docs-review style guides to ensure it follows Sentry documentation standards (peer tone, code-first, scannable paragraphs, no marketing fluff).