Operations
Shows the platform's component health, service objectives and open incidents. The platform operator runs checks and manages incidents here.
What's on this screen
- Four figures at the top: Components healthy, Blind spots (required components with no live measurement), Open incidents (with how many have no owner) and Objectives at risk (more than half the error budget spent). A blind spot is also said in a notice above them.
- The page is Operations in the menu and follows the scope switcher: in a Tenant it shows that Tenant's installs (see that help); elsewhere the platform's health.
- Component health: whether each component is required or optional, its status, any reason codes and the time of the last check.
- Service objectives: each objective's target ratio, window, error budget spent and measured value.
- Open incidents: severity, title, status, whether someone has taken it on, affected components and timeline. Below, the five most recently resolved incidents.
| Status | What it means |
|---|---|
| healthy | The last valid check is within thresholds. |
| degraded / lagging / saturated | Working, but a threshold was crossed; the reason code says which. |
| in maintenance | The component has been put into maintenance. |
| blocked / failed | The component cannot do its job. |
| unknown | There is no valid live check. Never counted as healthy. |
What you can do
- Check now: checks the components right away. A check is valid for 15 minutes. Today only the database and the audit pipeline are checked; the others stay unknown.
- Open new incident: open an incident with a title, severity (SEV0–SEV4, security, privacy) and affected components.
- Take on: become the incident's manager; the incident moves to ‘identified’.
- Close as resolved: close the incident. A closed incident cannot be taken on again.
Keep in mind If a required component has no live check, a blind spot warning appears at the top. It means the status is unknown, not that there is no problem.
Tip The screen works only while the console is in the platform scope. Viewing requires operations.read in the platform; checks and incident actions require operations.write. If you are in a Tenant scope, you get a link to that Tenant's operations screen.