To use AppNeta Performance Manager (APM), you need two things: an app to monitor, which you no doubt already have, and somewhere to monitor from. That ‘somewhere’ is a device that we provide you, which we call a monitoring point.
While physical monitoring points are monitoring software installed on dedicated hardware, the software sequencer is just the monitoring software. It comes in the form of a small executable, which you download from AppNeta Performance Manager (APM). Install it on an physical or virtual machine in your network, and the software sequencer will add itself to your organization.
- Decide where to deploy
- Adjust your firewall rules
- Prepare the host
- Download and install
- Assign licenses
- Set the device location
- Make sure you’re using a supported OS.
- For virtual environments, make sure you’re using a qualified hypervisor + guest OS. If not use a Virtual Monitoring Point instead.
Decide where to deploy
You need to be strategic about where you position your monitoring point:
- Make sure the paths you end up monitoring overlap as much as possible with the end-to-end application delivery path—from the user, through the network, to the server. This means matching your users in terms of geography and maybe even network segment.
- Make sure you’re monitoring from perspective of the people using the app so that your results are relevant to their actual experience. This means thinking about VLAN tags and QoS in addition to geography.
Our recommendation: For ease of deployment, and to get the most out of APM with only one monitoring point, we recommend deploying at the distribution layer.
Adjust your firewall rules
Once you’ve decided where you want to deploy your monitoring point, consult your network administrator to make sure that devices in that part of the network have sufficient access to the Internet. This table lists the ports and protocols that need to be allowed through your firewall.
Prepare the host
- Windows hosts: You may need to add an exception to your Windows Firewall and any other security software that may block sequencer traffic.
- Virtual hosts: The pseudo performance counter must be enabled or the software sequencer will return spurious results. The instructions that follow show you how to do this in vSphere Client 5.5.
- In the vSphere Client, navigate to View > Inventory.
- Power off the guest on which the sequencer 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. It’s the one with the .vmx extension.
- Search for the line
monitor_control.pseudo_perfctr = "true". If it is not present, append it to the file and save your changes.
- Back in the datastore view, upload your new .vmx file.
- Reset the guest.
Download and install
- Log in to login.appneta.com.
- Select an organization if you belong to more than one.
- If you’re setting up your first monitoring point, you’ll automatically be taken to the first step of the ‘+ Add Monitoring Point’ wizard.
- If your organization already has monitoring points, you’ll have to navigate to the first step:
- Log in.
- Select an organization.
- Navigate to > Manage Monitoring Points.
- Click ‘+ Add Monitoring Points’.
- Click ‘Software Sequencer’.
- Download the sequencer for your OS.
- Keep APM open. We’ll come back to it later.
- Install the sequencer on your host machine.
All monitoring points need a license before they can do anything. Every monitoring point comes with a base license that allows you to monitor a certain number of applications. Other licenses may be added as needed.
- Go back to APM where you should be prompted to assign the monitoring point a license.
- Assign it at least a base license—called ‘small’, ‘medium’, or ‘large’ depending on your device model.
If you find yourself outside the Add Monitoring Point workflow and there is an unlicensed monitoring point in your organization, navigate to > Manage Licenses to assign it one.
Set the device location
When adding a new monitoring point to APM, you are prompted to enter the it’s location. This setting provides essential context for the data that the monitoring point collects. APM is all about monitoring from the perspective of your end users, and the location setting effectively declares where those users are geographically.
If you find yourself outside the Add Monitoring Point workflow and there is a monitoring point in your organization without a location set, you can set it from > Manage Monitoring Points > > Edit Location.