Tallwatch has seven monitor types. HTTP and HTTPS run end-to-end today. The rest are creatable in the dashboard but not yet executed by the production probers, so treat them as preview for now (details below).Documentation Index
Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt
Use this file to discover all available pages before exploring further.
Fully supported
Requests a URL and checks the response. Set the method, the status codes you accept, request headers and body, and assertions on the response (latency, body content, JSON path, headers). This is the path consensus, incidents, and alerting are built and tested against. See Creating monitors.
Preview types
These types exist in the create form and schedule checks, but the production probers run on Cloudflare Workers, which can’t open raw TCP, ICMP, or socket connections. Until a non-Worker prober is deployed, a non-HTTP check returnsdegraded and the monitor sits at unknown rather than reporting real up/down. Don’t rely on them for paging yet.
Opens a connection to a host and port.
Sends echo requests to a host.
Resolves a hostname and checks the record (A, AAAA, CNAME, MX, TXT), optionally against an expected value.
Inspects a certificate and warns before expiry.
Fetches a URL and checks whether a keyword is present or absent. (The HTTP type already covers keyword checks through body assertions, which do run today.)
Expects your job to call a URL on a schedule, and alerts when a ping is late. Passive, so it has no “test” action.
Need a keyword or content check now? Use an HTTP monitor with a
body_contains or body_regex assertion. Those evaluate on the real HTTP path and are fully supported.