← ClaudeAtlas

ops-monitorlisted

Unified APM and monitoring surface. Polls Datadog, New Relic, and OpenTelemetry backends for active alerts, error traces, and entity health. Use --watch for live polling every 60 seconds. Use --setup to configure monitoring credentials.
Lifecycle-Innovations-Limited/claude-ops · ★ 17 · AI & Automation · score 86
Install: claude install-skill Lifecycle-Innovations-Limited/claude-ops
## Runtime Context ```bash PREFS="${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json" DD_API_KEY=$(jq -r '.datadog_api_key // empty' "$PREFS" 2>/dev/null) NR_API_KEY=$(jq -r '.newrelic_api_key // empty' "$PREFS" 2>/dev/null) OTEL_ENDPOINT=$(jq -r '.otel_endpoint // empty' "$PREFS" 2>/dev/null) ``` Determine `$ARGUMENTS` mode: - Contains `--setup` → run **Setup flow** - Contains `--watch` → run **Watch mode** - Otherwise → run **Default health check** # OPS ► MONITOR ## Setup flow (`--setup`) Ask which backends to configure: ``` Which monitoring backends would you like to configure? [Datadog] [New Relic] [OpenTelemetry] [All three] ``` For each selected backend, collect credentials via `AskUserQuestion` free-text input (one at a time, ≤4 options per call): **Datadog:** 1. `datadog_api_key` — API Key from app.datadoghq.com/organization-settings/api-keys 2. `datadog_app_key` — Application Key from app.datadoghq.com/organization-settings/application-keys **New Relic:** 1. `newrelic_api_key` — User API Key from one.newrelic.com/api-keys 2. `newrelic_account_id` — Numeric Account ID from New Relic admin portal **OpenTelemetry:** 1. `otel_endpoint` — Base URL of your OTEL-compatible backend (e.g., https://otlp.grafana.net) Write each credential to preferences.json using atomic tmpfile swap: ```bash tmp=$(mktemp) jq --arg k "$KEY" --arg v "$VALUE" '.[$k] = $v' "$PREFS" > "$tmp" && mv "$tmp" "$PREFS" ``` Run smoke test after savi