Integrations / Incidents & monitoring
Better Stack Uptime
Look up Better Stack monitors, heartbeats, status pages and incidents, create or pause monitors, open, acknowledge and resolve incidents, and trigger workflows from monitor, heartbeat and incident events.
Tools
better_stack.list_monitors
List monitors with their status (up, down, validating, paused, pending or maintenance) and when they were last checked. Monitor IDs are numeric strings, e.g. 238.
better_stack.get_monitor
Get a monitor by its numeric ID, e.g. 238, with its settings and current status.
better_stack.create_monitor writes
Create a monitor that checks a URL or host and alerts the on-call person when it fails.
better_stack.set_monitor_paused writes
Pause a monitor, so its downtime is not reported, or resume it.
better_stack.list_heartbeats
List heartbeats (cron and job check-ins) with their status, expected period and grace time in seconds. Heartbeat IDs are numeric strings.
better_stack.list_status_pages
List status pages with their overall state (operational, degraded or downtime) and address.
better_stack.list_incidents
List incidents, newest first, optionally only unresolved or unacknowledged ones or those of one monitor or heartbeat. Incident IDs are numeric strings, e.g. 123456789.
better_stack.get_incident
Get an incident by its numeric ID, e.g. 123456789, with its cause and the failing response.
better_stack.create_incident writes
Open an incident by hand and alert the current on-call person.
better_stack.acknowledge_incident writes
Acknowledge an ongoing incident, which stops it escalating. Fails with 409 if it was already acknowledged.
better_stack.resolve_incident writes
Resolve an ongoing incident. Fails with 409 if it was already resolved.
better_stack.api_get
Send a GET request to any Better Stack Uptime API path under https://incidents.betterstack.com/api and return the response. For endpoints the named tools don't cover.
better_stack.api_request writes
Send a POST, PUT, PATCH or DELETE request to any Better Stack Uptime API path under https://incidents.betterstack.com/api.
Tick Allow raw writes on the connection to add api_request, which can send POST, PUT, PATCH and DELETE requests to any Better Stack Uptime API path.
Connect
- In Better Stack, open API tokens (betterstack.com/settings/api-tokens), switch to the Team-based tokens tab, pick your team and copy a token under Incidents API tokens, or create one.
- Paste it as the connection's API token. A global API token also works, but then every write needs a team, so a team token is simpler.
- To trigger workflows, add an Incident log drain under Integrations → Exporting data with the request URL shown on the connection page, add a request header named Authorization with the value Bearer followed by a long random secret, and paste the same secret on the connection.
Credentials
Triggers
In Better Stack, add an Incident log drain under Integrations → Exporting data with this URL, add a request header named Authorization with the value Bearer followed by the log drain secret saved on this connection, and click Send a test log. Each event carries event, message, and the incident, monitor or heartbeat it is about, e.g. incident_id and resource_name.
Events
triggerkind: better_stack connection: better_stack events: [incident.started] resource_types: [...]
Turn one person's AI process into the company's.
Murmurator is invite-only. Already invited? Sign in and build something real.