> 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.md).

# Service Health

Service Health checks that your APIs and integration runtimes answer as expected, shows how close each service is to its availability target, and tells the people who depend on a service what is happening. Health checks run on your agent, from its network.

Open it from **Workspaces** → **Service Health** in the sidebar. Every Service Health screen has the same tabs at the top: **Service readiness**, **Monitoring coverage**, **Service objectives**, **Monitors**, **Status pages**, **Categories**, **Runbooks** and **Maintenance windows**.

{% 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%2FpuWISVViQMkiRvigNwAE%2Fv2-sh-status-owner.png?alt=media&amp;token=95c769f8-af90-4465-940c-44d975154eff" alt="Owner view of a status page with its current status and the incidents happening now"><figcaption><p>A status page as its owner sees it</p></figcaption></figure>

{% hint style="warning" %}
The tabs you see depend on your role. For example, a role that can view status pages but not monitors sees only status pages, runbooks and maintenance windows.
{% endhint %}

## Screens in Service Health

| Page                                                                                                                                              | What you do there                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| [Service Readiness](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/service-readiness.md)     | See whether monitoring is running, what needs attention now and which applications still have no monitor.     |
| [Monitoring Coverage](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitoring-coverage.md) | Go through your deployed applications, link a monitor to each one and set up monitors in bulk or by policy.   |
| [Service Objectives](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/service-objectives.md)   | Agree availability targets with an owner and see which monitors are letting them down.                        |
| [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md)                       | Create, inspect, enable and disable HTTP, AWS, MuleSoft and Azure monitors, including how a monitor signs in. |
| [Status Pages](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/status-pages.md)               | Publish the health of a set of monitors on a public or private status page.                                   |
| [Categories](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/categories.md)                   | Group monitors under headings that several status pages can share.                                            |
| [Runbooks](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/runbooks.md)                       | Write the response procedure a team follows when a monitor fails.                                             |
| [Maintenance Windows](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/maintenance-windows.md) | Plan maintenance so checks inside the window do not count as down, and announce it to subscribers.            |

## How the Pieces Fit Together

1. A **monitor** checks one endpoint or resource and records each result.
2. A **category** groups monitors; a **status page** shows categories, monitors added directly, or both.
3. A **service objective** sets an availability target for one or more monitors.
4. A **runbook** is linked to a monitor so responders know what to do when it fails.
5. A **maintenance window** covers monitors, categories or status pages while planned work runs.

## Next Steps

* [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md): create your first monitor.
* [Monitoring Coverage](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitoring-coverage.md): find applications that are not monitored yet.
* [Status Pages](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/status-pages.md): share service health with your audience.


---

# 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.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.
