Sentry Cookbook
Step-by-step recipes for real Sentry workflows: instrument agents, debug with MCP, triage from Slack, and more.
The Sentry Cookbook is a collection of recipes: concrete, short walkthroughs for a specific job you want to get done with Sentry. Docs explain how a feature works. Recipes show you how to wire a full workflow end-to-end.
Use the cookbook when you want to:
- Go one step further after setup (monitor an agent, triage overnight errors, ship a fix from Slack)
- Deep-dive a particular subject with a partnered tool (Claude Code, Cursor, Linear, Supabase)
- Copy a proven pattern instead of designing the workflow yourself
| Recipe | Outcome | Time |
|---|---|---|
| Monitor Claude Code with Sentry | Track Claude Code usage, errors, and cost | ~15 min |
| Monitor AI agent costs (Next.js) | Catch agent spend and failures in one place | ~20 min |
| Debug with Sentry MCP + Claude Code | Pull production issues into your coding agent | ~15 min |
| AI Code Review with Seer | Review PRs with Sentry context | ~15 min |
| Fix Sentry issues from Slack | Triage and open fixes without leaving Slack | ~15 min |
| Setup Supabase log drain monitoring | Forward Supabase logs into Sentry | ~10 min |
| Fix user feedback with Cursor agents | Turn feedback into actionable fixes | ~15 min |
| Install the Sentry plugin for coding agents | Land a first fix from your agent | ~10 min |
See every recipe, filter by topic, and pick your next workflow on the full cookbook.
Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").