Error Monitoring

Overview

This skill helps you analyze application errors from monitoring platforms. It processes error exports, groups events by root cause, identifies duplicates, and classifies errors by user impact — turning a chaotic error stream into an actionable triage report.

Instructions

When the user provides error data (JSON export, CSV, or pasted logs), follow this process:

1. Parse and Normalize

• Accept these inputs, whichever the user has:
  • Sentry: there is no native JSON issue export in the UI. Pull issues with the Organization Issues API, GET https://sentry.io/api/0/organizations/{org}/issues/ (Bearer token with event:read scope; query, statsPeriod, sort, project, limit up to 100, cursor pagination; the next cursor is in the response headers). The project-level /projects/{org}/{project}/issues/ endpoint is deprecated. Discover CSV downloads also work.
  • Datadog: Log Explorer CSV export (up to 100,000 individual logs per export; values are sanitized for spreadsheets) or the Logs API (at most 1,000 logs per request, so paginate).
  • Rollbar: occurrences via GET /api/1/item/{item_id}/instances with a read access token in the X-Rollbar-Access-Token header (limit up to 5000, last_id for the next page). Use the same item endpoints the Rollbar "download items" guide describes.
  • Generic JSON arrays or CSV files
• Never ask the user to paste API tokens into the chat; read them from an environment variable such as SENTRY_AUTH_TOKEN and never echo them into reports