メニュー
Search and manage Datadog Error Tracking issues via API - find grouped errors by service, resolve/ignore issues. Use when investigating production errors or managing error tracking issue states.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create, inspect, and update Datadog monitors via API - get monitor details by ID or URL, create or update metric/query alerts with thresholds and Slack notifications. Use when setting up alerting, tuning monitors, investigating monitor triggers, or checking monitor group states.
Troubleshoot Datadog API authentication issues (401/403 errors), understand API keys vs app keys, and configure correct regions. Use when hitting auth errors or setting up Datadog API access.
Work with Datadog Incidents API - fetch incidents with enrichment, update incident fields, understand incident data structures. Use when working with incidents or the dd-cli get-incident/update-incident commands.
Create log-based count metrics via API - works with all storage tiers including flex. Use when you need to monitor log patterns but logs are in flex tier (where log monitors don't work).
Search Datadog logs via API - query syntax, storage tiers (indexes, flex, online-archives), pagination. Use when searching logs or using the dd-cli search-logs command.
List and inspect Datadog SLOs via API - view SLI values, error budgets, thresholds, and history. Use when checking SLO compliance, reviewing error budgets, or finding SLOs by tag.
| name | datadog-error-tracking |
| description | Search and manage Datadog Error Tracking issues via API - find grouped errors by service, resolve/ignore issues. Use when investigating production errors or managing error tracking issue states. |
# Search issues by service (last 7 days)
dd-cli search-et-issues 'service:my-service-*' --from now-7d
# Search with specific error type
dd-cli search-et-issues 'service:my-service AND @error.type:NullPointerException' --from now-1d
# Search logs-based error tracking (instead of APM traces)
dd-cli search-et-issues 'service:my-service' --track logs
# Sort by most frequent
dd-cli search-et-issues 'service:my-service' --from now-7d --order-by TOTAL_COUNT
# Get a specific issue with details
dd-cli get-et-issue aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
# Resolve an issue
dd-cli update-et-issue-state aaaaaaaa-... RESOLVED
# Ignore an issue (suppresses monitor notifications)
dd-cli update-et-issue-state aaaaaaaa-... IGNORED
# Reopen a resolved/ignored issue
dd-cli update-et-issue-state aaaaaaaa-... OPEN
| Option | Default | Description |
|---|---|---|
QUERY | (required) | Search query (Datadog search syntax) |
--from | now-1d | Start time (now-1h, now-7d, or epoch ms) |
--to | now | End time |
--track | trace | Source: trace (APM), logs, rum |
--order-by | - | TOTAL_COUNT, FIRST_SEEN, IMPACTED_SESSIONS, PRIORITY |
| State | Meaning |
|---|---|
OPEN | New / for review |
RESOLVED | Fixed |
IGNORED | Suppressed from monitor alerts |
Tip: Ignoring an issue automatically mutes it from Error Tracking monitor notifications.
Error Tracking has its own monitor type (error-tracking alert) separate from metric/log monitors. These use a special query DSL:
# New issue monitor (fires on first occurrence or regression)
error-tracking("env:prod service:my-service-*").source("all").new().rollup("count").by("issue.id").last("1d") > 0
# High impact monitor (fires on high error count)
error-tracking("env:prod service:my-service").source("all").impact().rollup("count").by("issue.id").last("5m") > 1
Wildcard tip: Use service:my-prefix-* to automatically cover all current and future deployables without updating the monitor each time a new service is added.
POST /api/v2/error-tracking/issues/searchGET /api/v2/error-tracking/issues/{issue_id}PUT /api/v2/error-tracking/issues/{issue_id}/stateerror_tracking_read / error_tracking_write# Triage: find all open issues for a service, sorted by frequency
dd-cli search-et-issues 'service:my-service state:OPEN' --from now-7d --order-by TOTAL_COUNT
# Investigate: get full details on a specific issue
dd-cli get-et-issue <issue-id>
# Bulk resolve: pipe issue IDs through update
dd-cli search-et-issues 'service:my-service' --from now-30d | \
jq -r '.included[]? | select(.attributes.state == "OPEN") | .id' | \
xargs -I{} dd-cli update-et-issue-state {} RESOLVED