06.05.2013 Views

The eG Installation Guide - eG Innovations

The eG Installation Guide - eG Innovations

The eG Installation Guide - eG Innovations

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Installing and Configuring on Unix<br />

6. Finally, save the starta script.<br />

7. Restart the agent.<br />

Note:<br />

Figure 2.22: <strong>The</strong> edited starta script<br />

Before attempting to administer the <strong>eG</strong> Enterprise system, ensure that sysstat package is installed<br />

on the component to be monitored (check for the existence of the iostat command on the target<br />

system). <strong>The</strong> DiskActivity Test will not function on Unix environments without the sysstat package.<br />

2.12 Performance Impact of the <strong>eG</strong> Agent<br />

<strong>The</strong> resource utilization of an <strong>eG</strong> agent is dependent on various factors including:<br />

the number of components that are being monitored by the <strong>eG</strong> agent;<br />

the specific component types to be monitored;<br />

the frequency of monitoring;<br />

whether the agent is monitoring applications in an agent-based or an agentless manner;<br />

For an internal agent monitoring a single application on the server at a 5 minute frequency, the agent<br />

typically consumes 0.1-0.3% of CPU. Network traffic generated by the agent is about 0.05 – 0.2 kbps.<br />

<strong>The</strong> size of the agent on disk is about 100 MB. While a 32-bit <strong>eG</strong> agent will consume a heap memory<br />

of 64 MB on an average, the heap memory footprint of a 64-bit agent is 128 MB on an average.<br />

For an agent that monitors multiple applications on a server, or for an agent that monitors<br />

components in an agentless/external manner, the CPU, memory, and network bandwidth usage will be<br />

higher.<br />

2.13 Increasing the Memory of the <strong>eG</strong> Agent<br />

<strong>The</strong> <strong>eG</strong> agent runs as a Java process. <strong>The</strong> maximum heap memory that can be allocated to a 32-bit<br />

<strong>eG</strong> agent process is limited to 1.5 GB. <strong>The</strong> maximum heap memory allocation to a 64-bit <strong>eG</strong> agent<br />

process on the other hand, is limited to 3 GB. If an <strong>eG</strong> agent has been configured to monitor many<br />

components, then, you may have to allocate more heap memory to the <strong>eG</strong> agent. In such a case,<br />

follow the steps below for a Unix agent:<br />

1. Login to the <strong>eG</strong> agent host.<br />

2. Edit the start_agent script in the /opt/egurkha/bin directory.<br />

3. Look for the entry -Xmx in the file. You will find the following entry:<br />

70

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!