Monitor configuration history
Compare configuration versions and restore a saved snapshot.
Every monitor keeps an immutable version history of its configuration. Open Configuration history on a monitor row—or History in its detail drawer—to view the newest 100 versions and restore one.
A version captures the complete monitor input plus its enabled/paused state: protocol-specific configuration, cadence, timeout, confirmation, recovery, and retry policy, regions, IP policy, assertions, schedules, dependencies, tags, folder, and environment. Health writes such as check results, latency, and heartbeat activity do not create versions.
Compare versions
Select Compare to current on any version to open a side-by-side diff of that version against the current configuration. Credential values are always redacted.
Restore a version
Select Restore this version, then confirm. Restoring:
- replaces the monitor's configuration and enabled state with the version's;
- revalidates dependencies, so a restore is refused if it would reintroduce a dependency on a deleted monitor or a cycle;
- resets runtime health: the monitor returns to pending or paused evaluation;
- creates a new audited version—today's configuration is preserved and you can restore back to it.
Heartbeat tokens are not part of history. Restoring a heartbeat version keeps the current token when one exists; restoring a non-heartbeat monitor from a heartbeat version generates a fresh token and reveals its push URL once.