# Monitoring

URL: /code/systems/monitoring · Id: `system:monitoring`

> Monitoring captures errors, logs and traces, checks uptime and scheduled jobs, and ties each failure to the Version that caused it.

Monitoring captures errors, logs and traces, checks uptime and scheduled jobs, and ties each failure to the [Version](/business/nouns/version) that caused it. [Agents](/business/nouns/agent) triage and fix around the clock; no human carries a pager.

## Summary
| Part | This System |
| --- | --- |
| Group | Moves to Code |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Front: offered from a Startup’s first days |

You can ask:

- “Is the site up?”
- “Page me when checkout breaks”
- “Which release broke this?”

## What you get
| Part | This System |
| --- | --- |
| Starts | On for every Startup at creation, with nothing to install. |
| Built from | [Observability](/code/platform/observability), [Event streams](/code/platform/event-streams), [Functions](/code/platform/capabilities/functions), [Workflows](/code/platform/workflows) |

## Nouns it owns
| Noun | Definition |
| --- | --- |
| [Monitor](/business/nouns/monitor) | A Monitor is a scheduled check on something outside a Startup’s control, such as uptime, a Keyword’s rank or an AI answer, recording Events. |
| [Incident](/business/nouns/incident) | An Incident is an Issue where an Interface or Site fails Customers in production, tracked from detection to postmortem. |

## Verbs
| Verb | Object | Approval | Event |
| --- | --- | --- | --- |
| [Monitor.create](/business/nouns/monitor/create) | [Monitor](/business/nouns/monitor) | None | `Monitor.created` |
| [Monitor.check](/business/nouns/monitor/check) | [Monitor](/business/nouns/monitor) | None | [`Monitor.checked`](/business/events/Monitor.checked) |
| [Incident.open](/business/nouns/incident/open) | [Incident](/business/nouns/incident) | None | [`Incident.opened`](/business/events/Incident.opened) |
| [Incident.acknowledge](/business/nouns/incident/acknowledge) | [Incident](/business/nouns/incident) | None | [`Incident.acknowledged`](/business/events/Incident.acknowledged) |
| [Incident.resolve](/business/nouns/incident/resolve) | [Incident](/business/nouns/incident) | None | [`Incident.resolved`](/business/events/Incident.resolved) |

## Events
| Direction | Event | How |
| --- | --- | --- |
| Emits | `Monitor.created` | By [Monitor.create](/business/nouns/monitor/create) |
| Emits | [`Monitor.checked`](/business/events/Monitor.checked) | By [Monitor.check](/business/nouns/monitor/check) |
| Emits | [`Incident.opened`](/business/events/Incident.opened) | By [Incident.open](/business/nouns/incident/open) |
| Emits | [`Incident.acknowledged`](/business/events/Incident.acknowledged) | By [Incident.acknowledge](/business/nouns/incident/acknowledge) |
| Emits | [`Incident.resolved`](/business/events/Incident.resolved) | By [Incident.resolve](/business/nouns/incident/resolve) |

## States
None.

## Who operates it
| Part | This System |
| --- | --- |
| Accountable | [Reliability Engineer](/agents/engineering/reliability-engineer) |
| Team | [Engineering Team](/agents/engineering) |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | `supervised` |
| Also calls its Verbs | [Security Engineer](/agents/engineering/security-engineer) |

## Approvals and limits
None.

## Processes that use it
| Process | How it uses it |
| --- | --- |
| [Incident response](/workflows/processes/incident-response) | A step calls [Incident.acknowledge](/business/nouns/incident/acknowledge) |
| [Vulnerability disclosure](/workflows/processes/vulnerability-disclosure) | A step calls [Incident.open](/business/nouns/incident/open) |

## Rail underneath
None.

## Views and dashboards
| View | Shows | Metrics |
| --- | --- | --- |
| The [Reliability Engineer](/agents/engineering/reliability-engineer)’s view | The Metrics its accountable Role answers for. | [Restore drills passed](/agents/engineering#restore-drills-passed) |

## Access
What each Access level may call here.

| Access level | May call |
| --- | --- |
| `owner` | Every Verb (13) |
| `admin` | Every Verb (13) |
| `member` | Every Verb (13) |
| `viewer` | Read only (4 of 13) |

## Import and export
None.

## Fees and pricing
None.

## Availability and limits
| Part | This System |
| --- | --- |
| Status | Beta: it works, and its Verbs may still change |

## Compliance notes
Controls it carries:

- [Log completeness](/systems/trust-and-governance/controls/log-completeness)
- [Deploy reconciliation](/systems/trust-and-governance/controls/deploy-reconciliation)
- [Append-only records](/systems/trust-and-governance/controls/append-only-records)
- [Anomaly monitoring](/systems/trust-and-governance/controls/anomaly-monitoring)
- [Incident handling](/systems/trust-and-governance/controls/incident-handling)
- [Capacity headroom](/systems/trust-and-governance/controls/capacity-headroom)
- [Action completion](/systems/trust-and-governance/controls/action-completion)

## Related Systems
- [Status pages](/systems/status-pages): also holds [Incident](/business/nouns/incident)

## Example
A [Dataset API](/products/templates/dataset-api) of flight delays starts failing 3% of calls at 2am. Monitoring groups the errors, ties them to the Version deployed at 1:40 and rolls it back. The [Reliability Engineer](/agents/engineering/reliability-engineer) Agent opens an [Issue](/business/nouns/issue) with the failing trace, and [Status pages](/systems/status-pages) posts the [Incident](/business/nouns/incident) and its resolution.