OpenParable
Skip to content
← Back to skills

Sentry Common Errors

DevOps & Security
sentry-common-errors

Sentry Common Errors is an Agent Skill for devops & security published in the Dicklesworthstone/pi_agent_rust repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Execute troubleshoot common Sentry integration issues and fixes. Use when encountering Sentry errors, missing events, or configuration problems. Trigger with phrases like "sentry not working", "sentry errors missing", "fix sentry", "sentry troubleshoot".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Dicklesworthstone/pi_agent_rust/blob/HEAD/tests/ext_conformance/artifacts/plugins-community/plugins/saas-packs/sentry-pack/skills/sentry-common-errors/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sentry-common-errors, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Sentry Common Errors

Prerequisites

  • Sentry SDK installed
  • Debug mode enabled for troubleshooting
  • Access to Sentry dashboard
  • Application logs available

Instructions

  1. Enable debug mode in SDK configuration for verbose output
  2. Verify DSN is set correctly in environment variables
  3. Check beforeSend function returns event (not undefined)
  4. Review sampling rates to ensure events are not being dropped
  5. Verify source maps are uploaded with correct release version
  6. Set user context after authentication for user tracking
  7. Add ignoreErrors patterns for noisy errors to reduce volume
  8. Enable Breadcrumbs integration with appropriate options
  9. Set tracesSampleRate greater than 0 for performance monitoring
  10. Run diagnostic commands to verify connectivity and capture

Output

  • Issue root cause identified
  • Configuration fix applied
  • Error capture verified working
  • Documentation of resolution

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources