Use REST API calls to retrieve egress details

There are use cases where the manager is not running, and all tasks are completed through CLI or REST API.  In the WebUI there are some reports in the dashboard that the Manager generates.  One example is the Ingress and Egress Exposure reports.  For this case, a REST API call is available to return the conversations that can be used to gather the same information.

The REST API endpoint /v1/conversation will return connections.  The JSON result contains two sections: conversations and endpoints.  You will need to filter with to/from external to find the IDs, and they reference the IDs from the endpoints for the display_name.  Here's the jq example to identify the pods for egress.  

❯ cat conversation.json | jq -r '.conversations[] | select(.to == "external") | .from' | sort | uniq | while read FROM; do cat conversation.json | jq -r --arg v $FROM '.endpoints[] | select(.id == $v and .state != "exit") | .display_name';done

To see the egress server IP addresses, you must make subsequent calls to /v1/conversation/<container_id>/external.  Here's a script that will save each connection detail into a JSON file named with friendly display_name.

#!/bin/bash

# please remember to specify the controller ip address here
_controllerIP_="10.1.1.2"
_controllerRESTAPIPort_="443"
_neuvectorUsername_="admin"
_neuvectorPassword_="admin"

curl -k -H "Content-Type: application/json" -d '{"password": {"username": "'$_neuvectorUsername_'", "password": "'$_neuvectorPassword_'"}}' "https://$_controllerIP_:$_controllerRESTAPIPort_/v1/auth" > /dev/null 2>&1 > token.json
_TOKEN_=`cat token.json | jq -r '.token.token'`

curl -k -H "Content-Type: application/json" -H "X-Auth-Token: $_TOKEN_" "https://$_controllerIP_:$_controllerRESTAPIPort_/v1/conversation" > /dev/null 2>&1 > conversation.json
_FROM_=`cat conversation.json | jq -r '.conversations[] | select(.to == "external") | .from' | sort | uniq`

while IFS= read -r line
do
_DISPLAYNAME_=`cat conversation.json | jq -r --arg v $line '.endpoints[] | select(.id == $v and .state != "exit") | .display_name'`
curl -k -H "Content-Type: application/json" -H "X-Auth-Token: $_TOKEN_" "https://$_controllerIP_:$_controllerRESTAPIPort_/v1/conversation/$line/external" >> $_DISPLAYNAME_.json
done < <(printf '%s\n' "$_FROM_")

curl -k -X 'DELETE' -H "Content-Type: application/json" -H "X-Auth-Token: $_TOKEN_" "https://$_controllerIP_:$_controllerRESTAPIPort_/v1/auth" > /dev/null 2>&1
rm token.json

The application details can be extracted from the conversations.