An Enterprise Monitoring Point (EMP) can be completely restarted or you can restart only its networking. In either case, your connection to the Monitoring Point will be disrupted during the restart.

Restart a Monitoring Point

Restarting a Monitoring Point does not affect its software or its configuration.

To restart a Monitoring Point:

Web admin

  1. Log in to Web Admin.
  2. Click > Restart Monitoring Point.
  3. Click Confirm.
    • Access is lost while the Monitoring Point restarts.

Admin API

  1. Access the Admin API.
  2. Navigate to Appliance > PUT /appliance/.
  3. Click Try it out.
  4. In the Parameters section, for the action parameter, select reboot.
  5. Click Execute.
    • The Server response section should show Code “202”.
    • Access is lost while the Monitoring Point restarts.

Container - 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 Monitoring Point.

    kubectl get deployments
    
  3. Perform the restart.

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

    kubectl get deployments
    

Container - Docker Compose

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

  1. Login to the host the Monitoring Point is deployed on.
  2. Navigate to the directory the Monitoring Point was deployed from.
  3. Perform the restart.

    docker-compose -f mp-compose.yaml restart
    
    • Note: On Linux hosts, you may need to run sudo docker-compose -f mp-compose.yaml restart for this to execute successfully.
  4. Confirm that the Monitoring Point restarted successfully.

    docker-compose -f mp-compose.yaml ps
    
    • Note: On Linux hosts, you may need to run sudo docker-compose -f mp-compose.yaml ps for this to execute successfully.

NMP - macOS

To restart a macOS-based Native Monitoring Point (NMP):

  1. On your Mac, click the Apple icon (top left) and select ​System Preferences​. Screenshot of selecting the Apple icon then System Preferences.
  2. Click AppNeta Sequencer. Screenshot of the System Preferences dialog with AppNeta Sequencer highlighted.
  3. Enter your password if prompted, and click ​OK​.
  4. Click Restart. Screenshot of the AppNeta Sequencer Preferences screen with 'Restart' highlighted.
    • The macOS NMP software is restarted.

NMP - Windows

To restart a Windows-based Native Monitoring Point (NMP):

  1. Login to the host the Monitoring Point is deployed on.
  2. Open a Command Prompt window and Run as Administrator.
  3. Shut down the Monitoring Point.

    net stop "AppNeta Native Monitoring Point"
    
  4. Start the Monitoring Point.

    net start "AppNeta Native Monitoring Point"
    
  5. Confirm that the Monitoring Point restarted successfully.

    sc query "AppNeta Native Monitoring Point" | findstr "RUNNING"
    
    • You should see “STATE : 4 RUNNING”.

Note: You can also use the Windows Services app to restart the NMP.

Web admin

  1. Log in to Web Admin.
  2. Click Restart Appliance.
  3. Click OK.
    • Access is lost while the Monitoring Point restarts.

Restart networking on a Monitoring Point

Restarting networking on a Monitoring Point does not affect its software or its configuration.

To restart networking on a Monitoring Point:

Web admin

  1. Log in to Web Admin.
  2. Click > Restart Networking.
  3. Click Confirm.
    • Access is lost while the networking system restarts.

Admin API

  1. Access the Admin API.
  2. Navigate to Service > PUT /service/{service_name}.
  3. Click Try it out.
  4. In the Parameters section:
    1. Set service_name to “networking”.
    2. Set action to “restart”.
  5. Click Execute.
    • The Server response section should show Code “202”.
    • Access is lost while the networking system restarts.

curl

  1. In APM, navigate to > Manage Monitoring Points to determine the device hostname.
  2. Restart networking.

    curl -k -u <username> -X PUT -H 'Content-Type: application/json' -d {} 'https://<hostname>/api/v1/service/networking/?action=restart' | python -m json.tool
    
    • Access is lost while the networking system restarts.

The variables above are defined as follows:

  • <username> - the user name on the Monitoring Point.
  • <hostname> - the hostname or IP address of the Monitoring Point.

Web admin

  1. Log in to Web Admin.
  2. Navigate to Network Configuration.
  3. Click Restart Networking.
    • Access is lost while the networking system restarts.