How to set up an SLO with OpenTelemetry and your AI coding agent
Blog post from Dash0
A five-prompt workflow uses an AI coding agent to instrument an application with OpenTelemetry, send telemetry directly to Dash0, create an availability SLO as code, add deployment markers through CI, and configure alerts for rapid or gradual error-budget consumption. Users first obtain a Dash0 authentication token, OTLP/HTTP ingress endpoint, API endpoint, and dataset, while keeping credentials in a secure, gitignored environment file and ensuring consistent service name, namespace, and version values throughout the app, infrastructure, CI, and SLO configuration. The example SLO targets 99.5% successful requests over a rolling 28-day window, with Dash0 calculating error budgets and burn rates from request spans; dashboards begin collecting data only after the SLO is created. Deployment events appear as chart markers when service metadata matches exactly, helping teams correlate releases with reliability changes, while preset check rules can route fast-burn incidents to paging and slower deterioration to ticket queues. The approach also supports multi-service SLOs, latency objectives, direct telemetry ingestion without a collector, and up to 25 SLOs per organization.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| AI Coding Assistant | 6 | 1,471 | 355 | 128 | -25% |
| OpenTelemetry | 6 | 468 | 108 | 50 | -46% |
| Kubernetes | 1 | 3,442 | 313 | 98 | -33% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.