A component is a service whose state is published, such as a web application, an API or a connected platform. Each component has a name, an optional description and link, and an icon from a list of 97 icons. ## States A component always has one of five states. Each state has its own colour and icon, so the state never depends on colour alone: - Operational. - Degraded performance. - Partial outage. - Major outage. - Under maintenance. The state changes through an operator, an incident, a maintenance, a probe or an inbound integration. Every change is kept with its source and moment, and is listed under [[Invantive Cloud Status/Menu/Components|Components]]. An operator can hold a state against the probes, so a probe does not change it until the operator releases it. ## Overall State The top of a page shows the overall state: the worst state of the components that influence it. Per component the operator sets whether it influences the overall state. Typically production components do and sandbox, test and internal components do not. A group shows the worst state of its components in its header, when the group state is switched on for the group. ## Groups A group collects components under a title on one page, in a fixed order. A group can be collapsed by default, which keeps a long page short. ## Tags A tag has a code, a name, a colour and an icon. Tags are assigned to components and groups. Readers filter the history by tag and subscribe to the components of a tag. The contrast of the colour of a tag is checked when it is saved. ## Uptime and History Per component the operator switches on or off what readers see: - Uptime bars: one bar per day over 90 days, in the colour of the worst state of that day. - Uptime percentages over 30, 90 and 365 days. - A graph of the response time measured by the probes. - The public history of the incidents of the component. Planned maintenance does not count against the uptime.