Create a monitor
Create a monitor
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 '.
Headers
A project header is required when using an organization-scoped API key.
1
A project header is required when using an organization-scoped API key.
"luminous-guiding-tower"
Body
Monitor request
Monitor name
"Website"
http, tcp Monitoring request, depends of the chosen protocol
- HTTP protocol
- TCP protocol
List of regions where monitoring checks are performed
1 - 6 elementsas-jpn-hnd, as-sgp-sin, as-tha-bkk, eu-deu-fra, eu-fra-cdg, eu-gbr-lhr, eu-swe-arn, ng-nld-ams, na-mex-mex, na-usa-iad, na-usa-sea, oc-aus-syd, sa-bra-gru Monitoring interval in seconds
30, 60, 120, 180, 300, 600, 900, 1800, 3600 60
Monitoring timeout in milliseconds
1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000, 15000, 20000, 25000, 30000 20000
List of assertions that must be true for the check to be considered successful
- Status code assertion
- Response header assertion
- Response body assertion
Number of uninterrupted failed checks required to create an incident
1, 2, 3, 4, 5 1
Number of uninterrupted successful checks required to resolve an incident
1, 2, 3, 4, 5 1
Number of regions that must fail before an incident is confirmed
1 <= x <= 101
Response
Success, monitor created
Monitor name
"Website"
http, tcp Monitoring request, depends of the chosen protocol
- HTTP protocol
- TCP protocol
List of regions where monitoring checks are performed
1 - 6 elementsas-jpn-hnd, as-sgp-sin, as-tha-bkk, eu-deu-fra, eu-fra-cdg, eu-gbr-lhr, eu-swe-arn, ng-nld-ams, na-mex-mex, na-usa-iad, na-usa-sea, oc-aus-syd, sa-bra-gru Monitor ID
1
Parent project ID
1
fetching, online, offline, partial, paused Whether the monitor is currently paused
true
Rolling average response time of the last 10 requests, in milliseconds
123
Monitoring interval in seconds
30, 60, 120, 180, 300, 600, 900, 1800, 3600 60
Monitoring timeout in milliseconds
1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000, 9000, 10000, 15000, 20000, 25000, 30000 20000
List of assertions that must be true for the check to be considered successful
- Status code assertion
- Response header assertion
- Response body assertion
Number of uninterrupted failed checks required to create an incident
1, 2, 3, 4, 5 1
Number of uninterrupted successful checks required to resolve an incident
1, 2, 3, 4, 5 1
Number of regions that must fail before an incident is confirmed
1 <= x <= 101
Date of creation for the entity
Date of last update for the entity