> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/alarm-viewer/determining-alarm-priorities.md).

# Determining alarm priorities

The priority of each Alarm is indicated by the colour of the bar that appears at the beginning of each row. The priority of an alarm can be determined by either:

* hovering over the coloured bar beside the alarm.

  A pop-up displays indicating the Event Priority of the alarm. This example shows a **Medium High Priority** alarm.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c3d1d3514e74323b0a6f4781782af175bb8b6f0c%2Falarmpriority_hover.png?alt=media)

OR

* clicking on an alarm in the list (so it becomes highlighted).

  The corresponding coloured block (in the set of coloured blocks above the Alarm List) expands to display the Event Priority of the alarm selected, along with the number of alarms of that priority.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-14775eab85759b5b9fcaa865d3538d4ea0c7daf0%2Falarmpriority_selectalarm.png?alt=media)

The set of coloured blocks above the Alarm List provides a summary of the number and priority of the alarms in the Viewer. There is a block for every Event Priority, (i.e. even if there are no alarms of a particular priority, the outline of the block still displays in priority order).

**Note:** If you click on one of the coloured blocks, the system scrolls the list so the most recent unacknowledged alarm of that priority is selected and becomes visible.


---

# 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.security.gallagher.com/knowledge-hub/command-centre-client/using-command-centre/working-with-viewers/alarm-viewer/determining-alarm-priorities.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.
