In order to collect monitoring data or to access an Enterprise Monitoring Point (EMP) from APM, it must be connected to APM. You can view a monitoring point’s connection status on the Manage Monitoring Points page.

For a Container-based Monitoring Point (CMP), you can also check its status on the host it was deployed on.

For a physical and virtual monitoring point, to view its configuration you can access it via the Web Admin or via the Admin API.

For a physical monitoring point, you can also retrieve its configuration using a USB stick.

View monitoring point status

To view a monitoring point’s status on APM:

  1. 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 device is connected to APM.
Black circle with white minus sign Connection Lost The device is not connected to APM. Troubleshoot the issue.
Yellow circle with white exclamation mark Warning The device software needs to be updated, is not licensed, or is experiencing an error.

Viewing CMP status

If the Container-based Monitoring Point (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

To view CMP status:

  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

To view CMP status:

  1. Login to the host the monitoring point is deployed on.
  2. Navigate to the directory the monitoring point was deployed from.
  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: On Linux hosts, 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 monitoring point.

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