Update a monitor
Update a monitor by ID
Authorizations
Use a user token to access authenticated routes. The token must be specified in the Authorization HTTP header with the following format 'Authorization: Bearer <token>'.
Path Parameters
ID of the monitor to update
Body
Associated alert policy ID
Number of uninterrupted failed checks required to create an incident
1, 2, 3, 4, 5 Monitoring interval in seconds
30, 60, 120, 180, 300, 600, 900, 1800, 3600 Monitor name
http, tcp Number of uninterrupted successful checks required to resolve an incident
1, 2, 3, 4, 5 List of regions where monitoring checks are performed
as-ind-bom, as-jpn-nrt, as-sgp-sin, eu-deu-muc, eu-gbr-lhr, eu-swe-arn, na-mex-mex, na-usa-pdx, na-usa-ric Monitoring request, depends of the chosen protocol
Response
Associated alert policy ID
Number of uninterrupted failed checks required to create an incident
1, 2, 3, 4, 5 Monitoring interval in seconds
30, 60, 120, 180, 300, 600, 900, 1800, 3600 Monitor name
http, tcp Number of uninterrupted successful checks required to resolve an incident
1, 2, 3, 4, 5 List of regions where monitoring checks are performed
as-ind-bom, as-jpn-nrt, as-sgp-sin, eu-deu-muc, eu-gbr-lhr, eu-swe-arn, na-mex-mex, na-usa-pdx, na-usa-ric Monitoring request, depends of the chosen protocol
Date of creation for the entity
Monitor ID
Date of the last monitoring check
Whether the monitor is currently paused
Parent project ID
Rolling average response time of the last 10 requests, in milliseconds
fetching, online, offline, partial Date of last update for the entity
Was this page helpful?