NOTE: As of Jan 31, 2021, only Monitoring Points that support TLS1.2 will be able to access APM-Public. Because the Linux NMP does not support TLS1.2, it will no longer be able to access APM-Public.
The APM-Private release due in Q1 2021 will also support the ability to block TLS1.0 and TLS 1.1 connections, so plans should be made to migrate away from the Linux NMP in these cases as well.
Existing Linux NMPs can be replaced with Container-based Monitoring Points.
Please contact AppNeta Support if you require assistance.
Use the following steps to install a Native Monitoring Point (NMP) on a Linux system on your network. After installation is complete, the NMP software connects to back APM. Once this is done, you need to license the Monitoring Point, set its location, and then set up monitoring.
- Prepare the host
- Download and install the software
- Verify the software is running
- Assign licenses
- Set the Monitoring Point location
- Set up monitoring
- Related topics
- Make sure you have administrative privileges on the system you are deploying to.
- 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 (on KVM or VMware) instead.
- 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
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-linux -b StandardOutput=null [Install] WantedBy=multi-user.target networking.service
Enable the service.
systemctl enable sequencer.service
In virtual environments, the pseudo performance counter must be enabled or the NMP 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 host on which the NMP 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 host.
- Download the hosts’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 host.
Download and install the software
- Log in to APM.
- Select an organization (if you belong to more than one).
- If you’re setting up your first Monitoring Point, you will be taken to the first step of the Add Monitoring Point wizard.
- If your organization already has Monitoring Points, navigate to > Manage Monitoring Points > Add Monitoring Points.
- In the Platform Type field, select Linux (native).
- Click Native monitoring point for Linux or Native monitoring point for Linux 64-bit depending on your host.
- The installer is downloaded to your computer.
- Follow the in-product instructions to install the software.
Verify the software is running
From the command line, verify that the NMP is running.
[root@hostname ~]# ps -ef | grep netseq-linux root 25660 1 0 Jan29 ? 00:03:25 ./netseq-linux -b root 32522 32465 0 10:55 pts/1 00:00:00 grep netseq-linux
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 NMP only supports Delivery monitoring. It does not support Experience or Usage monitoring.