Open topic with navigation
ServerAgent is a component of Private Node Server that monitors the location health and resource usage. If your private location misses a scheduled monitor run, or if it stops communicating with AlertSite, an alert will be sent to the selected recipients.
ServerAgent is not enabled by default, you need to configure it manually. This guide explains how you can do this.
Note: Currently, you can view the ServerAgent status and reports only in AlertSite 1.0 (the classic interface). You cannot view them in AlertSite UXM. However, alerts will come anyway.
Before you begin, verify that you have an available (free of charge) plan that lets you use ServerAgent on your private nodes:
You should see the ServerAgent 5 w/ InSite plan in the list.
If you do not see the plan, please contact Customer Support or your AlertSite Sales Representative immediately.
Once the ServerAgent plan is in place, you can configure ServerAgent to monitor your Private Node Server. First, you need to generate a Device ID in the AlertSite console:
Click Add a New ServerAgent.
Enter your ServerAgent parameters:
Monitoring Is – set to Enabled.
This will generate a Device ID for your ServerAgent.
ServerAgent does not send data directly to the AlertSite platform. It sends it to one of AlertSite global monitoring locations, and from there, the data gets to AlertSite. The location is selected automatically on the previous step, but you can change it. Note that if your Private Node Server is behind a firewall, you must allow outgoing communication to this location through port 4892 (see Network Connectivity).
To view or change the location to which ServerAgent sends data:
In AlertSite 1.0, on the ServerAgent configuration page, click Locations in the top right corner.
Note down the first location in the list – it is marked as Primary.
(Optional.) If you want to change the location, select the radio button next to another location and click Submit.
Note: If you are a Usage-Based Monitoring customer and you select a location outside the United States, Canada or Europe, you will consume additional measurement credits for each ServerAgent check.
Note: The secondary location is assigned automatically and cannot be changed.
On the Monitoring Locations - IP Addresses page, find these locations and note down all of their IP addresses.
Note that if you change the location at any time later, you will have to update the firewall rules to allow connections to the new location.
Enter the Device ID that you copied from AlertSite earlier and click Register.
After ServerAgent is registered successfully, click the link to start it.
After a few minutes, the ServerAgent information in AlertSite will update to include the configuration section at the bottom of the page.
Make the following changes in the first (blank) line:
This means that ServerAgent will report a warning condition if your Private Node Server has not reported to AlertSite for 15 minutes, and an error condition if has not reported for 20 minutes or more.
Note: You may use different Warning and Threshold values, but do not make them lower than 20 minutes + the shortest run interval of monitors on your private node. Also, note that if your shortest run interval is 10 minutes, the data may not be sent until the next 10-minute check.
ServerAgent starts working immediately. There is no need to reboot Private Node Server, and there is no loss of monitoring.
Note: You may receive one or two alerts initially while the system syncs up the connection to ServerAgent. Allow some time for communications to settle in.
You can see the most recently reported status of your ServerAgents on the Status > ServerAgents screen in AlertSite 1.0 (the classic interface).
To view historical data, you can run the ServerAgent Detail report in Reports > Performance Reports. Note that the report is limited to one week of data.
The following status codes are returned for problems detected by ServerAgent:
|4050||Server is not responding (see Troubleshooting below).|
|4040||Error threshold exceeded.|
|4030||Warning threshold exceeded.|
ServerAgent sends alerts to warn you about potential issues with your Private Node Server. These alerts are similar to monitor alerts, but use the status codes mentioned above.
To receive alerts, you need to have alert recipients configured.
Note that by default, ServerAgent sends alerts to all the recipients configured in your AlertSite account. To limit the number of recipients, create a recipient group for ServerAgent.
ServerAgent sends outgoing performance data through port 4892. You can test the connection as follows.
In Private Node Server 2.0.2 and later:
In earlier versions:
On the Monitoring Locations - IP Addresses page, find all the IP addresses for these locations.
Open the Control Panel (web interface) of your private node by navigating to https://<IP address>, where <IP address> is that of your private node.
If there are connection problems, make sure your firewall allows traffic from the private node to the specified ServerAgent hosts through port 4892. You can also try restarting the private node or the ServerAgent.
Sometimes, restarting ServerAgent may solve connection problems. To restart ServerAgent:
Note that restarting the private node itself will also restart the ServerAgent.