Skip to main content

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.

Your status page shows two kinds of incident updates: the ones Tallwatch derives from your monitors, and the ones you write by hand. Manual updates are how you communicate during an outage or planned maintenance, in your own words.

​
Automatic updates

When a monitor on the page opens an incident, the page reflects it without any action from you. The component goes red, and the incident shows in the feed. When it resolves, the page updates again. For a lot of situations this is all you need.

​
Post a manual update

When you want to explain what’s happening, post your own incident:
1

Create the update

On the status page, add an incident. Give it a title and a body. The body takes Markdown, so you can add links and formatting.
2

Set severity and status

Pick a severity (minor, major, critical, or maintenance) and a status. Statuses move through investigating, identified, monitoring, and resolved.
3

Mark affected components

Select which components this affects so the page shows impact in the right place.
4

Publish, then update as you go

Publish it, then edit the status as the situation changes. Move it to resolved when the work is done.
Use the maintenance severity for planned work so visitors can tell a scheduled deploy apart from a real outage. Pair it with a maintenance window so the monitors don’t open their own incidents during the work.

​
Email subscribers

Visitors can subscribe to a status page with their email to follow updates.
Subscriptions are partial in this release. The subscribe form captures the address, but the confirmation email isn’t sent yet, so subscribers aren’t fully opted in and update emails don’t go out. Treat the public page itself as the reliable channel for now. Slack and RSS subscriptions are not available yet.