Menü
Working with Honeycomb SLOs, burn alerts, and SLO history
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
QA the honeycomb CLI against a live account to find bugs and feature gaps. Target one command or resource family for manual testing, or sweep everything before a release. Use when dogfooding the CLI, reproducing a bug, or producing a findings report mapped to issues.
Manage Honeycomb boards: create, update panels, configure visualizations, and review in Chrome. Activated by explicit mention of Honeycomb boards or /board invocation.
Design and build Honeycomb queries: calculations, filters, breakdowns, visualization selection, granularity tuning, and anti-patterns. Activated by explicit mention of Honeycomb queries or /query invocation.
Honeycomb CLI and MCP server usage — auth, queries, datasets, SLOs, boards, triggers, markers, columns, and raw API requests for observability workflows
Add a new cobra subcommand to the CLI
| name | slo |
| description | Working with Honeycomb SLOs, burn alerts, and SLO history |
Dependency chain: derived column (SLI) → SLO → burn alert. All commands require --dataset.
target_per_million: 99.9% = 999000, 99% = 990000, 95% = 950000.
slo create -f - (file-only, no flags yet — see #109)slo update <id> --name/--description/--target/--time-period (flag-based, read-modify-write) or -f (mutually exclusive)slo get <id> / slo get <id> --detailed (Enterprise-only)slo list / slo delete <id> --yesCreate body: {"name":"...","sli":{"alias":"<derived-column-alias>"},"time_period_days":30,"target_per_million":999000}
Create/update require recipients (non-empty array of {"id":"..."}) and slo as {"id":"..."} (nested, not flat slo_id).
Exhaustion time: {"alert_type":"exhaustion_time","exhaustion_minutes":240,"slo":{"id":"..."},"recipients":[{"id":"..."}]}
Budget rate: {"alert_type":"budget_rate","budget_rate_window_minutes":60,"budget_rate_decrease_threshold_per_million":50000,"slo":{"id":"..."},"recipients":[{"id":"..."}]}
All burn alert commands are file-only (-f), no flags yet (#110, #111).
slo history --slo-id <id> --start-time <unix> --end-time <unix> — --slo-id is repeatable. Response is a map keyed by SLO ID.