Configuring ServerAgent for Private Node Server

Network connectivity

ServerAgent uses the following ports for outbound communication through the firewall:

Port	Protocol	Destination	Purpose
443	TCP	privateagent.alertsite.com privateagent.jupiter.alertsite.com	To register the ServerAgent in AlertSite. Note: privateagent endpoints have dynamic IP addresses. Firewall rules must use the domain names and not their current IP addresses.
4892	TCP	Primary and secondary location configured for this ServerAgent (see below).	For outbound performance data and status of Private Node Server ServerAgent. Data is sent as encrypted XML.

ServerAgent does not use the proxy server configured for the Private Node Server. It uses a direct outbound connection.

Plan availability

Once the ServerAgent plan is in place, you can configure ServerAgent to monitor your Private Node Server. First, you need to generate a Device (Monitor) ID in the AlertSite console:

1. In AlertSite UXM, select  > AlertSite 1.0 from the top menu to switch to the classic interface.

2. Go to Configuration > ServerAgents.

3. Click Add a New ServerAgent.

   

4. Enter your ServerAgent parameters:

   • Site Name – a name for ServerAgent that will be displayed in AlertSite dashboards and reports.

   • Site Plan – select the Server Agent 5 w/ InSite plan. If you do not see the plan, contact your AlertSite Sales representative.

   • Monitoring Is – set to Enabled.

   • Notify on Error? – set to Yes. You will receive alerts when ServerAgent detects a problem with your Private Node Server.

   • Reporting Interval – specify how often (in minutes) ServerAgent should check in with AlertSite to report results and indicate that it is up and running. If ServerAgent has not reported in at the expected interval, a 4050 - server not responding error occurs.

   

5. Click Submit in the top right corner.

6. This will generate a Device ID for your ServerAgent.

   

7. Copy this value somewhere – you will need it later.

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:

1. In AlertSite 1.0, on the ServerAgent configuration page, click Locations in the top right corner.

   

2. Note down the first location in the list – it is marked as Primary.

   

3. (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.

4. To find the secondary location:

   • Go to Reports > Performance Reports.

   • Select your ServerAgent in the list.

   • Note down the secondary location that is displayed.

   Note: The secondary location is assigned automatically and cannot be changed.

5. On the Monitoring Locations - IP Addresses page, find these locations and note down all of their IP addresses.

6. Configure your firewall to allow outgoing traffic on port 4892 to all the IPs listed.

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.

1. Navigate to https://<IP address>, where <IP address> is the IP address of your Private Node Server.

2. Go to ServerAgent > Register ServerAgent.

3. Enter the Device (Monitor) ID that you copied from AlertSite earlier and click Register.

   

4. After ServerAgent is registered successfully, click the link to start it.

   

5. After a few minutes, the ServerAgent information in AlertSite will update to include the configuration section at the bottom of the page.

   

6. On this page, switch to the User Scripts tab.

7. Select the Enable User Scripts Monitor check box.

8. Make the following changes in the first (blank) line:

   • Select the Enabled and Notify check boxes.

   • Enter lastsend.sh in the Name column.

   • Change the Compare operator to > or >=.

   • Change Warning Value to 15.

   • Change Threshold Value to 20.

   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.

9. Click Submit in the top right corner.

ServerAgent starts working immediately. There is no need to reboot Private Node Server, and there is no loss of monitoring.

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:

To get notified of possible connectivity loss, we recommend using connectivity alerts instead of ServerAgent.

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.

Test connection through port 4892

Restart ServerAgent