Skip to main content
Monitors and dashboards are the two artifacts the agent builds. You describe what you want in chat; the agent builds it.

​
Dashboards

A dashboard is a live view of your telemetry. You ask for one in plain language:
The agent queries your telemetry to confirm the data exists, then builds the dashboard. It appears in the side pane next to the chat and refreshes on its own. Saved dashboards are listed on the Dashboards screen. To change one, ask — the agent edits it in place:

​
Monitors

A monitor watches your telemetry and reports one of three states: healthy, firing, or unknown. It is more than a threshold: in one check it can look across your traces, metrics, and logs, read your connected repository, and remember what it saw last time — enough to notice, for example, that errors climbed right after the latest deploy. You ask for one in plain language:
The Monitors screen lists every monitor with its schedule, current state, description, and — when firing — the reason. To change a monitor’s threshold, schedule, or logic, ask the agent. The three states:
  • healthy — the condition being watched is fine.
  • firing — the condition tripped. A firing always carries a short, specific reason.
  • unknown — the check could not run (failed query, missing data).
The screen also shows pending for a new monitor that has not checked yet, and failed for one that could not start — ask the agent to fix it.

​
Going live

A monitor is live as soon as the agent finishes writing it: it appears on the Monitors screen and starts checking. Edits take effect the same way.

​
Arming a monitor

An unarmed firing is only recorded. An armed monitor escalates: a firing opens an incident, and the agent investigates it against live telemetry. If the alert is a false alarm, the agent tunes the monitor; if it is real, it opens a pull request with a proposed fix. Your team reviews and approves what ships. You arm a monitor by asking:
Incidents and Slack covers what happens after a firing becomes an incident.