Define an SLO in Nobl9 using a YAML manifest and sync it via the sloctl CLI
domain: docs.nobl9.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Install sloctl and run sloctl config set to store your Nobl9 organization and client credentials (client-id YOUR_KEY, client-secret YOUR_SECRET)
Create a Project YAML manifest with apiVersion nobl9.com/v1alpha, kind Project, and a metadata.name value
Create a Service manifest referencing the project, then create an SLO manifest specifying: indicator (rawMetric or countMetric), objectives array with target and value, timeWindows (rolling or calendar), and alertPolicies
Reference a DataSource in the indicator.rawMetric.query or countMetric.good/total fields; the dataSourceRef must match a previously applied DataSource object
Apply all manifests in order with sloctl apply -f project.yaml -f service.yaml -f slo.yaml
Verify with sloctl get slo -p YOUR_PROJECT and check the Nobl9 UI for real-time error budget burn visualization
Known gotchas
Nobl9 requires a DataSource object to exist before an SLO that references it can be applied; apply order matters
Rolling time windows use a sliding calculation and may show different numbers than calendar-aligned windows for the same objective — align window type with your on-call cadence
The sloctl CLI version must match the server API version; mismatches produce schema validation errors on apply
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?