--- title: "Notifications for Offline Agents" slug: "notification-for-offline-agents" description: "Set up a sensor notification that alerts recipients when SysTrack agents in a group of critical systems are disconnected for 10 minutes." status: "update" updated: 2026-11-10T13:03:25Z published: 2026-11-10T13:03:25Z canonical: "documentation.lakesidesoftware.com/notification-for-offline-agents" --- > ## 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. # Notifications for Offline Agents You can receive a notification when a SysTrack agent is offline. Use the **Agent and Supervisor Not Connected to Master** sensor (in the **SysTrack** category) to receive a notification. > [!NOTE] > **NOTE**: This sensor is only in sensor notifications, and it must be the only sensor in its notification. You cannot combine it with other sensors. This sensor is intended for a group of critical devices that are expected to always be online. For example, you may set this to a group of servers for your call center team. This sensor is looking for: - whether the web socket connection between the agent and master has been closed for at least 10 minutes. - whether any sensor data has been received from the last 10 minutes. The data contains all results, which sensors have gone off and which have not. If there is no sensor data received, this indicates a problem with the Agent and Supervisor Service. If there is no web socket connection and no sensor data for 10 minutes, it is likely that the agent is disconnected. ## Create a Notification for Offline Agents 1. Go to **Configure** > **Sensor Configuration** > **Notifications**, unlock Configure, and start a new sensor notification. See [Create a Sensor Notification](/documentation/docs/manage-sensor-notifications-in-configure#create-a-sensor-notification). 2. In **Sensors**, select the **SysTrack** category, select **Agent and Supervisor Not Connected to Master**, and click **+ Add**. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/noothersensors.png?sv=2026-02-06&spr=https&st=2026-11-20T20%3A59%3A22Z&se=2026-11-20T21%3A59%3A22Z&sr=b&sp=r&sig=ZzHzB3%2BrRFYMRKNzlvxKY6Krubi%2BK8PWjqK0KJle4cg%3D) If you first added another sensor, the editor shows **This sensor must be added by itself**. Click **Remove Other Sensors** to remove the other sensors. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(524).png?sv=2026-02-06&spr=https&st=2026-11-20T20%3A59%3A22Z&se=2026-11-20T21%3A59%3A22Z&sr=b&sp=r&sig=UQyvb8yEjKPhp9ly98dLzdaACwOTujbJq2L4CqMu%2Bjo%3D) 3. In **Group**, select the group of critical systems. The default is **All Systems**. > [!WARNING] > **IMPORTANT**: We strongly recommend that you do not set the group for this notification to be All Systems because recipients would receive many notifications. 4. In **Activation** > **Count**, select **Number of Systems** (default) or **Percent of systems**. In **Activate notification when**, enter the number or percentage of offline systems that activates the notification. See step 10 of [Create a Sensor Notification](/documentation/docs/manage-sensor-notifications-in-configure#create-a-sensor-notification). 5. Add the recipients, and click **Save Notification**. 6. Click the lock icon when you are done.