Skip to content

docs(react): add Metrics to Next Steps section #16197

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
sfanahata merged 1 commit into from
Feb 3, 2026
Merged

docs(react): add Metrics to Next Steps section #16197

Show file tree
Hide file tree
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
42 changes: 42 additions & 0 deletions .claude/rules/pr-description.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# PR Description Format
Copy link
Contributor

@coolguyzone coolguyzone Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine to me, but was it intended to be a part of this PR?

Copy link
Contributor Author

@sfanahata sfanahata Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hah, I probably should have broken it out. I forgot I was on this branch when I made this addition. If it looks okay, I'll just merge. 😄


When creating pull requests for sentry-docs, use the following format:

```markdown
## DESCRIBE YOUR PR

[Clear description of what the PR does and why]

[Bullet points of specific changes if helpful]

- Change 1
- Change 2

## IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
```

## Notes

- Default urgency to "None" unless the user specifies otherwise
- Include preview URLs when relevant (Vercel deploys preview URLs automatically)
- Keep the "DESCRIBE YOUR PR" section concise but informative
- Use bullet points for multiple discrete changes
1 change: 1 addition & 0 deletions docs/platforms/javascript/guides/react/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -444,5 +444,6 @@ You've successfully integrated Sentry into your React application! Here's what t
- [Distributed Tracing](/platforms/javascript/guides/react/tracing/distributed-tracing/) — Trace requests from your React frontend to backend services
- [Connect GitHub + Seer](/organization/integrations/source-code-mgmt/github/#installing-github) — Enable AI-powered [root cause analysis](/product/ai-in-sentry/seer/) by connecting your repository
- [Logs](/platforms/javascript/guides/react/logs/) — Send structured logs correlated with errors and traces
- [Metrics](/platforms/javascript/guides/react/metrics/) <FeatureBadge type="beta" /> — Track custom counters, gauges, and distributions to monitor application health

</StepComponent>