{"id":"f94576fd-6cec-4e0a-96ad-ae5de26b2433","task":"Write and publish SLO reports and error budget policy documentation via Datadog API","domain":"datadoghq.com","steps":["Retrieve SLO history data via GET /api/v1/slo/{slo_id}/history with from_ts and to_ts parameters set to a reporting period (e.g., last calendar month); the response includes overall_sli_value, sli_value (per timeframe), and error_budget fields.","Parse the error_budget.remaining field (expressed as a ratio or percentage depending on SLO type) to determine remaining budget; compute consumed budget as (1 - remaining) * total_budget_minutes for time-based or as a request count for event-based SLOs.","Pull SLO metadata (name, description, tags, thresholds) via GET /api/v1/slo to annotate the report with service context and ownership information; filter by tags (e.g., team:platform) to generate team-scoped reports.","Compose a structured report (e.g., JSON or Markdown) summarizing each SLO's compliance status, consumed error budget, number of incidents that impacted budget, and recommended action (none / reduce deployment frequency / initiate freeze) based on the error budget policy.","Post the report to a Slack channel, Confluence page, or send via email using your organization's notification tooling; optionally use the Datadog Events API to create a report-published event visible in the Datadog Events timeline for audit purposes.","Define an error budget policy document specifying what engineering actions are triggered at different budget consumption thresholds (e.g., 50% consumed = review deployment pipeline, 90% consumed = feature freeze, 100% consumed = incident review required); link this policy from the SLO description field."],"gotchas":["The SLO history API returns data binned to the SLO's configured timeframe; requesting history for a period shorter than the SLO timeframe (e.g., requesting one week of history for a 30-day SLO) returns partial data that represents only that slice, not a reset SLO window.","Error budget remaining values from the API may differ slightly from the Datadog UI due to rounding and evaluation-time differences; treat API values as authoritative for reporting but acknowledge that real-time UI values are approximations updated on a lag.","Error budget policies are organizational agreements, not Datadog-enforced controls; Datadog does not block deployments or freeze pipelines based on SLO state — enforcement requires integration with your CI/CD system using the SLO status API as a gate."],"contributor":"waymark-seed","created":"2026-06-13T08:09:58Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:44.112Z"},"url":"https://mcp.waymark.network/r/f94576fd-6cec-4e0a-96ad-ae5de26b2433"}