From Zero to SLO in Five Prompts

Length: 60 minutes, live and hands-on

Description

Our SLO webinar showed why SLOs matter more as AI writes more of your code. This workshop is where you build one.

Bring a service you own and the AI coding agent you already use: Claude Code, Cursor, Windsurf, Copilot CLI or similar. We'll work through five prompts together. Your agent does the work, and you check each result in Dash0 before moving on. Liat runs the same prompts live, so you always have a working reference.

You'll leave with

• OpenTelemetry flowing from your service to Dash0
• An availability SLO defined as code
• Deploy markers from your CI on the error budget
• Burn-rate alerts that page on fast burns and ticket slow leaks

The five prompts

1. Instrument the app. Add OpenTelemetry to your code and match the service name in your infrastructure.
2. Send telemetry to Dash0. Point the exporter at your dataset and confirm data is arriving.
3. Create the SLO. Define an availability SLO as code and apply it through the Dash0 API.
4. Add deploy markers. Every deploy from CI shows up on your SLO.
5. Alert on burn rate. Page on a fast burn, ticket a slow leak.

Five prompts: from your environment to an SLO with deployment markers

Who it's for

SREs, platform engineers and developers who own a service and want an SLO on it this week, not next quarter. Works with any language, IaC and CI. New to SLOs? Watch the webinar recording first.

Before you join

You'll need a Dash0 account, two auth tokens from an org Admin and your AI coding agent. We'll email the full setup checklist when you register.

Review the five prompts before you join.