Use the following steps to install a software monitoring point (s35) in your network. After installation is complete, the s35 software connects to back APM. Once this is done, you need to license the monitoring point, set its location, and then set up Delivery monitoring.
- Prepare the host
- Download and install the software
- Assign licenses
- Set the monitoring point location
- Set up monitoring
- Make sure you’re using a supported OS.
- For virtual environments, make sure you’re using a qualified hypervisor and guest OS. If not, use a Virtual Monitoring Point instead.
- Determine the best place in your network to deploy the monitoring point.
- Configure your firewall rules to enable the monitoring point access to APM.
- The monitoring point can still be installed and configured without this step, but monitoring is not possible until it is done.
Prepare the host
Host preparation depends on the host operating system being used.
You may need to add an exception to your Windows firewall and any other security software that may block s35 traffic.
Mac OS hosts
No changes required.
In virtual environments, the pseudo performance counter must be enabled or the s35 will return spurious results. For example, to enable the pseudo performance counter in vSphere Client 5.5:
- In the vSphere Client, navigate to View > Inventory.
- Power off the guest on which the s35 will be installed.
- Select the host at the root of the inventory tree and then navigate to it’s Summary tab.
- In the Resources pane of the Summary tab, find its datastore and right-click > Browse Datastore.
- In the Datastore view, select the directory corresponding to the guest.
- Download the guest’s configuration file (the .vmx file).
- In the configuration file, search for the line
monitor_control.pseudo_perfctr = "true". If it is not present, append it to the file and save your changes.
- In the Datastore view, upload your new .vmx file.
- Reset the guest.
Linux hosts (systemd) - Configure auto-restart
To configure a Linux system (that supports systemd) to start automatically when the system is rebooted:
Create a systemd service file (/etc/systemd/system/sequencer.service) with the following content:
[Unit] Description=Sequencer After=syslog.target time-sync.target networking.service Requires=networking.service [Service] Type=forking ExecStart=/opt/pathview/netseq -b StandardOutput=null [Install] WantedBy=multi-user.target networking.service
Enable the service.
systemctl enable sequencer.service
Download and install the software
- Log in to APM.
- Select an organization (if you belong to more than one).
- If your organization already has monitoring points, navigate to > Manage Monitoring Points > Add Monitoring Points. Otherwise, you will automatically be taken to the first step of the Add Monitoring Point wizard.
- Click the button for your operating system.
- Follow the instructions to download the s35 software for your operating system and the configuration file for your organization.
- Keep APM open.
- Install the s35 software and configuration file on your host machine.
Every monitoring point is sold with a base license that allows it to monitor a certain number of applications. The base license must be assigned to the monitoring point in APM before it can be used. Optionally, add-on licenses can be assigned.
To license a monitoring point:
- Within APM, navigate to > Manage Monitoring Points.
- Wait for the new monitoring point to show up in the list (you may need to refresh your screen).
- The monitoring point status should show “Connection Established” ().
- If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
- Assign a base license to the monitoring point.
- Optionally, assign add-on licenses as required.
Set the monitoring point location
When adding a new monitoring point to APM, you need to specify its location. This setting provides essential geographical context for the data that the monitoring point collects.
To set the location of the monitoring point:
- Enter the monitoring point location if prompted during the setup procedure.
- If you are outside the setup procedure, you’ll need to edit the monitoring point location.
Set up monitoring
At this point the monitoring point setup is complete. Continue the APM setup procedure at Set up monitoring.
Note that the s35 only supports Delivery monitoring. It does not support Experience or Usage monitoring.