← Better StackCONTENT HISTORY

Update to Better Stack

Snapshot Nov 11, 2026 · 06:08 UTC · version 1.1.3

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Better Stack and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Reference for Better Stack Uptime monitors and escalation policies — monitor types, valid configuration values, how escalation policies work, and the limits of what the monitor tools can do. Load before using create_monitor, create_heartbeat, monitors, monitor, escalation_policies or escalation_policy.",
  "included_files": [],
  "name": "uptime-monitors",
  "skill_md_contents": "---\nname: uptime-monitors\ndescription: Reference for Better Stack Uptime monitors and escalation policies — monitor types, valid configuration values, how escalation policies work, and the limits of what the monitor tools can do. Load before using create_monitor, create_heartbeat, monitors, monitor, escalation_policies or escalation_policy.\n---\n\n# Uptime monitors & escalation policies\n\nWhat the Uptime tools can do, the non-obvious rules, and where the limits are. A **monitor** is one Uptime check against a URL or host; when a check fails it opens an **incident** and alerts whoever the monitor's **escalation policy** routes it to.\n\n## Tools at a glance\n\n- `monitors`, `monitor` — read monitors.\n- `monitor_availability`, `monitor_response_times` — a monitor's availability and response times, per region.\n- `create_monitor` — create a monitor. `create_heartbeat` — create a heartbeat (below).\n- `escalation_policies`, `escalation_policy` — read escalation policies (who gets paged).\n\nShow the user what you are about to create and get a yes before calling a create tool: a new monitor starts checking, and alerting, right away.\n\nThere is **no update, pause/resume or delete tool**. You can create and read monitors, but not edit one in place (change its URL, frequency, alerting, etc.), pause, resume or remove it. You can read escalation policies but not create/edit them. To change a monitor, give the user its link from the tool result so they can adjust it in the Better Stack UI.\n\n## Monitor types\n\n`monitor_type` defaults to `status`. What the `url` field means depends on the type:\n\n| Type                                    | Checks                                 | `url` is               | Extra field                      |\n| --------------------------------------- | -------------------------------------- | ---------------------- | -------------------------------- |\n| `status`                                | HTTP returns 2xx                       | full URL (`https://…`) | —                                |\n| `expected_status_code`                  | HTTP returns one of the listed codes   | full URL               | `expected_status_codes`          |\n| `keyword`                               | response body **contains** a word      | full URL               | `required_keyword`               |\n| `keyword_absence`                       | response body is **missing** a word    | full URL               | `required_keyword`               |\n| `ping`                                  | host answers ICMP ping                 | host (`example.com`)   | —                                |\n| `tcp` / `udp` / `smtp` / `pop` / `imap` | a port answers                         | host                   | `port`                           |\n| `dns`                                   | a DNS server answers                   | host (DNS server)      | `request_body` (domain to query) |\n| `playwright`                            | a scripted browser/API scenario passes | scenario name          | the script (UI only)             |\n\n**You can create every type except `playwright`**: `create_monitor` takes no script, so a Playwright monitor is set up in the Better Stack UI (see below). The port-based types (`tcp`, `udp`, `smtp`, `pop`, `imap`) need `port`.\n\n**Heartbeats** (passive \"ping us every N minutes\" checks for cron jobs and workers) are created with `create_heartbeat`; the job then calls the heartbeat URL from the result on every successful run. **SSL-certificate** / **domain-expiration** monitors (they alert N days before expiry; valid windows are 1, 2, 3, 7, 14, 30, 60 days) **can't be created via these tools**: direct the user to the UI.\n\n## Configuration you can set (and valid values)\n\n`create_monitor` exposes a curated subset of monitor settings. Passing an invalid value is rejected, so stick to these:\n\n- `check_frequency` (seconds): HTTP monitors **30, 45, 60, 120, 180, 300, 600, 900, 1800**; Playwright **60, 180, 300, 600, 900, 1800, 3600, …**. Sub-3-minute frequencies need a paid plan (otherwise floored to the plan minimum).\n- `request_timeout` (seconds): HTTP **2–180**, Playwright **15–900**; must not exceed `check_frequency`.\n- `regions`: any subset of **`us`, `eu`, `as`, `au`** (defaults to all four if omitted).\n- `http_method`: `get` (default), `head`, `post`, `put`, `patch`. Send a payload with `request_body` (for `post`/`put`/`patch`, or as the query for a `dns` monitor).\n- `verify_ssl` (default true) and `follow_redirects` (default true).\n- `recovery_period` (seconds the check must pass before an incident auto-resolves: 0, 60, 180, 300, 900, 1800, 3600, 7200) and `confirmation_period` (seconds to re-check before opening an incident: 0–86400).\n- `request_headers`: list of `{name, value}`.\n- `required_keyword`, `expected_status_codes` — see the type table.\n- Alert flags: `email`, `sms`, `call`, `push`, `critical_alert` (but see the policy gotcha below).\n- `paused`: create the monitor without checking until it's resumed (in the UI).\n- `policy_id` — see escalation policies.\n\n- `port` (port-based types), `monitor_group_id` (an existing monitor group), `team_wait` (seconds before escalating to the whole team).\n\n**Not settable via the tool** (UI-only — don't promise them): basic auth (`auth_username`/`auth_password`), the Playwright script, `environment_variables` and `scenario_name`, `remember_cookies`, maintenance windows, SSL/domain-expiration alerts and proxy.\n\n**3xx gotcha:** an `expected_status_codes` list containing a 3xx (e.g. `[200, 301]`) is rejected unless **both** `follow_redirects` _and_ `remember_cookies` are off — and `remember_cookies` isn't settable here. So a monitor that expects a 3xx can't be fully created via the tool; set it up in the UI, or don't list a 3xx as expected.\n\n## Creating a Playwright monitor\n\nA `playwright` monitor runs a JavaScript scenario — the way to assert **several things at once** (status + body + response time) or drive a browser flow, which no basic type can do.\n\n- `create_monitor` takes no script: write the scenario for the user and have them create the Playwright monitor in the Better Stack UI and paste it there.\n- For simple HTTP scenarios use Playwright's request API:\n  ```js\n  import { test, expect } from \"@playwright/test\";\n  test(\"health\", async ({ request }) => {\n    const start = Date.now();\n    const res = await request.get(\"https://example.com/health\");\n    expect(res.status()).toBe(200);\n    expect(await res.text()).toBe(\"OK\");\n    expect(Date.now() - start).toBeLessThan(3000);\n  });\n  ```\n- `check_frequency` for Playwright must be ≥ 60s (60, 180, 300, 600, 900, 1800, 3600, …); it defaults to 180 and is floored to the plan's minimum. Playwright monitoring also needs a plan that includes it, or the create is denied.\n- Playwright monitors are **stateless** — nothing persists between runs (no shared session or cookies), so each script must set up whatever it needs.\n- Secrets: credentials go in the monitor's environment variables in the UI. Never hardcode secrets in the script.\n\n## Importing Datadog synthetic tests\n\nWhen a user pastes a Datadog `datadog_synthetics_test` (Terraform or JSON), convert it to one Better Stack monitor:\n\n- **One simple assertion → a basic type.** Status-code only → `expected_status_code` (or `status` for 2xx). Body-contains only → `keyword`.\n- **Multiple assertions or a browser test → `playwright`.** Datadog API tests usually assert several things at once (statusCode + body + responseTime), which a basic monitor can't express — generate a Playwright script that makes the request and `expect`s each assertion. Build the request from `request_definition` (method + url) and one `expect` per `assertion` block (`statusCode`, `body`, `responseTime`, …).\n- **Map the fields:** `name` → `pronounceable_name` (or the scenario name in `url` for Playwright) · `request_definition` → into the script · `options_list.tick_every` → `check_frequency` (round to a valid value) · `locations` → `regions` (Datadog has many; pick the closest subset of `us`/`eu`/`as`/`au`). Datadog's `message`, `monitor_options`, `retry`, and `min_location_failed` have no direct equivalent — say they aren't carried over rather than inventing fields.\n- Show the user the script and settings before creating anything; a Playwright scenario goes in through the UI (above).\n\n## Escalation policies\n\n- To route alerts through a specific policy, pass `policy_id` — but **call `escalation_policies` first** to get a valid ID. Never guess an ID: a wrong one is rejected or belongs to another team.\n- **Omit `policy_id` to use the team's default policy.**\n- **Gotcha: when `policy_id` is set, the simple `email`/`sms`/`call`/`push` flags are ignored** — the policy decides who is notified. Only use those flags when you are _not_ setting a policy.\n- Use `escalation_policy` to read a policy's escalation steps (who is notified, in what order, with repeats) before recommending one.\n- A step notifies a Slack channel through a `slack_integration` step member, whose id is a Slack integration ID from `slack_integrations`. Policy steps are changed in the Better Stack UI; what the channel does with the alert (a thread or a channel per incident, who Slack users can page) is the Slack integration's, which `edit_slack_integration` changes.\n\n## Linking in chat\n\nLink a monitor or policy with the Better Stack URL from the tool result rather than a bare ID.\n"
}

SHA-256 of public snapshot: 213a6a5dce03999fc531a358b3e6a308bf3ae79481f9435fb926fb0e0e27b251