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

# Service Objectives

A service objective is an availability target, such as 99.9% over one month, agreed with the owner of a service. It covers one or more HTTP monitors and is measured from their probe results. Use this screen to define objectives and to see how each one is doing.

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

{% hint style="info" %}
Requires the **Service Health** licence. Objectives measure HTTP monitors only; AWS, MuleSoft and Azure resource monitors are not measured against an objective.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FFVj0sid4C7yRRn9KFpNO%2Fv2-sh-objectives.png?alt=media&amp;token=3168ef2b-02b5-4a75-958d-7e6d75b3b9a3" alt="Service objectives with the Monitors letting objectives down chart and the Measured performance donut"><figcaption><p>Service objectives and their charts</p></figcaption></figure>

## Charts

| Chart                                           | What it shows                                                                                                                                                                                                     |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Monitors letting objectives down**            | Each monitor that was up less often than an objective it belongs to requires, furthest behind first, with how far below target it is.                                                                             |
| **Measured performance**                        | A donut of all current objectives: **Meeting target**, **Below target** and **No data yet**, using each objective's availability over the last 24 hours. Click a slice to list its objectives and their monitors. |
| **Objectives meeting their target, day by day** | For each of the last 30 days, how many objectives kept their target (**Met target**) and how many did not (**Below target**). Empty days had nothing measured.                                                    |

Click **Show data table** on a chart to see its values as a table.

{% hint style="info" %}
Availability is measured from probe results, less maintenance windows. The service counts as down while any covered monitor is down; overlapping outages are counted once. Precision is one probe interval.
{% endhint %}

## Service Objectives List

Use the **Status** filter to show **Current** or **Archived** objectives; **Save filters** keeps a combination to pick again from **Saved filters**. The list has a search box (objectives or owners), **Refresh**, **Columns** and **Export**. Expand a row to see its measurements and monitors.

| Column        | Description                                                                                                                                                                                                               |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Objective** | Objective name and owner.                                                                                                                                                                                                 |
| **Target**    | The availability target and window, and the allowed downtime it implies (a planning value).                                                                                                                               |
| **Status**    | **Met**, **At risk**, **Missed** or **Not measured yet**, and **Archived** for an archived objective.                                                                                                                     |
| **Monitors**  | Number of covered monitors, or **Planning objective** when it covers none. Click the number to list the monitors with their status, downtime and last observation; **Remove from objective** takes one off the objective. |
| **Actions**   | **Edit objective**, **Export objective**, and **Archive objective** or **Restore objective**.                                                                                                                             |

An expanded row shows **Availability**, **Downtime** against the allowed downtime, **Error budget left** and **Average burn**, followed by the covered monitors with the most downtime first.

{% hint style="warning" %}
You cannot archive an objective while it covers enabled monitors. Remove them from the objective first (**Remove from objective**). Archiving does not change any monitor or schedule.
{% endhint %}

## Define a Service Objective

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FDR5yFzJOUPpzO6JTXzs2%2Fv2-sh-objective-define.png?alt=media&amp;token=749492b7-e119-4648-9d28-e52abe044556" alt="Define a service objective form"><figcaption><p>Define a service objective</p></figcaption></figure>

1. Click **Define objective**.
2. Fill in the fields below. The **Allowed downtime · planning value** box shows the minutes of downtime your target allows over the window.
3. Click **Create objective**.

| Field                                    | Description                                                                                                       |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Service objective name**               | **Required.** Up to 160 characters.                                                                               |
| **Responsible owner or team**            | **Required.** Who reviews the objective. Up to 160 characters.                                                    |
| **Availability target (%)**              | **Required.** Between 90 and 100.                                                                                 |
| **Rolling evaluation window**            | **Required.** A number of days, months or years, from 1 day to 3 years. Months count as 30 days and years as 365. |
| **Service boundary and review criteria** | What the probe proves, how to treat missing observations and maintenance, and who verifies recovery.              |

An objective created here covers no monitor yet. Saving it does not start a monitor or send a notification.

## Add Monitors to an Objective

You add monitors from the monitor side:

1. Open [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md).
2. In the **Objectives** column of an HTTP monitor, click **Set objective**, or open the monitor and click **Define a service objective for this monitor** or **Add another service objective**.
3. Choose a **Service objective**, or click **Define objective** to create one for this monitor.

To move a monitor to another objective, click **Change objective** next to the objective name in the monitor's **Objectives** column. To take it off, click **Remove from objective** there, or in the objective's list of covered monitors. Removing a monitor does not change the monitor, its results or incidents. An objective covers up to 50 monitors.

{% hint style="warning" %}
You need a role that can create or edit monitors to define, edit, archive objectives and add monitors to them.
{% endhint %}

## Next Steps

* [Monitors](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/monitors.md): add monitors to an objective.
* [Maintenance Windows](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/service-health/maintenance-windows.md): keep planned work out of the measurement.
* [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/service-objectives.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.
