> 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/service-readiness.md).

# Service Readiness

Service readiness is the start page of Service Health. It shows whether checks are running, how many monitors need attention, and which deployed applications still have no monitor.

Open it from **Workspaces** → **Service Health** → **Service readiness** 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%2FxZNFHlPUgsgMztz76hHy%2Fv2-sh-readiness.png?alt=media&amp;token=c3259244-10dd-4e10-af6d-4d4abea46489" alt="Service readiness page with coverage tiles, probe signals and readiness steps"><figcaption><p>Service readiness</p></figcaption></figure>

## Probe Notice

A red notice appears at the top when checks have stopped:

| Notice                                                              | What it means                                                                         |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Nothing has probed since** a date, or **Nothing has probed yet.** | The health check schedule has not run recently. Click **Open schedules** to check it. |
| **No API Health Check schedule is active.**                         | No schedule runs your monitors. Click **Open schedules** to create or enable one.     |
| **Probe results are refused**                                       | The checks allowance of your licence is used up. Click **Review licence details**.    |

## Tiles

| Tile                          | Description                                                                                                                                                                                               |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Applications in scope**     | Deployed applications you can access. Click it to open [Monitoring Coverage](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitoring-coverage.md). |
| **Linked monitoring**         | Applications with an enabled HTTP monitor or a linked resource collector. Click it to see them in Monitoring Coverage.                                                                                    |
| **Coverage gaps**             | Applications with no enabled HTTP monitor or resource collector. Click it to see them in Monitoring Coverage.                                                                                             |
| **Time to restore (90 days)** | Mean and 90th percentile time to recover from resolved outages, less maintenance. It shows **Not measured yet** when probes run less often than every 15 minutes.                                         |

## Service Readiness Panel

The panel shows three live signals: **Probe runs · last 24 h**, **Monitors down or degraded now** and **Incidents opened · last 24 h**.

* **Plan monitoring coverage** opens [Monitoring Coverage](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitoring-coverage.md).
* **Inspect monitors** opens [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md).

Below it, four numbered steps count what is in place across the whole workspace:

| Step                     | Counts                               |
| ------------------------ | ------------------------------------ |
| **Know the service**     | Applications you are allowed to see. |
| **Connect a monitor**    | Enabled HTTP monitor versions.       |
| **Collect observations** | Probe runs in the last 24 hours.     |
| **Prepare a response**   | Response runbooks.                   |

## Start With an Actual Application

This list shows a few applications that have no linked monitor yet, with their type, organization and environment. Click **View all applications →** to see the full list in Monitoring Coverage.

| Button                | What it does                                                                                                                                                                                                             |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Configure monitor** | Opens the HTTP monitor form, already linked to this application. See [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md#create-an-http-monitor). |
| **Open monitor**      | Shown when the application already has a monitor. Opens the **Monitor evidence & configuration** drawer.                                                                                                                 |

{% hint style="warning" %}
You need a role that can view monitors to see the tiles and lists. Without it, the page offers only links to status pages, runbooks and maintenance windows. To configure a monitor you need a role that can create monitors.
{% endhint %}

## Next Steps

* [Monitoring Coverage](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitoring-coverage.md): close the coverage gaps.
* [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md): inspect what each monitor last observed.
* [Runbooks](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/runbooks.md): give responders a procedure.
* [Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.md): check the schedule that runs health checks.


---

# 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/service-readiness.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.
