Analytics Integration
Query your Sentry error tracking data in plain English. No API calls needed.
Engineering managers, QA teams, and developers who use Sentry for error tracking and want to correlate error data with business metrics or automate error reporting.
Connect your Sentry account to AI for Database and query your error tracking data using natural language. View open issues, recent events, project configurations, and release history — all without writing API calls. Perfect for engineering managers, QA teams, and developers who want to correlate error rates with business metrics.
Sentry tracks every error and exception in your applications. AI for Database turns that error stream into instant answers: which projects have the most issues, how error rates changed after releases, and which errors affect the most users — all from a single query bar.
What data you can query
Issues
Open and resolved issues with error messages, stack traces, and affected users
idtitlestatuslevelnum_commentsfirst_seenlast_seencountuser_countEvents
Individual error events with full context, breadcrumbs, and user data
event_idmessageculprittimestampplatformenvironmentProjects
Project configurations, status, and metadata across your organization
slugnamestatusplatformdate_createdfirst_event_dateReleases
Deployment releases with associated commits and deployment metadata
versiondate_createddate_releasedproject_countcommit_countProblems this solves
Sentry UI doesn't support custom analysis
Sentry's dashboard shows errors but doesn't let you correlate error rates with deployments, feature flags, or business metrics.
Error trends require manual tracking
Understanding if errors are getting better or worse after a release requires manual comparison or building custom dashboards.
No cross-source error analysis
Sentry knows errors but not revenue impact, support ticket volume, or infrastructure metrics. Getting the full picture requires joining data sources.
API is rate-limited and complex
Sentry's API has pagination, rate limits, and requires path parameters. Building custom tooling takes engineering time.
How AI for Database helps
Ask questions in plain English. Get answers backed by real queries.
Error rate trending
Track how error rates change over time and correlate with releases.
> Show me the error count per day for the last 14 days across all projects
Project health comparison
Compare which projects have the most active issues.
> Which projects have the most open high-priority issues right now?
Release impact analysis
Understand if error rates changed after a deployment.
> How did the issue count change before and after our last release?
Error correlation with business data
Join Sentry error data with your database for impact analysis.
> Show me projects with high error rates that also have customer-reported issues in our support database
Pre-built dashboard templates
Error Tracking Dashboard
Monitor error rates and project health
- Open issues by severity (bar)
- Error count trend (line)
- Top projects by error volume (table)
- Recent releases timeline
- User impact metrics (KPI cards)
Automated workflows
Error spike alert
Alert when error count exceeds 2x the 7-day average
Trigger: Every 6 hours
Weekly error digest
Email the engineering team a summary of open issues and trends
Trigger: Weekly on Monday at 9 AM
Key metrics you can track
Example queries
> How many open issues do we have across all projects?
Queries the issues endpoint with status filter, counts open issues across all projects
> Which project has the most errors this week?
Aggregates issue counts per project from the last 7 days, orders by count descending
> Show me all releases in the last 30 days
Queries the releases endpoint, filters by date_created, returns version and project count
Connection options
Direct API (Only option)
Connect directly via Sentry's REST API using an auth token. No warehouse or ETL needed.
Pros
- + Quick setup (under 2 minutes)
- + Real-time data
- + No additional infrastructure
- + Read-only access
Cons
- - Rate limited (~1000 requests/min)
- - No historical backfill beyond API retention
Setup steps:
How to get your Sentry API token
Log in to sentry.io and go to Settings → API Keys (or sentry.io/settings/account/api/auth-tokens/)
Click 'Create New Token' and give it a name (e.g., 'AI for Database')
Select scopes: at minimum 'Project: Read' and 'Org: Read'
Click 'Create Token' — copy the token immediately (it starts with 'snr_')
Find your organization slug from your Sentry URL (sentry.io/{org}/)
Tip: The token is read-only — it cannot create, modify, or delete anything in your Sentry account.
Frequently asked questions
Does this require write access to Sentry?
No — the connector uses read-only scopes. It cannot create, modify, or delete anything in your Sentry account.
Can I query multiple organizations?
Each connection is scoped to one organization. Create multiple connections for multiple orgs.
What data can I query?
Issues, events, projects, and releases via the Sentry API.
How fresh is the data?
Real-time — queries hit the Sentry API directly.
Start querying your Sentry data
Connect in minutes. Ask questions in plain English. Get answers instantly.
Free plan available · No credit card required