Closed beta · run Worlds on your machineBrowse worlds →

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
Book a demo
Datadog · Monitors · ManageIllustrative
MonitorScopeDowntimeStatus
Checkout p99 latencyservice:checkout env:prodSat 02:00 to 04:00OKMuted
Payments error rateenv:prodSat 02:00 to 04:00OKMuted
Search queue depthservice:searchNoneWarn
Disk usage db-2host:db-2NoneAlert
Checkout syntheticsservice:checkoutSat 02:00 to 04:00OKMuted

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

  1. Schedule downtime for a maintenance window by scope
  2. Mute a noisy monitor and open a follow-up
  3. 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 downtimedowntime scope and windowScopes downtime to all of env:prod and mutes payments
Mute a monitormonitor mute stateMutes the disk alert that is still firing
Change thresholdscritical and warning thresholdsRaises the critical threshold above the max value
Edit tagsmonitor tagsRemoves the team tag that routes notifications

Example test

Describe the job. Review the checks before anything runs.

Brief · plain EnglishIllustrative

Schedule downtime for the checkout maintenance on Saturday 02:00 to 04:00. Scope it to service:checkout only. Leave every other alert active.
Drafted test · reviewDrafting
  1. 01One downtime with scope service:checkout
  2. 02Window Saturday 02:00 to 04:00
  3. 03Payments error rate not muted
  4. 04Disk usage db-2 still alerting
  5. 05No thresholds changed

fig. 2 · illustrative brief and drafted checks

Failures you can inject

Make it a bad day on purpose.

effectThe API returns 429 with X-RateLimit-Resetfires before the handler · state untouched · same result every run

Evidence

StatusIncluded in the closed beta, like every world in the catalog. Apply and tell us the workflow you want to test.Known limitations