Better Stack

Better Stack

This connector works with the Better Stack Incidents API (formerly Better Uptime, https://incidents.betterstack.com/api): uptime monitors and heartbeats, incidents and their timeline, on-call calendars, escalation policies and severities, status pages with status reports, and the configured integrations. Telemetry (logs, metrics, dashboards) is not part of this connector.

Setup (2 minutes)

1. Open https://betterstack.com/settings/api-tokens/0, pick your team and copy (or create) a token in Incidents API tokens. This team-scoped token is the simplest choice.
2. A global API token (https://betterstack.com/settings/global-api-tokens) also works and reaches every team; then pass team_name to filter lists, and it is required when creating monitors, heartbeats or incidents.
3. Paste the token into BETTER_STACK_API_TOKEN and run better_stack_list_monitors to check it. Writes need a token with write access.

Workflow

• Is something down? better_stack_list_monitors (status up, down, paused, validating, maintenance), then better_stack_get_monitor. Uptime numbers: better_stack_get_monitor_availability for a date range, better_stack_get_monitor_response_times for the last 24 hours.
• Manage monitors: better_stack_create_monitor, better_stack_update_monitor, better_stack_pause_monitor and better_stack_resume_monitor around planned work. Groups: better_stack_list_monitor_groups, better_stack_get_monitor_group, better_stack_list_monitor_group_monitors.
• Cron jobs: better_stack_list_heartbeats, better_stack_get_heartbeat, better_stack_create_heartbeat (returns the ping URL the job must call), better_stack_update_heartbeat, better_stack_get_heartbeat_availability, better_stack_list_heartbeat_groups.
• Incident response: better_stack_list_incidents with resolved: false for open incidents, better_stack_get_incident, better_stack_get_incident_timeline, then better_stack_acknowledge_incident, better_stack_escalate_incident, better_stack_resolve_incident or better_stack_reopen_incident. Notes: better_stack_list_incident_comments, better_stack_add_incident_comment. Raise one by hand with better_stack_create_incident (alerts people).
• Who is on call: better_stack_list_on_call_calendars, better_stack_get_on_call_calendar (use default for the team's default calendar, date for another moment), better_stack_list_on_call_events for the shifts in a window. Escalation: better_stack_list_escalation_policies, better_stack_get_escalation_policy, better_stack_list_severities.
• Status pages: better_stack_list_status_pages, better_stack_get_status_page, better_stack_list_status_page_resources (resource ids for affected_resources), better_stack_list_status_reports, better_stack_get_status_report, better_stack_list_status_updates. Communicate: better_stack_create_status_report, then better_stack_add_status_update as things change, and better_stack_update_status_report to change the title or reschedule.
• Configuration: better_stack_list_incoming_webhooks, better_stack_list_outgoing_webhooks, better_stack_list_slack_integrations, better_stack_list_metadata.

Before writing: creating an incident, escalating it and publishing a status report alert real people or public subscribers. Confirm with the user first; set notify_subscribers: false for a quiet status report.

Reading the answers: JSON:API style: data (one object or a list) with id, type, attributes and relationships; related users and status updates come in included. Ids are numeric strings. Times are ISO 8601 in UTC; date filters (from, to) take YYYY-MM-DD. Availability is a percentage (99.98), downtime and incident lengths are seconds, response times are seconds. Incident status is Started, Acknowledged or Resolved. Monitor passwords, Playwright environment variables and policy incident tokens are left out of the answers.

Paging: lists return pagination.next (a URL, null on the last page); call again with page set to the page number in that URL. per_page is 50 by default, up to 250; incidents default to 10 and allow 50.

Errors: 401 means a wrong or revoked token (or a Telemetry token instead of an Incidents one), 403 a token without write access, 404 an unknown id or an id of another team, 422 a validation error whose errors names the field, 429 the rate limit.