Update ramp monitoring configuration
Replaces the monitoring configuration. Metric IDs, snapshot cadence, and health-action thresholds (srmAction, noTrafficAction, etc.) can be updated at any time.
datasourceId and exposureQueryId are locked once monitoring starts — stop and recreate the schedule to change the data source.
Changes to guardrail or signal metric IDs take effect on the next analysis run.
Authorizations
If using Bearer auth, pass the Secret Key as the token:
Path Parameters
Body
Full replacement of the monitoring configuration. datasourceId and exposureQueryId cannot be changed while a monitoring experiment is active — stop the schedule first.
1x >= 10auto, manual rollback, hold, warn rollback, hold, warn How long to wait for traffic before applying noTrafficAction. Defaults to 24 hours when null or not set.
x > 0rollback, hold, warn Response
Resource updated
Unique identifier (rs_ prefix)
feature Controlled entity references
Ordered ramp steps
pending, ready, running, paused, completed, rolled-back Index of current step; -1 = not yet started
x >= -1When the current step's time gate elapses; null for steps with no interval (pure approval gates) and terminal states
Actions that restore controlled rules to their pre-ramp state. Applied when rolling back or jumping to start.
Actions applied on top of all step patches when the ramp completes. Represents the final desired rule state.
When the ramp fires. Absent/null means immediately on publish; set to a future datetime to delay start and keep the rule disabled until that time.
Rule-level kill date. When reached, the ramp is completed and the rule is disabled (enabled=false). Use for time-boxed rules that must stop serving on a fixed date regardless of ramp progress. Set to null to clear.
Anchor for cumulative interval timing; resets after each approval gate is satisfied
Milliseconds since startedAt (computed at response time, not stored)
rollback, hold, warn Approval record for the current step. Valid only while stepApproval.stepIndex === currentStepIndex.
When the monitored section most recently started (first monitored step entered). Used for no-traffic grace period gating.
Read-only monitoring status. Present when monitoringConfig is set.

