> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/categories.md).

# Categories

A category groups monitors under one heading, such as "Payments" or "Order APIs". Categories are shared: a change to a category reaches every status page that uses it. A category is optional; a status page can also show monitors added to it directly.

Open it from **Workspaces** → **Service Health** → **Categories** in the sidebar.

{% hint style="info" %}
Requires the **Service Health** licence.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FHokOjsKSpsMSSmsATa6u%2Fv2-sh-categories.png?alt=media&amp;token=da7ab474-a507-43e8-9f0a-ab827f0712af" alt="Categories list with status and monitor counts"><figcaption><p>Categories</p></figcaption></figure>

## Categories List

Use the **Status** filter to show **All**, **Needs attention** or **Unknown** categories; **Save filters** keeps a combination to pick again from **Saved filters**. The list has a search box, **Refresh**, **Columns** and **Export**.

| Column       | Description                                                                                  |
| ------------ | -------------------------------------------------------------------------------------------- |
| **Category** | Category name, with a **Managed by** tag when a monitoring policy maintains it.              |
| **Status**   | Recomputed every minute from each monitor's last check. An empty category stays **Unknown**. |
| **Monitors** | Number of monitors in the category.                                                          |
| **Actions**  | **Manage monitors** and delete.                                                              |

## Create a Category

1. Click **Create category**.
2. Enter the **Category name** (**Required**, up to 100 characters).
3. Optionally pick **Monitors** to add now. You can change them later.
4. Click **Create category**. The category opens so you can keep adding monitors.

## Manage a Category's Monitors

1. Click **Manage monitors** on the row.
2. In **Monitors in this category**, search for a monitor and click **Add monitor**.
3. To take a monitor out, click **Remove monitor** on it. The monitor itself is unchanged.

The drawer also shows the category's status, monitor count and when it last changed. Click **Rename category** to change its name.

{% hint style="info" %}
Only public, enabled monitors in a category appear on a public status page.
{% endhint %}

A category created by a monitoring policy shows **Maintained by**: the policy adds monitors of its type as it creates them, including any you removed. Click **Take over** to stop that.

{% hint style="warning" %}
You need a role that can create monitors to create a category, a role that can create or edit monitors to add monitors to it, a role that can edit monitors to rename it or take it over, and a role that can delete monitors to remove monitors from it or delete it.
{% endhint %}

## Next Steps

* [Status Pages](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/status-pages.md): add the category to a status page.
* [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md): create the monitors a category groups.
* [Service Health](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health.md): see how the screens fit together.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/categories.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
