Docker Monitoring Point Setup - c50

  1. Restrictions
  2. Prerequisites
  3. Create a c50
  4. Assign licenses
  5. Set the Monitoring Point location
  6. Set up monitoring
  7. Update a c50

The AppNeta c50 is a container Monitoring Point that runs as a Docker container within a Docker environment.

This document assumes Nomad is being used for orchestration.

Please contact AppNeta Support for installation and configuration assistance.


Only one c50 can be installed per host.


You need the following in place prior to creating a c50:

  • Physical or virtual host (e.g., Virtual Server within the IBM Cloud).
    • CentOS installed (minimum version 7.6).
    • Nomad installed (minimum version v0.8.7).
    • Docker CE installed (minimum version 18.03.1-ce).
    • 4 GB memory available for c50.
  • Nomad jobspec file: c50.nomad.
  • Network access to the container registry housing the c50 docker image.
  • Network access to AppNeta Performance Manager (APM).

Create a c50

To create a c50:

  1. Copy c50.nomad jobspec file (available from AppNeta) to the host where the c50 will reside.
  2. Confirm that your system has Docker running:

     docker version
    • You should see the version of Docker currently running
  3. Confirm that there are no other c50 Monitoring Points running:

     nomad job status
  4. Verify that the c50.nomad file is valid:

     nomad job plan c50.nomad
  5. Create the c50:

     nomad job run c50.nomad
  6. Confirm that the c50 is created and connected to APM:

     docker ps
    • When the STATUS of the c50 shows “Up X minutes (healthy)” it is connected to APM.

Assign licenses

Every Monitoring Point is sold with a base license that allows it to monitor a 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:

  1. Within APM, navigate to > Manage Monitoring Points.
  2. 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” (Green circle with white check mark).
    • If it doesn’t appear after a few minutes, you’ll need to troubleshoot the problem.
  3. Assign a base license to the Monitoring Point.
  4. 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.

Set up monitoring

At this point the Monitoring Point setup is complete. Continue the APM setup procedure at Set up performance monitoring.

Update a c50

When a new version of the c50 becomes available, it is added to the container registry with the current image. To use the new image, simply specify the new image number in the c50.nomad file and rerun the nomad job run c50.nomad command.

To update the c50:

  1. Determine the name of the new image:

     docker images
    • All available docker images are listed.
  2. Edit the c50.nomad file and replace the old image name with the new name. The image name is specified in the “image” parameter (for example, change “pathview-cmp:” to “pathview-cmp:”).
  3. Create the c50 with the updated image:

     nomad job run c50.nomad
  4. Confirm that the c50 is created and connected to APM:

     docker ps
    • When the Status of the c50 shows “healthy” it is connected to APM.