---
title: "Configure Scripts for Custom Alarms"
slug: "configure-scripts-for-custom-alarms"
updated: 2026-03-05T12:10:17Z
published: 2026-03-05T12:10:17Z
canonical: "documentation.lakesidesoftware.com/configure-scripts-for-custom-alarms"
---

> ## 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 Scripts for Custom Alarms

Custom alarms may be used to provide application-specific monitoring. Each alarm is based on the execution of a named script or program which must return a value through its exit code and allows for the configuration of scripts to provide specific timed information responses outside the bounds of the existing framework. For example, a script can send a ping to a router and if a successful reply is not received, denoted by an error code, the SysTrack Agent will respond with an action and/or a notification. In a more complex situation, a custom created script could send a SQL statement to a database and capture the response time of the query. If the response time is more than ‘y’ number of milliseconds, over number or consecutive requests, the SysTrack Agent could raise an alarm

For each script the following three alarms may be independently enabled:

- **Duration:** Triggered when the time required for the script to complete exceeds the specified limit for the specified time period.
- **Failure:** Triggered when an attempt to run the script fails.
- **Result:** Triggered when the value returned by the script exceeds the specified limit for the specified time period.

## Configure a Script

1. Select **Systems Configuration - Roles** on the navigation pane to display the Roles page, and then select the **Scripting** tab.
2. Click the **+** (plus) button to the left of **Scripts** to add a new child setting to the selected **Role**.

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/roles_scripting1(1).png)
3. In the **Add New Setting** dialog create a Name for your setting and click the **Create** button.
4. In the **Script path/Redist/SQL** field use the drop-down menu to select one of the following options:
  - **Redist** allows for the placing of a script in the redist folder that will be distributed to each system running in this Alarm Configuration. The redist folder is located off the Lsiagent folder on the Master System. If you select this option the path will appear as follows: **Redist\<script name>**
  - **Path** enables you to use the ellipsis button (to the right of the **File** field) to select a specified path on each system where you would like to manually place a copy of the script.
  - **SQL** allows you to enter a SQL command line argument in the **Arguments** field to be applied to the script.
5. Use the **Frequency** field to configure how often the script will run. The frequency you select will depend heavily on the **Time** values you select for **Duration** and **Result** times.
6. Click in the **Start Time** field to display the Choose Time dialog and select the appropriate start time using the sliders, or clicking the **Now** button for the current time. Click the **Done** button when complete.

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/roles_scripting_starttime(1).png)
7. The custom script can be schedule to run in accordance with your scheduling. To do this select the **Synchronize** check box to synchronize your scripts with the time you have set.
8. Enter the **Red Limit**. Red is generic designation of higher severity. Its Limits and Times are typically set higher than a Yellow. This is the value against which another value is compared. In the case of the Duration, it is the time in seconds that must be exceeded before a failure is recorded. In the case of a **Result**, it works in conjunction with the Operator to determine if the error condition is met. In both cases, the Limit is dependent on the Time value before an Alarm, Notification or Action will be triggered.
9. Enter the **Red Time**. Red is generic designation of higher severity. Its Limits and Times are typically set higher than a Yellow. This is the total time in seconds that the Duration or Result values must exceed before an alarm is sounded. The limit must be exceeded during the duration of the Time value or an alarm will not be generated.
10. Use the **Timeout** field to set a value that will cause the SysTrack Agent to stop the script after the script has run for that period of time.
11. Enter the **Yellow Limit** value. This is the value against which another value is compared. In the case of the **Duration**, it is the time in seconds that must be exceeded before a failure is recorded. In the case of a **Result**, it works in conjunction with the Operator to determine if the error condition is met. In both cases, the Limit is dependent on the Time value before an Alarm, Notification or Action will be triggered.
12. Enter the **Yellow Time**. This is the total time in seconds that the **Duration** or **Result** values must exceed before an alarm is sounded. The limit must be exceeded during the duration of the Time value or an alarm will not be generated.
13. Select a **Notification** from the drop-down menu.If desired select an **Action** to take when the set limits are exceeded from the drop-down menu.
14. If you wish to set the **Action** field to its default value, click the ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/refres__icon.png)icon to the right of the field.
15. When you are done, click the **Save Changes** button on the top right of the page.

<style> p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data-block-id] { margin-bottom: 0;} blockquote p[data-block-id] {margin-bottom: 0 !important;} &nbsp;p[data-block-id]:empty::after {content: "\00A0";} </style>