How to test HTTP using the Auvik Collector diagnostic shell

Access the diagnostic shell on the Auvik Collector

• Windows:
  • Launch Command Prompt as Administrator.
  • Navigate to the install directory, e.g., cd C:\auvik.
  • Run:

    AuvikAgentService -shell

• Linux/Docker:
  • With Docker Compose:
    • From the host machine, open a terminal window
    • Change directories to the location of the Docker compose configuration file

    • Run the following command to start the agent shell, replacing <SERVICE_NAME> with the service name defined within the Docker compose file:

      docker compose exec -it <SERVICE_NAME> /var/auvik/bin/agent -x

      Note: The <SERVICE_NAME> will be dependent on the deployment configuration. The service name will be based on the entry within the Docker compose file, specifically under the services section.

  • Standalone Docker:If your Docker image was not deployed using Docker compose, or you do not have access to the Docker compose configuration, then the following Docker commands can be used to start an agent shell process.From the host machine, open a terminal window

    • Run the following Docker command:

      docker exec -it <container_name_or_id> /var/auvik/bin/agent -x

      Note: The <container name/id> will be dependent on the deployment. If using Docker compose for the deployment, this will be the container_name used in the docker-compose.yaml file.
      
      If no name was specified during the configuration, a Docker will set a default name. This can be found using Docker ps command to list all running containers. Once the correct container has been identified, the container id OR the container name can be used in the above command.  Failure to keep the Docker image up to date can cause the collector to fail with these updates, causing instability and disconnects.

• Virtual Collector:
  • Open the collector’s VM console via your hypervisor.
  • At the menu, select Option 6, then confirm with Y—this drops you into the bash shell.
  • Run this command

    sudo /usr/share/agent/bin/agent_shell

Testing HTTP

The diagnostic shell contains a simple HTTP tester. It will attempt to fetch any URL, although note that the given URL must have at least a slash after the hostname to be considered valid by the remote system.

http http://<ip>/

For example:

auvik> http http://10.0.40.1/

http_message {
 response {
   status: 401
   entity {
     content_type {
       main_type: "application"
       sub_type: "octet-stream"
     }
     data: "401 Unauthorized\r\n"
   }
   headers {
     key: "Date"
     value: "Mon, 30 May 2016 15:06:03 GMT"
   }
   headers {
     key: "Server"
     value: "cisco-IOS"
   }
   headers {
     key: "Connection"
     value: "close"
   }
   headers {
     key: "Accept-Ranges"
     value: "none"
   }
   headers {
     key: "WWW-Authenticate"
     value: "Basic realm=\"level_15_access\""
   }
   protocol: HTTP_1_1
 }
}