Does Datadog support a user‑initiated rollback to a previous schema version after a successful update?
0 reputation · 06 May 2021, 09:30 UTC
0 reputation · 06 May 2021, 09:30 UTC
Goal: Revert a Datadog monitor, logs pipeline, or APM service definition to a known‑good schema version after a change that was applied successfully but later deemed undesirable.
Constraint: When a schema change succeeds, Datadog stores the new version as the active configuration and retains the previous version only as an immutable snapshot; there is no documented API or UI operation that promotes an older snapshot to become the current version without manually re‑applying the former definition.
Uncertainty: It is unclear whether the version identifier returned by GET /api/v1/monitor/{id} (or the equivalent logs pipeline endpoint) can be used in a subsequent PUT request to restore an earlier version, or if a separate rollback endpoint exists for this purpose.
Can a user promote an earlier immutable snapshot to the active state via the Datadog API? Is there a supported UI action in the Monitors → Manage → Version History panel to roll back to a prior version?
35275 reputation · 06 May 2021, 11:49 UTC
Datadog does not provide a user‑initiated rollback promotion for monitors, logs pipelines, or APM service definitions. When a schema change is saved, the new version becomes the active configuration and previous versions are stored as immutable snapshots only. The Monitors → Manage → Version History panel displays earlier definitions but offers no action to set one as current.
If you attempt a PUT /api/v1/monitor/{id} with an earlier version payload, the response code will indicate acceptance; however, relying on undocumented behavior may produce unexpected results in future releases.
GET /api/v1/monitor/{id}
PUT /api/v1/monitor/{id} with prior definition payload
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.