Components and statuses
Components and groups, the five renamable statuses, one-click status changes, visibility, how 90-day uptime is derived, and URL monitors.
A status page is built from components, the individual services you report on, optionally organized into groups. You manage the whole board from the Status view of the workspace.
The board
- Components are the rows visitors see; each carries a current status.
- Groups hold components. Add a component inside a group from the inline row at the bottom of the group, or move one in from its menu.
- Reorder by dragging, with the Move up / Move down / Move to group actions, or with Alt+Up and Alt+Down on a focused row.
- Only leaf components count toward the free-tier cap; groups are free.
- Components and groups carry an optional description, shown under the name on the public page.
A group's status rolls up to the worst of its children automatically. From a group row you can either set every component inside it at once, or pin the group to a status of its own and later return it to the rollup.
The five statuses
Every component is in one of five statuses. The labels are renamable per page (Settings, Advanced); the colors and icons are fixed so visitors learn them once:
| Status | Default label | Color |
|---|---|---|
operational | Online | green |
degraded | Degraded | yellow |
partial | Partial Outage | orange |
outage | Outage | red |
maintenance | Maintenance | blue |
The page's overall headline ("All Systems Operational", and so on) is derived from the worst component status and is also renamable.
Changing a status
- One click on the board. Every row has a five-icon toggle. The change is live for visitors within a few seconds. If you take a component off Online and no incident covers it, the workspace offers to open an incident for it, or to add it to an incident that is already open.
- From an incident. Posting an incident or an update sets the status of the affected components, and resolving restores them (see Incidents).
- From a monitor or the Reporting API.
All of these count toward uptime.
Visibility
Each component has a visibility setting: Always shown, Only when degraded (it appears on the page only while it is not Online), or Hidden. Hidden components still roll up into their group and into the overall headline, so a hidden dependency can still turn the page red. Each component can also show or hide its uptime bar.
Uptime
Each leaf component can show a 90-day uptime bar. Uptime is derived from every status change, whichever way it happened: a one-click change, an incident, a monitor, or the API. A component counts as down while it is in Degraded, Partial Outage or Outage. Maintenance does not count as downtime, so a planned window stays blue in the bar instead of denting your numbers. The page header shows the average across components.
Monitors
Any component can have a URL monitor: Hep.gg requests the URL on a schedule (every 3, 5, 10 or 15 minutes; every minute on Prime), treats a 2xx or your expected status code as up, and after the number of consecutive failures you choose flips the component to the status you choose. With auto-incident on, the monitor also opens an incident for you and resolves it when the URL recovers; if an incident is already open for that component, the monitor posts to it instead of opening another, and it only ever resolves incidents it opened itself. Set a monitor up from the component's sheet or the Monitors view, where you also see the last check, its result and latency, the last error if any, a 24-hour latency chart, and a Check now button.