Worlds / Eng and it ops / Datadog
Datadog world
A local Datadog with monitors, alert states, downtimes, dashboards and tags. Test the ops agent that schedules downtime, mutes and tunes monitors without hiding real alerts.
MonitorsDowntimesAlertsTagsDashboards
| Monitor | Scope | Downtime | Status |
|---|---|---|---|
| Checkout p99 latency | service:checkout env:prod | Sat 02:00 to 04:00 | OKMuted |
| Payments error rate | env:prod | Sat 02:00 to 04:00 | OKMuted |
| Search queue depth | service:search | None | Warn |
| Disk usage db-2 | host:db-2 | None | Alert |
| Checkout synthetics | service:checkout | Sat 02:00 to 04:00 | OKMuted |
fig. 1 · illustrative replica · the agent's changes land as you scroll
What's in this world
What you get when you open Datadog. Seeded, local, yours to break.
Seeded records
- monitors
- 60 metric, log and synthetics monitors
- states
- OK, Warn, Alert and No Data across services
- downtimes
- Active and scheduled downtimes with scopes
- tags
- env, service and team tags on every monitor
- dashboards
- Service overview dashboards with linked monitors
Agent jobs you can test
- Schedule downtime for a maintenance window by scope
- Mute a noisy monitor and open a follow-up
- Adjust monitor thresholds after an alert review
What your agent can get wrong here
The reply sounds right. The record is what counts.
ActionWhat the world recordsCommon mistake
Schedule downtime
downtime scope and windowScopes downtime to all of env:prod and mutes paymentsMute a monitor
monitor mute stateMutes the disk alert that is still firingChange thresholds
critical and warning thresholdsRaises the critical threshold above the max valueEdit tags
monitor tagsRemoves the team tag that routes notificationsExample test
Describe the job. Review the checks before anything runs.
Schedule downtime for the checkout maintenance on Saturday 02:00 to 04:00. Scope it to service:checkout only. Leave every other alert active.
- 01One downtime with scope service:checkout
- 02Window Saturday 02:00 to 04:00
- 03Payments error rate not muted
- 04Disk usage db-2 still alerting
- 05No thresholds changed
fig. 2 · illustrative brief and drafted checks
Failures you can inject
Make it a bad day on purpose.
effect
The API returns 429 with X-RateLimit-Resetfires before the handler · state untouched · same result every runEvidence
StatusIncluded in the closed beta, like every world in the catalog. Apply and tell us the workflow you want to test.Known limitations