Does Sentry provide dashboards and infrastructure metrics?

No. Sentry focuses on application errors: search_issues and search_events pull grouped problems and event statistics, and find_releases ties them to a release. For dashboards and alerting over metrics, Grafana fits better, and Datadog for full APM and log search across the stack.

Why is Sentry the first stop in a monitoring investigation?

Because most investigations start with the error. search_issues surfaces the failing issue, search_events shows its frequency, and find_releases checks whether a deploy lines up with the spike, so the agent reaches the exception and its likely cause before pulling wider metrics from Datadog or Grafana.

Sentry for monitoring & incidents

Our top pick for monitoring & incidentsOfficialSentry712

For monitoring and incident investigation, Sentry's official server is the top pick. It pulls issues, stack traces, and events and can run Seer root-cause analysis, giving an agent the fastest path from an error alert to what actually broke, instead of an on-call engineer flipping between consoles at 3am.

It leads here because the first move in most production investigations is reading the error and its stack trace, and that is Sentry's home ground. The broader picks add metrics, dashboards, and product-side context around the failure, but Sentry is where the failure itself is grouped, traced, and tied to a release.

How Sentry fits

search_issues surfaces the grouped problem that fired and search_events queries the underlying events and replays for counts and statistics, so an agent reads the stack trace and sees how often the error occurs. find_releases connects the spike to the release that introduced it, the correlation that often explains a sudden regression, while find_projects and find_organizations keep the investigation scoped. The Seer analysis in Sentry's tagline moves from the raw error toward a likely cause.

The honest scope: Sentry is deep on application errors and does not provide infrastructure metrics, log search, or dashboards of its own. Datadog fits better for full APM and log search across the stack, Grafana for dashboards and alerting over your metrics, and PostHog for product-side regressions in user behavior. The investigation loop, detect, query, correlate, is the same across them, so install by stack. Reach for Sentry first when the alert is an error and you want the exception and its cause immediately.

Tools you would use

Tool	What it does
whoami	Identifies the authenticated user in Sentry.
find_organizations	Finds organizations that the user has access to in Sentry.
find_teams	Finds teams in an organization in Sentry.
find_projects	Finds projects in Sentry.
find_releases	Finds releases in Sentry.
find_dsns	Lists all Sentry DSNs for a specific project.
create_team	Creates a new team in Sentry.
create_project	Creates a new project in Sentry (includes a DSN automatically).
update_project	Updates project settings such as name, slug, platform, and team assignment.
create_dsn	Creates an additional DSN for an existing project.

Full Sentry setup and config →

FAQ

Does Sentry provide dashboards and infrastructure metrics?: No. Sentry focuses on application errors: search_issues and search_events pull grouped problems and event statistics, and find_releases ties them to a release. For dashboards and alerting over metrics, Grafana fits better, and Datadog for full APM and log search across the stack.
Why is Sentry the first stop in a monitoring investigation?: Because most investigations start with the error. search_issues surfaces the failing issue, search_events shows its frequency, and find_releases checks whether a deploy lines up with the spike, so the agent reaches the exception and its likely cause before pulling wider metrics from Datadog or Grafana.