Creates an uptime check.
The check starts running as soon as it is created: it is scheduled in the monitoring region
named by RegionId, the same way the app schedules one.
Target has to match TypeId - ICMP takes Ip, TCP takes Ip and
Port, HTTP takes Url - and sending a field belonging to another type is
rejected rather than ignored.
Autorisations
Your Gorelo API key. See Generate API key. If your data is hosted in Australia, click the base URL at the top of this page and select https://api.aue.gorelo.io.
Corps
Uptime check details.
Request body for creating an uptime check. The owning service provider is resolved from the request context, not from the body.
What the check does: 1 ICMP, 2 HTTP, 3 TCP. Required.
1
What an uptime check points at. Which fields are populated depends on the check type:
ICMP uses Ip, TCP uses Ip and Port, HTTP uses
Url. The others are null.
Move unassigned devices whose public IP matches this check's address to the check's client. Only acted on for ICMP checks that carry both a client and a location; stored either way.
Identifier of the client the check belongs to. When supplied, LocationId
is required with it.
Identifier of the client location the check belongs to.
What the check watches, free text. Max 250 characters.
How often the check runs, in minutes. Required.
1
How many times a failure is rechecked before the check counts as down. Defaults to 2.
2
Which monitoring region runs the check: 1 Seattle, 2 Sydney, 3 UK, 4 Frankfurt. Required.
1
Link to the ISP or provider status page for this endpoint. Max 500 characters.
Identifiers of tags to apply to the check.
Réponse
OK
100, 101, 102, 103, 200, 201, 202, 203, 204, 205, 206, 207, 208, 226, 300, 301, 302, 303, 304, 305, 306, 307, 308, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 421, 422, 423, 424, 426, 428, 429, 431, 451, 500, 501, 502, 503, 504, 505, 506, 507, 508, 510, 511 The identifier of the created uptime check.
null