Monitoring Points

The AppNeta Container-based Monitoring Point (CMP) is software that runs in a Docker container. It supports Delivery/Experience monitoring up to 1Gbps. It is typically deployed on Azure in one of the following scenarios:

  • Monitoring from a remote region - The CMP is deployed in Azure in a region where you have users but where you can’t deploy at their locations. User experience can then be measured from that region to your critical applications.
  • Monitoring to an Azure-based app - The CMP is deployed in the same Virtual Network (VNet) as your critical applications. It is used as a target when monitoring network performance from remote regions or sites. It can also be used to measure baseline user experience to your applications.

The CMP can be deployed using either Azure Kubernetes Service (AKS) orchestration or Docker Compose.

Keep in mind:

  • The CMP does not have a Web UI. Instead, management of the CMP container is performed using the applicable orchestration commands.
  • Capacity measurements can be influenced by networking on the host, kernel version on the host, other containers sharing the host.
  • When targeting a CMP, use dual-ended monitoring.
  • AKS
    • When deployed on Azure using AKS, a redundant instance is automatically created and failover is automatic.
    • To target a CMP deployed using AKS, run the terraform output command within the Azure Cloud Shell to determine the Load balancer fqdn to target.

A full list of features can be found on the Monitoring Point Feature Comparison page.

Specifications

Host Requirements

The host requirements for the CMP are as follows:

Host requirement Azure
OS Linux
Environment AKS or Docker Compose
CPU D1 v2 (1 vCPU)
RAM 3.5 GB
Storage min 20 GB

Limitations

CMP limitations include:

Setup

Monitoring Point setup

Use the following steps to install a Container-based Monitoring Point (CMP) in your network. After installation is complete, the CMP software connects back to AppNeta Performance Manager (APM). Once this is done, you need to license the CMP, set its location, and then set up monitoring.

Deployment options on Microsoft Azure include:

To install the CMP into a remote region on the Azure public cloud, you can use AKS or, if it is not available in the region you are deploying to, you can use Docker Compose.

To install the CMP into an Azure Virtual Network (VNet) (Azure’s version of a Virtual Public Cloud) that you control, you’ll need to use Docker Compose.

Installing the CMP using AKS

Use this procedure to install the CMP into your Docker environment using AKS orchestration.

Prerequisites

The following are required to deploy and run the CMP using AKS.

  • An Azure account.
    • If prompted to create a storage account, enter “yes”.
  • “Owner” or “Contributor” and “User Access Administrator” roles assigned.
  • Kubernetes 1.14+ (provided within the Azure environment)
  • Azure Cloud Shell (provided within the Azure environment), which also provides:
    • Terraform v0.12.23+
    • Helm v3.1.1+ (added during deployment steps)
Install a CMP using AKS

You can install a CMP using AKS either via the APM user interface or via the APM API.

Note: Only one CMP can be installed on a host. To remove an existing CMP, first delete it from APM (see Delete), then uninstall the CMP software (see Uninstall CMP software - AKS).

Install using the APM user interface
  1. Log in to APM.
  2. Select an organization if you belong to more than one.
  3. If you’re setting up your first Monitoring Point, you’ll automatically be taken to the first step of the Add Monitoring Point wizard.
  4. If your organization already has Monitoring Points, navigate to > Manage Monitoring Points > Add Monitoring Points.
  5. Click Azure Kubernetes (AKS).
  6. Follow the instructions provided. A CMP is created and running.
Install using the APM API
  1. Log in to APM.
  2. Navigate to > Explore API.
  3. Determine your organization ID.
    1. Navigate to organization > GET /v3/organization.
    2. Click Try it out!
    3. In the Response Body, find and record the id for the organization you want the CMP associated with.
  4. To specify the CMP configuration, navigate to appliance > POST /v3/appliance/configuration/{orgId}/{configurationType}/{hostname}.
  5. In the Parameters section, specify the following:
    • orgId - Set this to the organization ID you recorded in the previous step.
    • configurationType - Set this to AKS.
    • hostname - Set this to the hostname for your CMP. Note: The hostname must start and end with an alphanumeric character, contain only lowercase alphanumeric characters or ‘-’, and have a maximum of 53 characters.
  6. Click Try it out!
  7. Copy the output from the Request URL section. This is the <endpoint_url> used in the following step.

From the Azure Cloud Shell, run the following commands:

  1. Upload the CMP configuration (you will be prompted for your APM password)

        curl -u <APM_username> -X POST --header "Content-Type: application/json" --header "Accept: application/gzip" "<endpoint_url>" -o aks.<hostname>.tar.gz
    
    • APM_username - your APM username
    • endpoint_url - the URL copied in the previous step
    • hostname - the hostname you specified for your CMP in the previous step
  2. Uncompress the configuration file.

        tar -xf aks.<hostname>.tar.gz
        cd <hostname>
    
  3. Set up an AKS cluster (done once for each Azure location you deploy to or to change the cluster configuration).

        /bin/bash setup.sh
        terraform init
        terraform apply
    
    • This process will take approximately 8 minutes. Follow the prompts. The output is used in the next steps.
    • Note: If you plan to use the CMP as a target, make note of the Load balancer fqdn. This is the target hostname you’ll use.
  4. Start the CMP.

    • Run the helm command output by terraform apply. If you miss the output, use terraform output to view it.
    • A CMP is created and running.
Assign a base license

Every CMP is sold with a base license (Strategic (m50/c50)/Legacy Small Office) that allows it to monitor a number of applications. The base license must be assigned to the CMP in APM before it can be used.

  1. Within APM, navigate to > Manage Monitoring Points.
  2. Wait for the new CMP to show up in the list (you may need to refresh your screen).
    • The CMP’s 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. To assign it a base license, navigate to > Manage Licenses.
  4. In the Parent Organization drop-down (if visible), select the parent organization containing the CMP.
  5. In the Organization drop-down, select the child organization containing the CMP.
  6. Click the APM Monitoring Points tab in the bottom table.
  7. For the CMP you want to add the license to, select > Assign Licenses.
  8. In the Base License section, select a base license.
  9. Click Submit. The CMP is ready to use.
Optional - Assign add-on licenses

In addition to a base license, you can add Standard Enterprise Application licenses, voice licenses, and video licenses to the CMP. Before they can be assigned, you need to purchase them. Once purchased, they will be added to your organization and available for assignment.

To assign an add-on license to the CMP:

  1. Navigate to > Manage Licenses.
  2. In the Parent Organization drop-down, select the parent organization containing the CMP.
  3. In the Organization drop-down, select the child organization containing the CMP.
  4. Click the APM Monitoring Points tab in the bottom table.
  5. For the CMP you want to add the license to, select > Assign Licenses.
  6. In the Add-on Licenses section, specify the types and quantities of licenses you want to add.
  7. Click Submit.
    • The new capabilities are ready to use.
Set the location

When adding a new CMP to APM, you need to specify its location. This setting provides essential geographical context for the data that the CMP collects. Typically, you specify its location during the setup procedure.

If you are outside the setup procedure, you’ll need to edit its location:

  1. Navigate to > Manage Monitoring Points
  2. For the CMP you want to edit, select > Edit Location.
  3. Specify the location of the CMP.
  4. Click OK.
    • The location is set.
Set up monitoring

At this point the Monitoring Point setup is complete. Continue the APM setup procedure at Set up performance monitoring.
Note that the CMP only supports Delivery and Experience monitoring. It does not support Usage monitoring.

Installing the CMP using Docker Compose

Use this procedure to install the CMP into your Docker environment using Docker Compose.

Operational Note: If you change the DNS settings on a CMP host (either the DNS Nameservers or the DNS Search Domain), you will have to restart the CMP to propagate the DNS settings down to the container.

Prerequisites

The following are required to deploy and run the CMP using Docker Compose:

Install Docker

If you have not already done so, install Docker Engine and Docker Compose on your deployment host.

Note: Different Linux operating systems have different requirements for installing Docker Engine and Docker Compose. Be sure to follow the setup instructions for your operating system.

Install a CMP using Docker Compose

Important: Always use a dedicated instance and “host networking” when installing on Azure.

To remove an existing CMP, first delete it from APM (see Delete), then uninstall the CMP software (see Manage software).

You can install a CMP using Docker Compose either via the APM user interface or via the APM API.

Install using the APM user interface
  1. Log in to APM.
  2. Select an organization if you belong to more than one.
  3. If you’re setting up your first Monitoring Point, you’ll automatically be taken to the first step of the Add Monitoring Point wizard.
  4. If your organization already has Monitoring Points, navigate to > Manage Monitoring Points > Add Monitoring Points.
  5. Click Docker Compose.
  6. Follow the instructions provided.

    • If you are prompted “Would you like to use host networking?”, enter ‘y’.

    • A CMP is created and running.
    • The install directory contains an mp-compose.yaml file. Do not remove this file as it is required to manage the CMP.
Install using the APM API
  1. Log in to APM.
  2. Navigate to > Explore API.
  3. Determine your organization ID.
    1. Navigate to organization > GET /v3/organization.
    2. Click Try it out!
    3. In the Response Body, find and record the id for the organization you want the CMP associated with.
  4. Specify the CMP configuration.
    1. Navigate to appliance > POST /v3/appliance/configuration/{orgId}/{configurationType}/{hostname}. In the Parameters section, specify the following:
      • orgId - Set this to the organization ID you recorded in the previous step.
      • configurationType - Set this to DOCKER_COMPOSE.
      • hostname - Set this to the hostname for your CMP.
    2. Click Try it out!
    3. Copy the output from the Request URL section. This is the <endpoint_url> used in the following step.
  5. On your deployment host, upload the CMP configuration (you will be prompted for your APM password)

    curl -u <APM_username> -X POST --header "Content-Type: application/json" --header "Accept: application/gzip" "<endpoint_url>" -o compose.<hostname>.tar.gz
    
    • APM_username - your APM username
    • endpoint_url - the URL copied in the previous step
    • hostname - the hostname you specified for your CMP in the previous step
  6. Uncompress the configuration file

    tar -xf compose.<hostname>.tar.gz
    cd <hostname>
    
  7. Authenticate with the Container Registry

    /bin/bash setup.sh
    
    • Note: You may need to run sudo /bin/bash setup.sh for this to execute successfully.
  8. Start the CMP

    docker-compose -f mp-compose.yaml pull && docker-compose -f mp-compose.yaml up -d
    
    • A CMP is created and running.
    • Note: You may need to run sudo docker-compose -f mp-compose.yaml pull && sudo docker-compose -f mp-compose.yaml up -d for this to execute successfully.
Assign a base license

Every CMP is sold with a base license (Strategic (m50/c50)/Legacy Small Office) that allows it to monitor a number of applications. The base license must be assigned to the CMP in APM before it can be used.

  1. Within APM, navigate to > Manage Monitoring Points.
  2. Wait for the new CMP to show up in the list (you may need to refresh your screen).
    • The CMP’s 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. To assign it a base license, navigate to > Manage Licenses.
  4. In the Parent Organization drop-down (if visible), select the parent organization containing the CMP.
  5. In the Organization drop-down, select the child organization containing the CMP.
  6. Click the APM Monitoring Points tab in the bottom table.
  7. For the CMP you want to add the license to, select > Assign Licenses.
  8. In the Base License section, select a base license.
  9. Click Submit. The CMP is ready to use.
Optional - Assign add-on licenses

In addition to a base license, you can add Standard Enterprise Application licenses, voice licenses, and video licenses to the CMP. Before they can be assigned, you need to purchase them. Once purchased, they will be added to your organization and available for assignment.

To assign an add-on license to the CMP:

  1. Navigate to > Manage Licenses.
  2. In the Parent Organization drop-down, select the parent organization containing the CMP.
  3. In the Organization drop-down, select the child organization containing the CMP.
  4. Click the APM Monitoring Points tab in the bottom table.
  5. For the CMP you want to add the license to, select > Assign Licenses.
  6. In the Add-on Licenses section, specify the types and quantities of licenses you want to add.
  7. Click Submit.
    • The new capabilities are ready to use.
Set the location

When adding a new CMP to APM, you need to specify its location. This setting provides essential geographical context for the data that the CMP collects. Typically, you specify its location during the setup procedure.

If you are outside the setup procedure, you’ll need to edit its location:

  1. Navigate to > Manage Monitoring Points
  2. For the CMP you want to edit, select > Edit Location.
  3. Specify the location of the CMP.
  4. Click OK.
    • The location is set.
Set up monitoring

At this point the Monitoring Point setup is complete. Continue the APM setup procedure at Set up performance monitoring.
Note that the CMP only supports Delivery and Experience monitoring. It does not support Usage monitoring.

Troubleshooting connectivity to AppNeta

Your CMP is properly connected to AppNeta Performance Manager (APM) when the status icon in > Manage Monitoring Points shows Green circle with white check mark.

If this is not the case, use the troubleshooting procedure below to help determine why it is not connecting.

Requirements Things to check
The Monitoring Point must be running. Check that the containers are running.
Your firewall/Network Security Group must be configured to allow the CMP to connect to APM. Check the general firewall configuration.
Check the CMP-specific firewall configuration for Delivery monitoring.

If you are still unable to resolve the issue, contact AppNeta Support.

Access

View Monitoring Point status

You can view the CMP status on APM and on your deployment host.

View Monitoring Point status on APM

To view a Monitoring Point’s status in APM:

  • Within APM, navigate to > Manage Monitoring Points.
    • The Monitoring Point status is indicated by the icon in the left column.
Icon Status Description
Green circle with white check mark OK The Monitoring Point is connected to APM.
Black circle with white minus sign Connection Lost The Monitoring Point is not connected to APM. Troubleshoot the issue.

Additional statuses can be found in the Additional Status columns. Hover over the icons for details and/or actions to take.

Icon Status Description
Shared The Monitoring Point is shared between organizations.
Unlicensed The Monitoring Point is unlicensed.
Monitoring Point Error There is a Monitoring Point error.
Upgrade Available There is a software upgrade available for the Monitoring Point.

View Monitoring Point status on your deployment host

If the CMP is not connecting to APM, you will want to confirm that it is running on the deployment host. The commands for viewing CMP status on the deployment host depend on how it was deployed: using AKS or using Docker Compose.

View CMP status - AKS
  1. Sign in to the Azure Cloud Shell.
    • To view deployments:

       kubectl get deployments
      
    • To view deployment details:

       kubectl describe deployment <deployment-name>
      
    • To view pods:

       kubectl get pods
      
    • To view pod details:

       kubectl describe pod <pod-name>
      

For additional kubectl commands see kubectl Commands.

View CMP status - Docker Compose
  1. Login to the host the CMP is deployed on.
  2. Navigate to the directory the CMP was deployed from (it contains the mp-compose.yaml file).
  3. View the status of a CMP and verify that the two main system containers (with names ending in “sequencer_1” and “talos-001_1”) are up and running. For example:

    $ docker-compose -f mp-compose.yaml ps
    
           Name               Command                       State                                         Ports
    -----------------------------------------------------------------------------------------------------------------------------------------------------------------
    <name>_sequencer_1   /sbin/entrypoint.sh              Up (healthy)   0.0.0.0:1720->1720/udp, 0.0.0.0:3236->3236/tcp, 0.0.0.0:3236->3236/udp, 3237/tcp,
                                                                         0.0.0.0:3237->3237/udp, 0.0.0.0:3238->3238/tcp, 0.0.0.0:3238->3238/udp, 3239/tcp,
                                                                         0.0.0.0:3239->3239/udp, 0.0.0.0:33434->33434/udp, 0.0.0.0:443->443/tcp,
                                                                         0.0.0.0:5060->5060/udp
    <name>_talos-001_1   /app/run-engine-wrapper.sh ...   Up
    
  • Note: You may need to run sudo docker-compose -f mp-compose.yaml ps for this to execute successfully.
  • Alternatively, you can use docker ps to view the status of the two containers used by the CMP.

For additional docker-compose commands, see the Docker Compose CLI reference.
For additional docker commands, see the Docker CLI reference.

Determine the Monitoring Point hostname or IP address

Once the CMP has connected to APM, you can view its hostname and IP address.

  1. Log in to APM.
  2. Make sure you are using the correct organization
  3. Navigate to > Manage Monitoring Points.
  4. Click the CMP you want to connect to. In the right pane:
    • the Host Name field contains the hostname.
    • the Public IP field contains the public IP address. Use this if you are connecting to the CMP across the internet.
    • the Host Networking Details section contains the active CMP interfaces and the local IP address of each. Use this if you are connecting to the CMP locally.

Configure

Methods

Management and configuration capabilities are accessed from within APM via > Manage Monitoring Points. For example, changing Monitoring Point location or renaming the Monitoring Point.

The CMP does not have a Web UI. Instead, management of the CMP container is performed using Docker Compose commands. See the Docker documentation for details.

Basic settings

There are a few settings that should be configured on the CMP including Time zone, Location, and Name.

Time zone

There are two time zones that must be configured - your local time zone and the Monitoring Point time zone.

The Monitoring Point time zone must be configured on the host the CMP is running on.

Setting the CMP time zone correctly is important for a number of reasons:

  • In conjunction with the CMP’s system time, it is required in order for the CMP to connect to APM. If the time is not correct, then there could be an issue with certificate validity checks when connecting.
  • It is required for monitoring results to be timestamped correctly.
  • It is required in order to display the correct time in path performance charts when Source Monitoring Point Time Zone is set.
  • It is required for alert conditions to be applied at the right time according to alert time ranges you have set.

Location

The location specified for the CMP is necessary for a variety of reports and charts.

The CMP’s location is specified during the setup procedure but it can be edited at any time.

  1. Navigate to > Manage Monitoring Points
  2. For the Monitoring Point you want to edit, select > Edit Location.
  3. Specify the location of your Monitoring Point.
  4. Click OK.
    • The Monitoring Point’s location is set.

APM name and hostname

All Enterprise Monitoring Points (EMP) have two names: a hostname and an APM name. The hostname is used to identify the Monitoring Point on the network. The APM name is used to identify the Monitoring Point within APM. These are specified when the container is created.

If you manually change the APM name, the hostname is not affected. If you change the hostname, the APM name is changed automatically unless the APM name was changed manually. In this case, changing the hostname does not affect the APM name.

Rename a Monitoring Point

To change the CMP’s APM name:

  1. Navigate to > Manage Monitoring Points.
  2. For the CMP you want to rename, navigate to > Rename.
  3. Select rename to.
  4. In the rename to field, enter the new APM name.
  5. Click Submit.
    • The CMP’s APM name is changed.
Reset a Monitoring Point name to its default

You can reset the APM name of the CMP to the default name generated by APM.

To reset the CMP’s APM name to its default:

  1. Navigate to > Manage Monitoring Points.
  2. For the CMP whose name you want to reset, navigate to > Reset Name.
    • The CMP’s APM name is reset to its default.
Change the hostname

When you change the CMP’s hostname, the APM name is changed automatically unless the APM name was changed manually. In this case, changing the hostname does not affect the APM name.


To change the CMP’s hostname:

Change CMP hostname - AKS
  1. Sign in to the Azure Cloud Shell.
  2. Uninstall the software.

    helm uninstall <monitoring-point-name>
    
  3. Navigate to the directory the Monitoring Point was deployed from (it contains the terraform.tfstate file).
  4. Edit the hostname.txt file and change hostname to the new hostname.
  5. Set up an AKS cluster.

    /bin/bash setup.sh
    terraform init
    terraform apply
    
  6. Start the Monitoring Point.
    • Run the helm command output by terraform apply.
Change CMP hostname - Docker Compose
  1. Login to the host the CMP is deployed on.
  2. Navigate to the directory the CMP was deployed from (it contains the mp-compose.yaml file).
  3. Bring down the CMP.

    docker-compose -f mp-compose.yaml down
    
  4. Edit the .env file, and change APPNETA_CONTAINER_NAME to the new hostname.
  5. Bring the CMP back up.

    docker-compose -f mp-compose.yaml up -d
    

Networking

The following networking-related features can be configured on the CMP.

Hostname

See APM Name and Hostname

Web proxy

For networks that require internet traffic to be forwarded by a web proxy, the Container-based Monitoring Point (CMP) must be configured to connect to your proxy server so that it can communicate with APM.

The proxy settings on the CMP only affect how it connects and reports data back to APM. These settings are not used for performance monitoring. If you are using Experience monitoring, you will also need to configure access to the proxy either when you create a web app group or after the web app group is created.

In a Docker Compose environment, to configure the CMP to use your proxy server, you must make the configuration changes in Docker.

Manage

Restart

Restarting the CMP will disrupt its connection to APM but it does not affect its software or its configuration.

Restart - AKS

To restart a Container-based Monitoring Point (CMP) installed using Azure Kubernetes Service (AKS):

  1. Sign in to the Azure Cloud Shell.
  2. Determine the deployment name for the CMP.

    kubectl get deployments
    
  3. Perform the restart.

    kubectl rollout restart deployment <deployment name>
    
  4. Confirm that the CMP restarted successfully.

    kubectl get deployments
    

Restart - Docker Compose

To restart a Container-based Monitoring Point (CMP) installed using Docker Compose:

  1. Login to the host the CMP is deployed on.
  2. Navigate to the directory the CMP was deployed from (it contains the mp-compose.yaml file).
  3. Perform the restart.

    docker-compose -f mp-compose.yaml restart
    
    • Note: You may need to run sudo docker-compose -f mp-compose.yaml restart for this to execute successfully.
  4. Confirm that the CMP restarted successfully.

    docker-compose -f mp-compose.yaml ps
    
    • Note: You may need to run sudo docker-compose -f mp-compose.yaml ps for this to execute successfully.

Shutdown

Shutdown - AKS

To shut down the CMP:

  1. Sign in to the Azure Cloud Shell.
  2. Determine the deployment name for the Monitoring Point.

    kubectl get deployments
    
  3. Perform the shutdown.

    kubectl scale deploy <deployment name> --replicas=0
    
  4. To start it back up again:

    kubectl scale deploy <deployment name> --replicas=1
    
Shutdown - Docker Compose

To shut down the CMP:

  1. Login to the host the CMP is deployed on.
  2. Navigate to the directory the CMP was deployed from (it contains the mp-compose.yaml file).
  3. Perform the shutdown.

    docker-compose -f mp-compose.yaml stop
    
  4. To start it back up again:

    docker-compose -f mp-compose.yaml start
    
  • Note: You may need to run sudo docker-compose -f mp-compose.yaml stop and sudo docker-compose -f mp-compose.yaml start for these commands to execute successfully.
  • If necessary, you can use docker ps and docker kill to find and stop the two containers used by the CMP. Their names end in “sequencer_1” and “talos-001_1”.

Delete

Deleting the CMP from an organization is typically done when you are moving it to another organization or freeing up its base license so it can be used by another Monitoring Point.


Deleting the CMP has the following effects:

  • All paths where the CMP is the source (and the monitoring history related to those paths) are deleted (though they can be moved to another Monitoring Point during the delete process).
  • Tests and assessments are not deleted.
  • The base license and any add-on licenses that were assigned to the CMP become available again.
  • The CMP can no longer be seen from APM and will be decommissioned if it is online during the delete process.

To delete the CMP from your organization:

  1. Navigate to > Manage Monitoring Points.
  2. For the CMP you want to delete, select > Delete.
    • You will be prompted to confirm this action, and optionally to move all affected paths to another Monitoring Point.
  3. You should also remove resources on the deployment host.

Manage software

For a CMP, the software management functionality available depends on how it is deployed.

Manage software on a CMP deployed using AKS

For a CMP deployed using AKS, you can upgrade the software, roll it back to the previous version, or uninstall it. You can also remove all resources associated with the deployment.

Upgrade software - AKS

To upgrade the software on a CMP:

  1. Sign in to the Azure Cloud Shell.
  2. Perform the upgrade.

    helm repo update
    helm upgrade <monitoring-point-name> cmp-charts/c50
    

Other useful helm commands include:

  • helm list - lists installed CMP releases. Useful to show release version before and after an upgrade.
  • help search repo - lists the most recent chart.
  • helm repo ls - lists helm repositories.
Roll back software - AKS

To roll back the software version on a CMP:

  1. Sign in to the Azure Cloud Shell.
  2. Perform the rollback.

    helm rollback <monitoring-point-name>
    
Uninstall software - AKS

To uninstall the software on a CMP:

  1. Sign in to the Azure Cloud Shell.
  2. Perform the uninstall.

    helm uninstall <monitoring-point-name>
    
Remove all resources - AKS

To remove all resources associated with a CMP deployed using AKS:

  1. Sign in to the Azure Cloud Shell.
  2. Navigate to the directory the Monitoring Point was deployed from (it contains the terraform.tfstate file).
  3. Determine the resource group name.

    terraform output
    
  4. Perform the resource group removal.

    az group delete -n <resource group name>
    
  5. Remove the contents of the directory containing the CMP software.

    cd ..
    rm -r <hostname>
    

Manage software on a CMP deployed using Docker Compose

For a CMP deployed using Docker Compose, you can recreate it if the host fails, upgrade its software or uninstall it.

Recreate a CMP - Docker Compose

In a Docker Compose environment there is no automatic failover, so if the host fails and needs to be reinstalled, the CMP needs to be reinstalled as well. In order to keep all its monitoring history, you can recreate the failed CMP with the same identity as the old one rather than creating a new one.

Note: To avoid monitoring problems, you should only recreate a single instance of a CMP.

To can recreate a failed CMP deployed using Docker Compose:

  1. Log in to APM.
  2. Select the organization of the failed CMP (if you belong to more than one).
  3. Navigate to > Manage Monitoring Points.
  4. For the CMP you need to recreate, select > Re-create.
  5. Follow the instructions provided.
    • The replacement CMP is created and running.
Upgrade software - Docker Compose

To upgrade the software on a CMP deployed using Docker Compose:

  1. Login to the host the CMP is deployed on.
  2. Navigate to the directory the CMP was deployed from (it contains the mp-compose.yaml file).
  3. Perform the upgrade.

    docker-compose -f mp-compose.yaml down
    docker-compose -f mp-compose.yaml pull && docker-compose -f mp-compose.yaml up -d
    
  • Note: You may need to run sudo docker-compose -f mp-compose.yaml down and sudo docker-compose -f mp-compose.yaml pull && sudo docker-compose -f mp-compose.yaml up -d for these commands to execute successfully.

Note: For automated upgrades, Watchtower is available.

Uninstall software - Docker Compose

To uninstall the software on a CMP deployed using Docker Compose:

  1. Login to the host the CMP is deployed on.
  2. Navigate to the directory the CMP was deployed from (it contains the mp-compose.yaml file).
  3. Perform the uninstall.

    docker-compose -f mp-compose.yaml down
    
    • Note: You may need to run sudo docker-compose -f mp-compose.yaml down for this to execute successfully.
    • If necessary, you can use docker ps and docker kill to find and stop the two containers used by the CMP. Their names end in “sequencer_1” and “talos-001_1”.
  4. Remove the contents of the directory containing the CMP software.

    cd ..
    rm -r <hostname>
    

Note: This procedure removes the AppNeta software. It does not remove Docker volumes or images. If you wish to remove them, use Docker commands: docker volume rm and docker image rm.

Share

See Sharing a Monitoring Point.

Move between orgs

CMPs and the data they have collected cannot be moved to another organization. If you need to move a CMP to another organization you must first delete it then reinstall/re-deploy it in the new organization.

  1. Delete the CMP.
  2. Reinstall the CMP in the new organization.