Heartbeat Monitors
This resource uses a 'cursor' to paginate. 'start-index' has no effect here.
The Bearer API key of your user more info.
A cursor identifying the current position in the pagination, leave empty to start at the first item, each call returns a 'next-cursor' header for the next page, do not alter the cursor yourself.
nullThe maximum number of results when paging through a list of heartbeat monitors.
100The heartbeat monitor objects
The heartbeat monitor objects
The 'integrationKey' field cannot be set as it is generated automatically. Note: if you are building installation scripts for your hosts, you may send deterministic names and ?include=integrationUrl to still return the 'response.body.integrationUrl' field on 409 (already existing resource) conflict responses. This allows you to run installations with a simple single POST request.
The Bearer API key of your user more info.
We recommend using an interval between 3 and 5 minutes, while pinging every 60 seconds. Of course if you are tracking use-cases like backup jobs that run once a week, a larger timeout and less pings suffice.
Your newly created heartbeat monitor
A heartbeat monitor with this name already exists, this resource will return the details of the already existing heartbeat monitor.
The Bearer API key of your user more info.
numeric entity id
the heartbeat monitor object
the heartbeat monitor object
ATTENTION: changing 'intervalSec' will regenerate the 'integrationKey', you will have to update your monitoring integrations.
The Bearer API key of your user more info.
entity ID
We recommend using an interval between 3 and 5 minutes, while pinging every 60 seconds. Of course if you are tracking use-cases like backup jobs that run once a week, a larger timeout and less pings suffice.
the updated heartbeat monitor object
the updated heartbeat monitor object
Last updated
Was this helpful?