--- title: "Configure Alarms in a Role" slug: "configure-alarms-in-a-role" description: "Turn alarms on or off in a SysTrack role, set their limits and times, and select time windows, notification profiles, and action profiles." status: "update" updated: 2026-10-26T15:14:02Z published: 2026-10-26T15:14:02Z canonical: "documentation.lakesidesoftware.com/configure-alarms-in-a-role" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure Alarms in a Role In Configure, on the **Alarms** tab of a role, you turn alarms on or off, set their limits and times, and select a **Time Window**, a **Notification** profile, and an **Action** profile. Notification profiles and action profiles are separate. You select each one for a category or for a single alarm. The **Alarms** tab is on the **Roles** page (**Configure** > **System Configuration** > **Roles**). ## Prerequisites - A role that you can edit. Factory roles and password-protected roles cannot be edited. - The notification profiles, action profiles, and time windows that you want to use. See [Alarm Notifications](/documentation/docs/alarm-notifications), [Alarm Actions](/documentation/docs/alarm-actions), and [Alarm Time Windows](/documentation/docs/alarm-time-windows). ## Alarm Categories on the Alarms Tab The **Alarms** tab groups the alarms into 20 categories. The article for each category describes its alarms, an example, and the default values: - [Applications](/documentation/docs/application-alarms) - [Boot Time](/documentation/docs/boot-time-alarms) - [Changes](/documentation/docs/changes-alarm) - [Latency](/documentation/docs/latency-alarms) - [Memory Leaks](/documentation/docs/memory-leaks-alarms) - Performance: Blast - Performance: Blast (Pre 7.3) - Performance: Blast VC (Pre 7.3) - [Performance: Disk](/documentation/docs/performance-disk-alarms) - [Performance: GPU](/documentation/docs/performance-gpu-alarms) - [Performance: ICA](/documentation/docs/performance-ica-alarms) - [Performance: Network](/documentation/docs/performance-network-alarms) - [Performance: Other](/documentation/docs/performance-other-alarms) - [Performance: PCoIP](/documentation/docs/performance-pcoip-alarms) - [Performance: Remote FX](/documentation/docs/performance-remotefx-alarms) - [Performance: System](/documentation/docs/performance-system-alarms) - [Performance: VMware Host Disk](/documentation/docs/vmware-performance-host-disk-alarms) - [Performance: VMware Host System](/documentation/docs/performance-vmware-host-system-alarms) - [Security](/documentation/docs/security-alarms) - [VMware](/documentation/docs/vmware-alarms) ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(474).png?sv=2026-02-06&spr=https&st=2026-11-03T05%3A34%3A29Z&se=2026-11-03T06%3A34%3A29Z&sr=c&sp=r&sig=2%2FPUWfsov%2F%2BOEikjfBchG1smiD7VxbQYGNoFFtJraCM%3D) ## Turn On Alarms and Change Their Settings Use this procedure for every alarm category on the **Alarms** tab of a role. Some categories have fewer columns or more settings, as described in Alarms Tab Columns and Defaults below. 1. In Configure, go to **System Configuration** > **Roles**, and select the role. 2. Click the **Alarms** tab. 3. Select or clear the check box to the left of the category. > [!CAUTION] > **WARNING**: In **Performance: Disk**, **Performance: Network**, **Performance: System**, and **Performance: VMware Host Disk**, the category check box turns every alarm in the category on or off. It replaces the on or off choice that you made for single alarms in the category. 4. To give every alarm in a category the same value, set the value in the blank first row of the category. > [!CAUTION] > **WARNING**: A value that you set in the blank first row of a category is copied to every alarm in the category. It replaces the values that you set on single alarms in that category. 5. To turn a single alarm on, select the check box to the left of the alarm. Depending on the alarm, it triggers when the value is either above or below the configured limit for the specified time period. If you clear the check box, the SysTrack Agent ignores the limits and generates no alarm. The agent still tracks data for this setting. 6. To change a **Red Limit** or **Red Time (s)** value, click the value, and then enter the new value. 7. In **Time Window**, select the time window for the alarm. 8. To change a **Yellow Limit** or **Yellow Time (s)** value, click the value, and then enter the new value. 9. In **Notification**, select the notification profile to use when the alarm triggers. 10. In **Action**, select the action profile to use when the alarm triggers. 11. Click **Save Changes** at the top right of the **Roles** page. **Save Changes** saves all changes on the **Roles** page, on every tab. > [!NOTE] > **NOTE**: An alarm that passes through a Yellow state and achieves a Red state is considered to be in both Yellow and Red alarm status until the condition value is within the limits. ## Alarms Tab Columns and Defaults The **Alarms** tab shows the column headings on the category rows only. The columns are in this order: **Red Limit**, **Red Time (s)**, **Time Window**, **Yellow Limit**, **Yellow Time (s)**, **Notification**, and **Action**. Times are in seconds. Every alarm starts with these factory values: - **Time Window**: **18x6** - **Notification**: **None** - **Action**: **None** The factory limits, times, and on or off state of each alarm are in the **Default** column of the category article. A role can change them. Some categories differ from this layout: - **Applications**, **Changes**, and **Security** have no limits. Their rows show only **Time Window**, **Notification**, and **Action**. - **Boot Time** alarms have only a **Red Limit**, in milliseconds. The tab shows no time for them. See [Boot Time Alarms](/documentation/docs/boot-time-alarms). - **Memory Leaks**, **Latency**, and **Performance: Other** have more settings. Their articles describe them. ## Check the Alarm Settings Systems receive the changed role with their configuration during routine processing. To check the settings and apply them right away: 1. On the **Roles** page, select the role and click the **Alarms** tab. The values that you saved show on the alarm rows. 2. Go to **SysTrack Settings** > **Administration**. In the **Operations** panel, under **Command Dashboard**, select the systems, select **Read Configuration**, and click **Run**. The systems read their configuration, with the changed role, right away. ## Troubleshooting Alarms ### Alarms Stop Alerting for New Events After an endpoint has collected many events, its alarms can stop alerting for new events. SysTrack collects a maximum number of new events (default 300). After that, it ignores new events until the pending alarms are cleared (default 30 days). You can change both values in the **Events** settings of the role. Higher values can affect performance, especially when forwarding is turned on. See [Alarms Are Not Alerting for New Events](/documentation/docs/alarms-are-not-alerting-for-new-events). ### An Alarm Action Script Does Not Run In SysTrack On-Premises, an alarm action that runs a script can fail on the endpoint with an "unexpectedly failed" error in the agent log. This happens when the script is not in the folder from which SysTrack distributes scripts to endpoints. See [Alarm Action Unexpectedly Fails on Agent](/documentation/docs/alarm-action-unexpectedly-fails-on-agent-1).