Sentry dashboard builder. Error analytics with AI.
Connect to Sentry, build custom error dashboards, monitor release stability, and automate incident response — just by asking.
InsufficientStockError
error 2,847 events
InsufficientStockError: Requested 5 units of SKU-8847, but only 2 available
return fn(req, res, next);
src/middleware/auth.ts:
const token = await verifyJWT(req.headers.authorization);
src/services/user.ts:
const user = await db.query('SELECT * FROM users WHERE id = $1', [id]);
src/controllers/order.ts:
const inventory = await checkStock(items);
src/services/inventory.ts:
throw new InsufficientStockError(sku, requested, available);
First seen 2h ago 412 users affected release v2.4.2
Every severity, at a glance.
camelAI pulls your Sentry data and builds severity-aware dashboards that show what matters most — right now.
| Severity | Count | Change |
|---|---|---|
| Fatal | 3 | +2 vs yesterday |
| Error | 847 | -12% vs yesterday |
| Warning | 2,391 | +3% vs yesterday |
| Info | 14,208 | stable |
Track stability across releases.
See which deploys introduced regressions and which ones cleaned things up. camelAI builds release-aware error dashboards automatically from your Sentry data.
| Release | Date | Error Delta | Crash-free | New Issues |
|---|---|---|---|---|
| v2.4.0 | Mar 1 | -8% | 99.7% | 2 |
| v2.4.1 | Mar 5 | +2% | 99.5% | 1 |
| v2.4.2 | Mar 8 | +47% | 97.2% | 14 |
| v2.5.0 | Mar 12 | -31% | 99.8% | 3 |
| v2.5.1 | Mar 15 | +5% | 99.1% | 5 |
Beyond the alert.
Sentry tells you what broke. camelAI builds the dashboard to understand why and how often.
Pattern Detection
Sentry: Groups similar errors
camelAI: Builds dashboards showing error correlations across services, deploys, and user segments. Surfaces patterns Sentry's grouping misses.
Root Cause Analysis
Sentry: Shows the stack trace
camelAI: Cross-references error spikes with deploy timelines, config changes, and traffic patterns to pinpoint what actually caused the regression.
Impact Assessment
Sentry: Counts affected users
camelAI: Builds impact reports: revenue at risk, SLA budget consumed, affected customer tiers. Gives you the business context to prioritize fixes.
From raw issues to real insight.
Ask camelAI to build an issue dashboard and get a live, filterable view of your Sentry data — deployed to a shareable URL.
Error Dashboard — Production
3 critical
Error Rate (last 24h)
Errors Spike
5002500
00:0006:0012:0018:0023:00
| Issue | Events | Users | First Seen | Last Seen |
|---|---|---|---|---|
| InsufficientStockError | 2847 | 412 | 2h ago | 14s ago |
| fatalDatabaseConnectionTimeout | 156 | 89 | 2m ago | 45m ago |
| warningRateLimitExceeded | 8291 | 1204 | 1m ago | 3d ago |
| errorPaymentProcessingError | 94 | 67 | 8m ago | 6h ago |
| errorInvalidTokenError | 531 | 298 | 32s ago | 1d ago |
Showing 5 of 127 unresolved issues.
Automated incident response.
Set up a cron job that monitors your Sentry error rate every hour. When errors spike above your baseline, camelAI posts a summary of the top new issues to Slack — before your customers notice.
- Hourly error rate checks against 7-day baseline
- Automatic Slack alerts with top issues and affected users
- Release regression detection on every deploy
- Custom thresholds per project and environment
"Every hour, check Sentry error rates. If errors spike above 2x baseline, alert #incidents in Slack with the top 5 new issues."
Setting up cron job: 0 * * * *
Connecting to Sentry API...
Baseline error rate: 12.4/min (7-day avg)
Threshold configured: >24.8/min triggers alert
Slack webhook: #incidents channel configured
Cron job active. Next run: 14 minutes.
What will you build on your Sentry data?
- “Connect to our Sentry project and build a release stability dashboard. Show crash-free rate, new issues, and error deltas for each release over the last 30 days.”
- “Pull all unresolved issues from Sentry, group them by service, and build an impact dashboard showing affected users, event frequency, and revenue at risk per issue.”
- “Analyze our Sentry error trends for the past week. Correlate spikes with our deploy log and build a report showing which commits introduced the most regressions.”
- “Set up an hourly cron that checks our Sentry error rate. If it exceeds 2x the baseline, post a summary of the top new issues to #incidents in Slack.”
Your errors are already tracked.
Now make them actionable.