datadog
Use when the user says "check Datadog", "查 Datadog", "查日志", "check logs", "crash logs", "查 crash", "gateway crash", "查告警", "check alerts", "check metrics", or needs to investigate production issues via Datadog Logs API.
npx skills add nexu-io/nexu --skill datadog --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Datadog Log Investigation Query Datadog Logs API to investigate production issues for the Nexu platform. ## Authentication **Before making any Datadog API call, you MUST ask the user for these two keys:** - `DD_API_KEY` — Datadog API Key (Organization Settings → API Keys) - `DD_APP_KEY` — Datadog Application Key (Organization Settings → Application Keys, requires `logs_read_data` scope) Store them in shell variables for the session. Never hardcode or commit them. Site: `datadoghq.com` (US) ## API Base All requests go to `https://api.datadoghq.com/api/v2/logs/events/search`. Headers: ``` DD-API-KEY: <api_key> DD-APPLICATION-KEY: <app_key> Content-Type: application/json ``` ## Common Queries ### OpenClaw Crash Events ```bash curl -s "https://api.datadoghq.com/api/v2/logs/events/search" \ -H "DD-API-KEY: $DD_API_KEY" \ -H "DD-APPLICATION-KEY: $DD_APP_KEY" \ -H "Content-Type: application/json" \ -d '{ "filter": { "query": "service:nexu-gateway @event:openclaw_crash", "from": "now-1h", "to": "now" }, "sort": "-timestamp", "page": {"limit": 20} }' ``` Key fields in results: - `attributes.attributes.exitCode` — process exit code (1 = fatal error, null = signal) - `attributes.attributes.
- Authentication
- API Base
- Common Queries
- OpenClaw Crash Events
- OpenClaw stderr Output (Crash Details)
- Gateway Startup / Recovery Events
- Slack Token Health Check
- API HTTP Request Logs
- Filter by Pod
- Filter by Time Window
- Parsing Results
- Services and Events Reference
- Tag Reference
- Investigation Playbook
curl -s "https://api.datadoghq.com/api/v2/logs/events/search" \
curl -s ... | python3 -c "
import json, sys
data = json.load(sys.stdin)
events = data.get('data', [])
for e in events:
attrs = e['attributes']['attributes']
tags = e['attributes']['tags']
pod = next((t.split(':',1)[1] for t in tags if t.startswith('pod_name:')), '?')
ts = attrs.get('time', '?')What does the datadog skill do?
Use when the user says "check Datadog", "查 Datadog", "查日志", "check logs", "crash logs", "查 crash", "gateway crash", "查告警", "check alerts", "check metrics", or needs to investigate production issues via Datadog Logs API.
How do I install it?
Run `npx skills add nexu-io/nexu --skill datadog --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/nexu, a repository with 3,239 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.