> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/troubleshooting/service-tile.md).

# Service Tile

## Overview

This page explains which watches are included in the numbers shown on the service tiles.

## Watch count

The watch count appears in the top right of the tile under this icon.

The watch count is unaffected by watches in maintenance, but excludes those which are not being reported.

Moving around the tree changes the watch count to show only those watches contained in the selected folder or location.

## Number of issues

For service tiles, only watches in a red state are counted towards the number of issues. Green and amber watches are excluded.

In the watch status cards shown here, the 3 bearers labelled **Aberdeen, Albany** and **Alliance** are red and thus counted as watches with issues. Other watches are green or amber and thus not counted.

The total issues count excludes watches in maintenance.

## Tile calculations

This section explains the chart threshold calculations and tile/icon colours.

The chart shows the proportion of issues compared to the total number of "eligible" watches. The total number of eligible watches is the watch count less any watches currently in maintenance.

In the example shown above, there are 15 watches linked to the tile of which 5 are currently in maintenance. Thus a total of 10 watches are used to determine the colour of the tile and the threshold bar.

In this example the tile will be red if greater than 23% of watches have issues. In our case 4 watches out of 10 (40%) have issues so the tile and threshold bar are red.

Watches in maintenance do not change the colour of heat tiles.

## Stability, load and health indicators

Stability, load and health indicators use the same thresholds as the tile, as set in the Container dialog on the Tile tab. Because the tile changes colour based on the percentage of all issues, it's possible to have a red tile with 3 amber indicators (as shown below) or an amber tile with 3 green indicators (see image below right).

**Example 1:** In the example above there are 4 total issues on the tile. Hover shows 2 stability issues, 2 load issues and 3 health issues which sums to 7, not 4. This is because a single watch can have more than one issue.

**Example 2:** In the example below the amber threshold is 15%. If 10% of the container watches have red stability issues, 10% have red load issues, and 10% have red health issues, then the tile will be amber because 30% of watches are in a red state, which exceeds the 15% threshold. However all the indicators will be green as they are each below 15%.

*Amber tile with 3 green icons*


---

# 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://help.highlight.net/troubleshooting/service-tile.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.
