Connector health monitoring

Load indicator helps to assess the health of connector based on performance metrics like disk, CPU, memory, traffic and active dialouts.

The EAA connector card helps you troubleshoot the connector issues, and directly access applications, directories associated with the connector. If your connector has high load, you can improve its health by reducing the load.A connector card on the EAA Management portal, under Connectors looks like:

Connector version (EAA connector version/OS version). Indicates the EAA connector’s version and the OS version of the server it is installed on.

Geo IP. EAA infers the geographical location of the connector from the IP address and displays it in the connector card. Choose the connector closest to the application’s Akamai Cloud zone location.This can improve the performance of your apps by reducing the latency.

APPLICATIONS UP/DOWN. Applications Up are the apps that are deployed and running successfully. Applications Down are the apps in ready to deploy state or deploy failed state. You can click on applications up down link to filter only applications associated with this connector. You can make any configuration changes like adding another connector, change the connector and redeploy the application.

DIRECTORIES UP/DOWN. Directories Up are the directories that are reachable and have network connectivity. Directories Down are the directories that are unreachable and have no network connectivity. You can click on the directories up down link to filter only directories associated with this connector. You can make any configuration changes to the directory like adding another connector, change the connector.

Load. The load on the connector is indicated by a thermometer. It is an aggregate of different performance metrics namely system resources like CPU, memory, disk utilization, traffic and the number of active dial-outs. The active dialouts are the total number of outbound connections from all applications and directories associated with the connector. You can interpret the load as follows:

Interpretation of Load based on performance metrics like CPU, Memory, Disk, Traffic and Active Dialouts
Load Interpretation Performance metrics is based on
Red thermometer Performance metrics > 70% Any of the System resources (CPU, Mem, Disk, Traffic) or Active Dial-outs are more than 70%
Orange thermometer Performance metrics - 50% to 70% Any of the System resources (CPU, Mem, Disk, Traffic) or Active Dial-outs are between 50% - 70%
Green thermometer Performance metrics < 50% All of the System resources (CPU, Mem, Disk, Traffic) and Active Dial-outs are less than 50%

You can click on the Performance icon on the connector card to see the different performance metrics for a selected time range of 1 hour, 4 hours, 1 day, or 7 days.

Note: You might need to wait for the data to load if it is 7 days.

System. The chart shows the values for CPU, memory, disk and traffic for the time range. You can click on the legend for any system resources to deselect it and remove it from the graph.

For example, The disk usage for the connector is more than 50% and therefore the load indicator is medium.

Resource. Shows the total number of dialouts of all access-applications (web, SSH, RDP), directories. The total dialout is a sum of active dailout and idle dialout. Active dailout is when there is active traffic between the connector and the EAA cloud when the application is in use. Idle dialout is the dialout when the application is idle and is not in use. The dialouts are shown as 120 second data for all applications.

Applications. Shows the active connections per app for the top five apps or all the apps associated with the connector, that are used by the users of the organization. You can also de-select each of the applications and remove it from the graph. If you hover over the graph you can see which application has active connections.

You can save any of these graphs as a gif image and provide it to Akamai support when you see any unusual behavior. You can also zoom-in, zoom-out, and restore the graphs to examine specific points.

Troubleshoot high-load issues.

When any of the System resources (CPU, Mem, Disk, Traffic) or Active Dial-outs are more than 70% for the connector, it’s load is high. For optimal performance for your users, it is best to reduce the load on your connector. When you see a high load on your connector:

  1. Click the performance icon on the connector card where the thermometer indicates high-load (red) to see the system, resource and applications graphs.
  2. Check which performance metric is above 70%.
  3. If it is caused by CPU, Mem, Disk values being too high in utilization, check connector requirements and add additional hardware if required. If it does not fix the problem, contact support.
  4. If it is caused by too much traffic in the System graph or too many total active dialouts of all applications and directories in the resource graph, check the applications graph. Disable each application at a time and find the application causing the highest dialout.
  5. Add another connector for the application and see if the traffic reduces, dialouts reduce, and the load changes to medium. If it does not fix the problem, contact support.
    Note: RDP applications, TCP-type client-access applications, and tunnel-type client-access applications may show higher dialouts than other apps like web, SSH, or VNC apps.