~Agent Status View~

This view provides a snapshot of the status of the Agent on a selected End Point, including health status, Agent state, connection status, and logging status. In addition, the view enables users to control the Agent remotely, through the Aternity Console.

The Agent Status view is useful in situations where it is necessary to manage a single Agent. For example, administrators can investigate an Agent with an unhealthy status, and view details of the Agent's recent events and statistics. After getting the Agent's logs, the administrator can disable the Agent until the problem is resolved.

The following is an example of the Windows Agent Dashboard:

The upper portion of the page displays the Aternity Agent application, which is a modified version of the End Point Dashboard. The progress bar on the top of the page provides a summary of Agent processes over the past 2 hours. Each 5-minute segment is color coded, according to the periodical health measurements from the Agent. In addition, the status of measurements for process resource consumption are shown in the progress bar, according to the detection settings configured by the administrator. For example, the CPU usage parameter might be configured as follows:

  • Green: Usage is below 50%.
  • Yellow: Usage is 50%-75%.
  • Red: Usage is over 75%.

Expanding the Agent Dashboard opens the Activities and Processes frame, which display the periodical health measurements and process resource consumption for Agent processes.

The User Experience Risk attribute is an availability-like attribute (green or red) that represents the risk of this Agent impacting the user experience on the device. The attribute is colored red in the following situations:

  • The Agent uses more CPU/memory than what the Watchdog allows, for 75% of the time monitored. For example, if the Watchdog allows the Agent to consume up to 10% CPU for up to 2 minutes, and the Agent goes to 20% CPU, after 1.5 minutes the User Experience Risk attribute is marked red, and 30 seconds later, the Watchdog will stop the Agent.
  • The Exception Filter Hook (normally used by the Agent to monitor application crashes) catches an exception that may be attributed to the Agent itself.

The Data Loss attribute is also an availability-like attribute (green or red) that counts how many events are inadvertently dropped inside the Agent due to internal factors, such as full processing queues.

Both these attributes are normally green, and turn red only under very rare conditions that call for deeper investigation to understand the root causes. Therefore, by design, the attributes indicate the existence of an anomaly, but do not reflect its magnitude (e.g., small and big data losses do not differ in appearance). The occurrence of a red attribute should normally be followed by a more thorough analysis of the Agent logs, to understand the magnitude of the issue and its causes.

The following is an example of the Mobile device Dashboard:

Note:

Mobile devices are monitored through Aternity SDK so there is no Aternity Agent application.

For both Windows and mobile devices, the Agent Current Status frame is a read-only area that provides information about the Agent's current status, including details about connection to the system, Agent configuration, and measurement statistics.

The Agent Control frame enables you to manage the Agent remotely. To send a command to the Agent, select a command from the relevant drop-down list, and then click Apply.

Options to change the Agent state include:

  • Active: Restarts a stopped Agent or approves a pending approval agent.
  • Stopped: Stops the Agent, without disconnecting it from the Aggregation Server.
  • Disabled: Stops the Agent, disconnects it from the Aggregation Server, and disables the service.
Note:

Disabled Agents cannot be restarted via the Aternity Console. They must be restarted locally.

Log Level options are:

  • Default: Default logging levels are set, as defined in the server for all Agents.
  • Debug : Debug logging level is turned on for all Agent log files.
  • Trace: Trace logging level is turned on for all Agent log files.

The Logs Download frame allows you to collect Agent logs on the Management Server. When you click Collect Logs, a message and a progress wheel appear. When the process is complete, a confirmation message is displayed. Click the Download link to open the files on the browser, or to save them to a local directory.

It is not necessary to stay on this page while logs are being downloaded. You may move to other pages of the Console, or even close the browser altogether – the log downloading will keep running in the background. When coming back to this page, the Logs Download frame will show the current status of the logs downloading task. When collection is finished, the Download link (used to retrieve the logs) appears.