Agentless monitoring is a monitoring approach that collects performance, availability, and health metrics from servers, network devices, cloud platforms, virtualization platforms, and applications without installing monitoring agents on the target systems. Instead, it uses protocols, APIs, WMI, SNMP, SSH, or cloud-native services to gather monitoring data remotely.
There are several differences between agent-based and agentless monitoring.
As you can see, there are pros and cons to each and a combination approach to monitoring might be the best option.
Agentless monitoring is particularly useful for monitoring network devices, cloud services, storage platforms, SaaS applications, virtualization platforms, and environments where installing software agents is not permitted or not possible. Many organizations adopt a hybrid monitoring strategy that combines both agent-based and agentless monitoring to achieve complete infrastructure visibility.
Measuring the availability, response time and behaviour of each and every business transaction is key to understanding the user journey. When a user performs a transaction on a digital business service, the application owner needs to know:
With eG Enterprise, agentless monitoring is implemented in eG Enterprise using remote agents. A remote agent is capable of monitoring a number of systems and applications remotely, i.e., without requiring an agent to be locally installed on the system that is to be monitored. For monitoring Microsoft Windows systems and applications, a remote agent uses Netbios/perfmon to communicate with the operating system/applications. For monitoring Unix systems, secure shell (SSH) is used. In addition, for specific applications, the remote agent uses application-specific protocols to communicate with the application (e.g., SQLNet for Oracle databases, HTTP for WebLogic and WebSphere application servers, JDBC for Sybase, etc.). Agentless monitoring of virtual environments and cloud technologies uses the respective APIs. SNMP is widely used for agentless monitoring of network devices.
eG Enterprise supports both agentless and agent-based monitoring. Administrators can choose which parts of the infrastructure they want to monitor agentlessly, and which components to monitor using agents.
Agent-based monitoring uses software installed on the target server, device, or application being monitored to collect detailed performance data about the target. Agentless monitoring gathers metrics remotely using REST APIs, SDKs, protocols, or native platform integrations, so nothing needs to be installed on the target system. Agent-based monitoring usually gives deeper visibility, while agentless monitoring is easier to deploy and maintain. Also, since agent-based monitoring collects metrics and insights locally, it is more efficient and consumes less bandwidth and resources than agentless monitoring.
In general, whether to use agent-based or agentless monitoring is determined by the type of server, device, or application being monitored. Agentless monitoring is recommended for cloud services and SaaS applications where direct access to the server being used is not possible.
Agentless monitoring is also recommended for modern technologies like virtualization and Kubernetes where powerful APIs are available for metrics collection. Agentless monitoring is also recommended for network equipment, storage devices, and hardware monitoring, where it is not possible to install agents. Protocols such as REST APIs, SNMP, SSH, SMI-S, or CLI can be used for agentless monitoring.
Implemented correctly, agentless monitoring is secure. Strong access controls, encryption, least-privilege permissions, access only from trusted endpoints, and proper network configuration must be performed to support agentless monitoring.
Yes, agentless monitoring is well suited to hybrid cloud environments. On-prem systems are monitored with agents, network and storage devices on-prem are monitoring agentless and SaaS applications and cloud services are monitored agentless. Despite the monitoring and data collection being done in different ways, you can still get a unified view of the on-prem and cloud infrastructure and applications.