Skip to content
TakoAPI
Back to skills

sentry-observability

by sergical

Coding Agents & IDEs
615Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Add observability to your OpenClaw instance — errors, logs, and traces sent to Sentry.

Description

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

INPUT

User asks: Why is my OpenClaw gateway throwing errors in production?

AGENT
  1. 1

    Run sentry issue list <org>/<project> --query "is:unresolved" --sort date --limit 5 to find recent issues

  2. 2

    Run sentry issue view <short-id> to see context, affected users, and timeline

  3. 3

    Run sentry issue explain <issue-id> to get AI root cause analysis via Sentry Seer

  4. 4

    Run sentry issue plan <issue-id> to generate concrete fix steps

  5. 5

    Run sentry api /issues/<id>/ --method PUT --field status=resolved to close the issue after fixing

OUTPUT

Root cause identified with a concrete fix plan; issue marked resolved in Sentry

Requirements

  • Sentry account
  • SENTRY_AUTH_TOKEN environment variable (or interactive login via sentry auth login)

Installation

clawhub install sergical/sentry-observability

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links