Monitoring
Monitoring captures errors, logs and traces, checks uptime and scheduled jobs, and ties each failure to the Version that caused it.
Agents 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, Event streams, Functions, Workflows |
Nouns it owns
| Noun | Definition |
|---|---|
| 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 | 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 | Monitor | None | Monitor.created |
| Monitor.check | Monitor | None | Monitor.checked |
| Incident.open | Incident | None | Incident.opened |
| Incident.acknowledge | Incident | None | Incident.acknowledged |
| Incident.resolve | Incident | None | Incident.resolved |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Monitor.created | By Monitor.create |
| Emits | Monitor.checked | By Monitor.check |
| Emits | Incident.opened | By Incident.open |
| Emits | Incident.acknowledged | By Incident.acknowledge |
| Emits | Incident.resolved | By Incident.resolve |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Reliability Engineer |
| Team | Engineering Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | supervised |
| Also calls its Verbs | Security Engineer |
Approvals and limits
None.
Processes that use it
| Process | How it uses it |
|---|---|
| Incident response | A step calls Incident.acknowledge |
| Vulnerability disclosure | A step calls Incident.open |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Reliability Engineer’s view | The Metrics its accountable Role answers for. | 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
- Deploy reconciliation
- Append-only records
- Anomaly monitoring
- Incident handling
- Capacity headroom
- Action completion
Related Systems
- Status pages: also holds Incident
Example
A 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 Agent opens an Issue with the failing trace, and Status pages posts the Incident and its resolution.