Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Added structured logs docs (sentry log list/view), log buffer flush gotcha, updated plugin reference with real implementation, fixed config path docs
What This Skill Does
Connects an OpenClaw instance to Sentry for error tracking, structured logs, and performance traces. Covers plugin setup to route telemetry and CLI-based investigation of issues, logs, and events.
The Sentry CLI covers listing issues, getting AI-generated fix plans, and marking issues resolved in the terminal, without opening the web dashboard for routine investigation.
When to use it
- Monitoring production errors from an OpenClaw gateway
- Streaming real-time structured logs to catch failures as they happen
- Running AI root cause analysis on unresolved exceptions
- Filtering logs by level or message content from the terminal
- Resolving Sentry issues directly via CLI without opening a browser
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Why is my OpenClaw gateway throwing errors in production?
- 1Run `sentry issue list <org>/<project> --query "is:unresolved" --sort date --limit 5` to find recent issues
- 2Run `sentry issue view <short-id>` to see context, affected users, and timeline
- 3Run `sentry issue explain <issue-id>` to get AI root cause analysis via Sentry Seer
- 4Run `sentry issue plan <issue-id>` to generate concrete fix steps
- 5Run `sentry api /issues/<id>/ --method PUT --field status=resolved` to close the issue after fixing
Root cause identified with a concrete fix plan; issue marked resolved in Sentry
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.