The eG Installation Guide - eG Innovations

Installing and Configuring on Windows Environments
4. Upon restarting, the following files will be automatically created in the
\agent\logs directory:
The agentout.log file, which records details of the tests run and measures reported by the agent
to the manager
The agenterr.log and error_log files to which the runtime errors encountered by the eG agent are
logged
The agentupgrade.log file which provides the agent upgrade status.
5. The errors (if any) will be logged in the error_log file that will be automatically created in the
\agent\logs directory.
You can ‘switch off’ error logging if so required, by running the debugoff.bat file in the
\lib directory.
3.19 Performance Impact of the eG Agent
The resource utiliation of an eG agent is dependent on various factors including:
the number of components that are being monitored by the eG agent;
the specific component types to be monitored;
the frequency of monitoring;
whether the agent is monitoring applications in an agent-based or an agentless manner;
For an internal agent monitoring a single application on the server at a 5 minute frequency, the agent
typically consumes 0.1-0.3% of CPU. Network traffic generated by the agent is about 0.05 – 0.2 kbps.
The size of the agent on disk is about 100 MB. When the agent is started, its memory footprint will be
about 10-15 MB additional to that of the Java Virtual Machine. In total, the eG agent process
consumes 30 – 50 MB of memory.
For an agent that monitors multiple applications on a server, or for an agent that monitors
components in an agentless/external manner, the CPU, memory, and network bandwidth usage will be
higher.
3.20 Increasing the Memory of the eG Agent
The eG agent runs as a Java process. The maximum heap memory that can be allocated to a 32-bit
eG agent process is limited to 1.5 GB. The maximum heap memory allocation to a 64-bit eG agent
process on the other hand, is limited to 3 GB. If an eG agent has been configured to monitor many
components, then, you may have to allocate more heap memory to the eG agent. In such a case,
follow the steps below for a Windows agent:
1. Login to the eG agent host.
2. Edit the debugon.bat or debugoff.bat file in the \lib directory.
3. Look for the entry -Xmx in the file. You will find the following entry:
-Xmx128M
4. From the Xmx specification, you can infer that by default, a maximum of 128 MB of memory has
been allocated to the eG agent. If you want to increase the heap memory allocation to say, 256
MB, then your specification should be changed as indicated below:
-Xmx256M
308