Team: Huntress Managed Endpoint Detection and Response (EDR)
Product: N-able
Environment: Huntress integration
Summary: Setup guide for N-Able integration for monitoring Huntress Agent and Huntress Updater service statuses.
Huntress has fully implemented Watchdog functionality into our services. While monitoring services can be a best practice in some scenarios, Huntress strongly recommends disabling self-healing actions and scripts that start or restart our services.
Starting a service during an update can lead to unintended consequences that can disrupt stability and functionality.
Updates often involve modifying configuration files, upgrading dependencies, or replacing critical components, which can leave the service in an inconsistent state if it starts prematurely. For example, the service may attempt to access files or resources that are being updated, leading to errors or data corruption. Additionally, partial updates can result in mismatched versions of libraries or binaries, causing the service to crash or behave unpredictably.
Follow the steps below to create a Service Monitor in N-able that monitors the Huntress Agent and Updater service statuses.
- Log into N-able
-
Create a Service Template from the Configuration menu
-
add a “Windows Service” to the template (choose that from the dropdown, and click the
Add Servicebutton) -
Name and write the full-service name in the “Service Name” section
- Set thresholds (probably nothing to change here)
-
Configure “When status changes” section
- Scroll down to configure "self-healing" action / after-action.
NOTE: The time period must be at least 30 minutes, as our agent will stop to install updates. Setting the timer too low may lead to unexpected issues that can negatively impact the agent. While agent updates typically finish in under a minute, external factors may extend this duration slightly, and any interference with the installation process could cause the update to fail or become unstable. - Click the “Action” tab, select the limit of self-healing actions (no idea what this should be), and choose the “Matching Service Name” - NOTE: You’ll have to do one of these for each individual service you want to monitor.
-
then it’ll look like this, and you can click save (partners might want notifications set up, that’s in the next tab over)
- The end should look like this (minus Rio if you don’t want to monitor it--it's not recommended to monitor the Rio service)
- Apply to customers/sites