メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | datadog-slos |
| description | 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. |
# List all SLOs
dd-cli list-slos
# Filter by tags
dd-cli list-slos --tags 'env:prod,team:backend'
# With pagination
dd-cli list-slos --limit 10 --offset 20
| Option | Default | Description |
|---|---|---|
--tags | - | Comma-separated tags to filter by (e.g., env:prod,team:backend) |
--limit | - | Max number of SLOs to return |
--offset | - | Pagination offset |
--timeout | 15 | Request timeout in seconds |
Returns a summary array with id, name, type, tags, and thresholds for each SLO.
# Get SLO with default 7-day history
dd-cli get-slo abc123def456
# Get SLO with 30-day history
dd-cli get-slo abc123def456 --from now-30d
# Custom time range
dd-cli get-slo abc123def456 --from now-1d --to now
| Option | Default | Description |
|---|---|---|
SLO_ID | (required) | The SLO identifier (hex string) |
--from | now-7d | History start time (e.g., now-7d, now-30d, or epoch seconds) |
--to | now | History end time |
--timeout | 30 | Request timeout in seconds |
| Field | Description |
|---|---|
data.name | SLO name |
data.type | SLO type: metric or time_slice |
data.tags | Tags (e.g., env:prod, service:my-service) |
data.thresholds | Target percentage per timeframe (e.g., 99.9% over 7d) |
data.query | Numerator/denominator metric queries (for metric SLOs) |
history.data.overall.sli_value | Current SLI value (e.g., 99.9999) |
history.data.overall.state | Current state: ok, breached, no_data |
| Type | Description |
|---|---|
metric | Based on metric queries (good events / total events ratio) |
time_slice | Based on time slices where a condition is met |
GET /api/v1/slo -- returns all SLOs, supports tags, limit, offset paramsGET /api/v1/slo/{slo_id} -- returns SLO definitionGET /api/v1/slo/{slo_id}/history -- returns SLI value, error budget over time range# 1. Find SLOs by service tag
dd-cli list-slos --tags 'service:my-service'
# 2. Check error budget for a specific SLO (30-day window)
dd-cli get-slo abc123def456 --from now-30d
# Look at: history.data.overall.sli_value and history.data.overall.state
# Check all SLOs for a team before deploying
dd-cli list-slos --tags 'team:my-team'
# Then inspect any that look concerning:
dd-cli get-slo <id> --from now-7d
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.
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.
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.