---
title: "Services"
slug: "services"
description: "Monitor Windows services and applications in a SysTrack role, and raise an alarm when one stops responding or uses too many resources."
status: "new"
updated: 2026-10-26T10:40:25Z
published: 2026-10-26T10:40:25Z
canonical: "documentation.lakesidesoftware.com/services"
---

> ## 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.

# Services

Use the **Services** settings of a role to monitor Windows services and applications on systems that use the role. For each service or application that you add, you choose the conditions that raise an alarm, such as the service not responding or using more CPU than a limit. Each entry can also send a notification or run an action when its alarm is raised. The agent checks monitored services every 15 seconds.

## Open the Services Settings

1. Go to **Configure** > **System Configuration** > **Roles**.
2. Click the lock icon in the upper-right corner to unlock Configure for editing.
3. Select the role.
4. Select the **Services** tab. If the Roles page shows a **Policies** tab, select **Services** from the **Additional Settings** list instead.

The **Services** settings show the services and applications that the role monitors, with one row for each. To see only the entries and values that differ from the defaults, select **Display only non-default values**.

## Add a Service or Application

1. Open the **Services** settings of the role.
2. Click the **Add new child setting** icon. The **Add New Setting** dialog box opens.
3. Choose the service or application to monitor:
  - To pick a service that runs on one of your systems, select the system in **Select from System**, and then select the service.
  - To enter a service by name, select **Manual Service Entry**, and then enter the **Display Name** and the **Service Name**.
  - To monitor an application, select **Manual Application Entry**, and then enter the **Display Name** and the **Executable Name**.
4. Click **Create**. The new entry appears as a row in the **Services** settings.
5. In the row, select the conditions that raise an alarm, and change their limits if needed. See [Monitoring Conditions](/docs/services#monitoring-conditions).
6. (Optional) In **Notification**, select the notification to send when the alarm is raised. In **Action**, select the action to run. Both are **None** by default.
7. Click **Save Changes**.

Systems that use the role apply the change the next time they read their configuration. To apply it right away, run **Read Configuration** on those systems. See [Operations: Command Dashboard](/documentation/docs/operations-command-dashboard).

## Monitoring Conditions

Each condition is a check box in the row of the service or application. The agent raises an alarm on the system when a selected condition is met. For a service, **Not Responding** is selected by default. All other conditions are cleared. The agent checks **Not Responding** for services only. For an application, select another condition.

| Condition | When the Alarm Is Raised | Settings and Defaults |
| --- | --- | --- |
| **Not Responding** | The service does not answer a status request from the agent for the time in **Time Not Responding**. | **Time Not Responding**: 120 seconds |
| **If Number of Instances** | The number of running instances meets the condition set by **Instance Count Operator** and **Number of Instances** for the time in **Instances Affected For**. For example, with the default values, the alarm is raised when more than one instance runs for 15 seconds. | **Instance Count Operator**: Greater Than (also Less Than, Equal To, Not Equal To) **Number of Instances**: 1 **Instances Affected For**: 15 seconds |
| **CPU Above Limit** | CPU use stays above **High CPU Limit (%)** for **High CPU Time (seconds)**. When **Measure CPU of All Cores** is 0, CPU use is a percentage of one core, so it can be above 100% on a system with more than one core. Set **Measure CPU of All Cores** to 1 to measure CPU use as a percentage of all cores. | 90% for 120 seconds. **Measure CPU of All Cores**: 0 |
| **Physical Memory Above Limit** | Physical memory use stays above **High Physical Memory Limit (MB)** for its time setting. | 64 MB for 120 seconds |
| **Virtual Memory Above Limit** | Virtual memory use stays above **High Virtual Memory Limit (MB)** for its time setting. | 128 MB for 120 seconds |
| **I/O Above Limit** | Disk and network I/O stays above **High IO Limit (KB)** for its time setting. | 2.00 KB for 60 seconds |
| **CPU Below Limit**, **Physical Memory Below Limit**, **Virtual Memory Below Limit**, **I/O Below Limit** | Use stays below the matching **Low …** limit for its time setting. | Each limit is 0, for 60 seconds |
| **If Matching Service State** | The service is in the state selected in **Service State**. | **Service State**: **Ignored** (also **Stopped**, **Running**) |

## Change or Remove a Monitored Service

1. Open the **Services** settings of the role.

> [!CAUTION]
> **WARNING**: Deleting an entry stops monitoring of that service or application, and its conditions, limits, notification, and action are lost. Reverting an entry replaces its values with the defaults. Both take effect when you click **Save Changes**.
2. Do one of the following:
  - To change an entry, change the values in its row.
  - To reset an entry to its default values, click the revert icon in its row.
  - To stop monitoring a service or application, click the **Delete setting** icon in its row.
3. Click **Save Changes**.