|Application Type||Applications that can be monitored remotely (i.e., agentless)|
|Databases||Oracle, Microsoft SQL, Sybase, Informix, MySQL|
|Application Servers||WebLogic, WebSphere, Coldfusion|
|Mail Servers||Exchange server, Lotus Notes|
|Microsoft Applications||Domain Controller, Active Directory, File and Print Servers, DHCP servers|
|Messaging Servers||IBM MQ|
|Terminal Servers||Citrix, Microsoft Terminal server|
|Operating Systems||Solaris, AIX, HPUX, Linux, OS/400, Novell Netware, Windows NT, Windows 2000, Windows 2003, Windows XP, Windows 2008, VMware ESX, Citrix XenServer|
There are interesting tradeoffs between the agentless monitoring and the agent-based monitoring approaches.
|Agentless Monitoring||Agent-based Monitoring|
|Ease of deployment||Easier to deploy because software installation is required only on the remote data collection system.||Agents need to be deployed on all the target servers in the infrastructure. Once deployed, the eG agents require no direct maintenance as they can be auto-upgraded from the central management console.|
|Security||The remote data collector must be allowed to communicate with the target system on different ports. The data collector may also need to be installed with domain administration privileges to be able to access the remote systems.||Much more secure than the agentless model. The agent to application / OS communications are handled internal to the server. Hence, no additional firewall rules need to be configured to allow monitoring.|
|Overheads||This approach introduces additional network traffic as the raw performance data is transported to a remote data collector for analysis.||The agent installed on a server collects data locally and only the processed final results are transported to the console. Hence, this approach results in lower network traffic and processing overheads.|
|Breadth & Depth of monitoring||Not all applications and operating systems have built-in monitoring capabilities and hence the coverage of the agentless approach is less than that of the agent-based approach. Moreover, the depth of the diagnostic information obtainable from the agentless approach is limited.||The agent-based approach provides deeper, broader monitoring. Some of the capabilities available in the eG agent-based solution only include the detailed diagnosis capability (eg., if the CPU usage is 100% which process is consuming CPU?), the eG web adapter for web transaction monitoring, and the eG remote control action capability for initiating corrective actions when abnormal situations are detected.|
The agentless monitoring solution is ideal for small enterprises where security or the network traffic involved in the monitoring are not key criteria in deciding a monitoring approach. For more critical, complex environments where in-depth monitoring, root-cause diagnosis, and problem resolution are key, the agent-based approach is more appropriate. The automatic capability of the eG agents ensures that the eG agent-based monitoring solution requires near zero maintenance, similar to an agentless solution.