> 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/configuring-command-centre/viewer-configuration-overall-process/configuring-the-viewer-navigation-panel/spot-monitor-viewer/quick-tips-for-configuring-panels.md).

# Quick Tips for configuring Spot Monitor Panels

The "Panel Rules" allows you to determine what tiles are displayed based on the Alarm priority, the Alarms Event source (or sources) and whether the rule applies to a Single or Multiple Alarm source scenario.

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

**Single Alarm Source Rules**

* Single Alarm Source Rules apply to individual alarms which match the priority, and one of the event sources, (e.g. for a critical alarm on A **or** B **or** C **or** D).
* Multiple Alarms from the same Alarm Source (i.e alarm flooding) are treated as a Single Alarm Source.

**Multiple Alarm Source Rules**

Multiple Alarm Source Rules apply to a collection of alarms that match priority and event sources, (e.g. for a critical alarm on A **and** another critical alarm on B or C or D).

**Notes:**

* Where a Multi Source rule is configured a matching Single Source rule should also be configured.
* If an alarm matching a Multiple Source rule is manually sent to the spot monitor and the alarm does not match any "Single Source" rule then the Spot Monitor Viewer only displays the Event message, configured panels will not show.

**Alarms Event Sources**

* Single Source rules can have any number of event sources. Multiple Source rule have more than one source.
* Leaving the Event sources blank will apply the rule to **all** event sources ("Multiple Source" rules with no specified Event Sources should be lower in the Rules Panel).

**Assigning Panels to the Rule**

* A new or existing Panel can be assigned to the rule.
* Panel names must be unique within a Viewer.

**Panel Rule order**

* The order of the Rules is important as it determines which rule will be applied first to an incoming alarm.
* Starting at the top (the highest in the order) The alarm source and priority check through the rules until a matching rule is found and then check if there are additional (unprocessed) alarms with specified alarm sources that meet that criteria, the first match found is the rule applied to display the relevant panel.
* With "Multiple Source" Rules, the higher the Rule is in the list determines whether the Panel will be replaced with another of a Higher Rule Priority.
* Rules can be reordered using the up / down buttons.
* There is no column sorting within the Panel rule grid.

### Understanding Spot Monitor Behaviour

The Spot Monitor display is triggered automatically for alarms that match the criteria in the Panel Rules.

**Manual Mode**

A manually selected Alarm, meeting any "Single Source" Rule criteria can be displayed at any time effectively overriding the Automatic mode. An operator with the required privileges can send an alarm to the Spot Monitor through the Alarm Management Viewer.

**Automatic Mode**

* The panel will display until the alarm is processed or an alarm with a higher priority is presented.
* If the alarm is of the highest priority, the panel will display until the alarm is either processed or another alarm (of the same priority) triggers a "Multiple Source" Rule to display a Panel.
* When a Multiple Source Alarm Rule Panel is displayed, the Spot Monitor is not cleared until all alarms meeting the criteria are processed (or another "Multiple Source" Alarm Rule Panel with a higher **Rule** Priority is triggered).
* If there are no "Multiple Source" Rules configured, the first highest priority alarm panel displays until the alarm is processed.
* If there are no alarms meeting the rule criteria, then the Spot Monitor is blank.

|   | <p><strong>Example</strong><br>Rule 1 = Critical Priority, Multiple, Alarm Sources A (or/ +) B (or/ +) C (or/+) D. - Panel 1<br>Rule 2 = Critical Priority, Single, Alarm Source A or B or C or D - Panel 2</p><ol><li>Critical alarm for A apply rule 2</li><li>Critical alarm for A + B, apply rule 1 (Multiple Alarm source rule)</li><li>Critical alarm for Z - meets no rule (Note Z is not a specified alarm source.)</li><li>Critical alarm A was processed, apply rule 2 (B single alarm source)<br></li></ol> |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

* **Multiple Alarm Tile Context**

  When a Panel is displayed for a Multiple Alarm source rule, the first, (i.e. oldest unprocessed) alarm source is the context for the tile contents.

  For instance:

  * If camera tiles are configured, the camera's associated with the first alarm source are displayed.
  * If the first alarm is processed but there are still multiple alarms on the same panel, it refreshes to display the oldest unprocessed alarm and so on.


---

# 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/configuring-command-centre/viewer-configuration-overall-process/configuring-the-viewer-navigation-panel/spot-monitor-viewer/quick-tips-for-configuring-panels.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.
