sentry

To list unresolved Sentry production errors, you filter issues by organization, project, environment, and time range, then configure retrieval limits. This read-only query returns recent production issues without leaving your command line.

You can query the Sentry API to retrieve specific issue details and examine specific error events. The script fetches read-only observability data deterministically, providing isolated information for targeted debugging.

You need a SENTRY_AUTH_TOKEN for authentication to inspect Sentry events via the API. The bundled Python script requires this token to execute read-only queries against your configured Sentry organization.

The best way to check for new critical errors after a deployment is listing top unresolved issues filtered by the production environment and recent time range. This summarizes recent production health data quickly.

Filtering Sentry issues by environment and project works by passing these parameters to the Sentry API script. It restricts the read-only observability data retrieval to match your specific application context and infrastructure.

Limitations of monitoring production issues using read-only API queries include the inability to resolve, assign, or modify issues directly. The script strictly retrieves observability data for inspection and summarization.