Getting Started With Sentry
Set up Sentry and configure the key features that help you find and fix problems faster.
Sentry captures errors, logs, traces, replays, profiles, and metrics from your application — and connects them all through distributed tracing. This page walks you through the steps to get the most out of Sentry after you've installed the SDK.
New to Sentry? → Sign up here or try the sandbox to explore the product without installing anything.
Plans and Pricing → Sentry offers a free Developer plan and three paid plans (Team, Business, and Enterprise). Each paid plan includes a base volume per data type, and you can add more with discounted reserved volume or a pay-as-you-go budget, all billed by the amount of data you send. Sentry has a 14-day free trial with unlimited event data and access to Business plan features. At the end of the trial, you can upgrade or return to the features and quotas included with your existing plan. If no plan is selected at the end of your trial, your organization will default to the free Developer plan. Learn more about pricing and billing.
Connecting your source code repository is the single most impactful setup step. It unlocks:
- Suspect commits — Sentry identifies the most likely commit that introduced an error
- Seer AI debugging — root cause analysis and Autofix (automatic PR generation); Ask Seer to find relevant telemetry related to issues, or create dashboards, monitors, and alerts
- Stack trace links — click from a stack trace directly to the line in your repo
- Readable stack traces — upload source maps (JavaScript) or debug symbols (native) for de-minified/de-obfuscated stack traces
Set up your GitHub, GitLab, or Bitbucket integration in Settings > Integrations.
Alerts make sure the right people know when things go wrong. Sentry supports:
- Alerts — notify on new errors, regressions, error spikes, or when thresholds like error rate, latency and crash-free session rate are crossed
- Uptime monitors — watch your endpoints for downtime
- Cron monitors — track scheduled jobs for failures or missed runs
Route alerts to Slack, Discord, PagerDuty, or your issue tracker (Jira, Linear, GitHub Issues). See alert best practices for tips on avoiding noise.
After basic error monitoring, these features add the debugging context to help you find and fix problems faster. Data types that Sentry collects are connected via a common TraceID (when tracing is enabled), and can be used together for debugging issues. For example, when an error happens, spans, logs, replays, and profiling data can be used in combination to provide highly useful context for an agent or human to investigate that error.
| Feature | What it adds | Set up |
|---|---|---|
| Tracing | Follow requests across services, find slow queries and N+1s | Enable tracesSampleRate in SDK config |
| Agent Tracing | Trace and debug agent workflows and conversations | Read the instructions for your SDK |
| Logs | Structured logs alongside errors and traces | Add log calls or a logging integration — set up guide |
| Session Replay | Video-like recordings of user sessions (web and mobile) | Enable replay in SDK config |
| Profiling | CPU profiles showing which functions are slow | Enable profiling in SDK config |
| Application Metrics | Custom counters, gauges, distributions | Add metric calls to your code |
| User Feedback | Collect bug reports from users, linked to errors | Add the feedback widget |
Once data is flowing, use these tools to understand your application's health:
- Dashboards — pre-built views for frontend, backend, mobile, and AI performance, plus custom dashboards
- Trace Explorer — search, filter, and aggregate span data to find performance bottlenecks
- Releases — track crash-free sessions, version adoption, and regressions by deploy
Our Guides cover real-world patterns for each feature:
- What to Prioritize — error handling and triage strategies
- What to Log — structured logging patterns
- What to Track — choosing the right metrics
- Querying Traces — finding slow pages and bottlenecks
- Adding Custom Spans — instrumenting your own code
- Using Session Replay — debugging workflows with replays
- Getting Started Tutorial — follow a sample full-stack JavaScript app end-to-end
The Sentry Cookbook has step-by-step recipes for common workflows, including debugging with MCP + Cursor, setting up AI observability, creating dashboards with agents, and more. Full recipes live on sentry.io/cookbook.
- Sandbox — explore Sentry with pre-populated sample data
Follow along with a sample app to set up error monitoring or distributed tracing end-to-end:
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").
