eG Administration
 

AGENTS - STATUS

The eG manager is able to determine and report the operational status of all the eG agents in the target environment. The sections that follow will discuss how to view this status information.

If you select the Agent Status option from the Agents tile, you will be lead to the AGENTS - STATUS page, which will provide status information for agents based on the agent types.

To obtain the status of the eG agents of a particular type, the administrator has to first select the type of agent (whether basic, premium, external, or remote) from the Agent type list box. If the Named User license is enabled, the eG Enterprise system provides you with a single, central interface using which you can instantly ascertain the current status of the internal agents (if any) that are monitoring the thin client and VDI components in your environment! In this case, an additional Agents for user licensed types option will appear in the Agent type list box.

The IP address / host names of the agents of the selected type will then be displayed. A against each agent indicates that the agent has been deployed. A symbol appearing against each agent implies that the agent has not been deployed. While the symbol indicates that the agent is running currently, the symbol in the Status column indicates that the eG agent is not running.

Also, using the Search text box, you can find out the status of a particular agent. To know the status of a particular agent, just specify the IP address / host name of that agent in the Search text box, and then click the ‘magnifying glass’ icon next to it. The status of the specified agent will then appear. If the exact IP address / host name of the agent is not known, then a string or a character that features in the IP / host name of the agent can be provided in this text box. Multiple search conditions can be specified as a comma-separated list.

To know the agents that are currently in a particular state, simply select an Agent status (which can be Running/Not Running/All). The default selection here is All.

To obtain a brief summary of all the agents in the target environment, click the Agent Summary button.

You can even remotely initiate an agent-restart, by simply clicking on the icon that corresponds to an agent. To restart all agents, click on the Restart All Agents button in this page. Doing so immediately sends out restart requests to all the agents that are currently running and reporting metrics to the eG manager. If an agent is not running currently, then eG Enterprise sends out the restart request soon after that agent starts running.

You can also stop an eG agent from the eG management console itself, using this page. Click on the icon corresponding to an eG agent, to stop that agent. Doing so immediately sends out a stop request to that agent. The next time that agent sends metrics to the manager, it reads the stop request and serves it.

If an administrator needs to be alerted upon login, about agents that are not reporting measures to the manager, then do the following:

  1. Open the eg_services.ini file in the <EG_HOME_DIR>/manager/config directory.
  2. In the [MISC_ARGS] section, set the AlertAgentsNotRunning flag to Yes (default is No).
  3. Once this is done, the next time the administrator logs into the admin interface, a message box to that effect will appear, if any agents are not running.

Note:

An eG agent can be configured to run specific tests once a day or once every few hours. You can configure the eG manager to exclude tests that are infrequently run when it determines whether an agent is running or not. To do this, modify the value of NotReportingCutoffFactor in the [MISC_ARGS] section of the eg_services.ini file. By default, tests running with measure period of greater than 20 minutes are not considered by the eG manager for determining if an agent is running or not.

Also, by default, output logging is disabled for the eG agents configured in an environment. The eG Enterprise system allows you to enable output and error logging for a specific agent from the eG administrative interface itself, thereby saving you the trouble of running the RunAgent.bat file to achieve the same. When output logging is enabled, an agentout.log file is created in the <EG_INSTALL_DIR>\agent\logs directory to which details of the tests run and measures reported by that agent to the manager are recorded. To enable output logging for an agent, set the Output Logging Enabled? flag for that agent to ON. When you attempt to enable output logging, a message box will appear, requesting your confirmation to enable output logging for that agent.

Click on the OK button in the message box to enable output logging or the Cancel button to disable it. You can then click on the icon that corresponds to an agent in this page to view both error logs and output logs related to that agent. Clicking on the icon will lead you to AGENT - LOGS page, where the contents of the error_log of the corresponding agent can be viewed by default.

Note:

If you have turned on output logging for an eG agent using the AGENTS - STATUS page, then you should not turn off output logging for that eG agent by manually running the RunAgent.bat file. Likewise, if you have turned on output logging for an eG agent by running the RunAgent.bat file, then you should not turn it off using the AGENTS - STATUS page.

Clicking on an agent displayed in the AGENTS - STATUS page will lead you to the AGENT INFORMATION page, which provides some additional information of that eG agent.

Moreover, if the Agent type chosen is External Agents or Remote Agents, then you will also be able to view the count of hosts assigned (if any) to each external/remote agent. For this, you will have to click on the > button that pre-fixes an agent. Beneath the assigned host count, the specific hosts that have been assigned to that agent will also be listed. From a single glance therefore, you can precisely identify the external/remote agents that are currently being utilized, and those that are not.

If too many components are to be monitored by an eG agent, you may have to allocate more heap memory to the eG agent. To achieve this, you can click on the icon that corresponds to the eG agent. This will lead you to the AGENT XMX page using which you can assign additional heap memory to the eG agent.

To add more hosts to an external/remote agent, click icon that corresponds to an agent. This will lead you to the ASSIGN - EXTERNAL AGENTS page or ASSIGN - REMOTE AGENTS page (as the case may be) using which you can assign more hosts to the agent or disassociate existing hosts from the agent.

If the agent type chosen from the Agent type list box is Agents for user licensed types, then you will be able to view the status (whether installed or not and whether running or not) of those agents that are monitoring the thin client and VDI components in your environment in an agent-based manner - in other words, by selecting this option, you can determine the status of those internal agents that are monitoring the thin client and VDI components.

eG's Remote Control Action capability allows an administrator to remotely and securely access any monitored server in an IT infrastructure and to execute remote commands in order to perform detailed analysis of problems and to initiate corrective actions against them. This page also allows you to view the mode of operation of the eG agent, so that you can remotely control the eG agent if needed, and run commands on them. For this, click on the icon against each agent.