Agent Vs Agentless Monitoring in cloudmon

Attribute	Agent-based Monitoring	Agentless Monitoring
Methodology	Deploy the Cloudmon agent on each server that requires monitoring.	Cloudmon uses Probes to monitors IP network endpoints, and devices in the network like routers, switches, servers and hosts supporting SNMP. Cloudmon Probe is pre-installed with Cloudmon All-in-One installation. For scalability and for the purpose of monitoring your endpoints from multiple locations, you can install, multiple probes and add it to Cloudmon controller.
How it works	Cloudmon Agent collects information and key metrics relating to he compute system (hardware/OS/hypervisor) and the processes running on the system and periodically sends them to the Cloudmon Controller over a secure channel.	The Cloudmon Probe gathers information by employing SNMP polling for network devices / Servers, while it acquires data from IP Endpoints through ping and tracepath operations. At regular intervals, the collected metrics are sent to the Cloudmon controller
Installation methods	Install a Cloudmon agent individually on every server in windows and linux environment	Cloudmon Probe is pre-installed with Cloudmon All-in-One installation. For scalability and for the purpose of monitoring your endpoints from multiple locations, you can install (on CentOS physical / virtual machine) using one-step installation, multiple probes and add it to Cloudmon controller.
Connectivity to the internet	All agents requires connectivitytowards Cloudmon Controller. In case, the Controller is deployed in public cloud or externally, agents can send the data to Cloudmon controller through a proxy server connected to the internet.	Satisfactory collection of server metrics by the On-Premise Probe doesn't requires any internet access, and the Cloudmon probe must possess connectivity to the Cloudmon controller.
Credentials	Administrative credentials for installation.	Requires SNMP credential details. Supported versions: SNMP v1/v2 and SNMP v3.
Dedicated server	Does not require a dedicated server.	Cloudmon Probe is pre-installed with Cloudmon All-in-One installation. For scalability and for the purpose of monitoring your endpoints from multiple locations, you can install probe (on CentOS physical / virtual machine) using one-step installation, multiple probes and add it to Cloudmon controller.
Status checks and real-time alerting	Performs one-minute status update and has a poll frequency of up to one second to collect the performance metrics.	For SNMP polling, performs one-minute polling frequency to collect the performance metrics. For IP endpoint monitoring, performs one-minute status update and has a poll frequency of up to one second to collect the performance metrics.
Data transfer to Cloudmon	A one-way HTTPS connection that sends data to Cloudmon Controller using the secure SSL protocol.	Uses an HTTPS connection to send data to Cloudmon Controller.
Supported OS types	Windows and Linux	For SNMP polling, any device that supports SNMP protocol For IP endpoing monitoring, any device that supports ICMP / TCP protocol
Automatic Remediation	Incident remediation through the configuration of scripts that get executed automatically based on the alert	Incident remediation through the configuration of scripts that get executed automatically based on the alert
Alerting and reporting	SMS, Zoho Desk Integration, Slack, Microsoft Teams, Email, and Customwebhook	SMS, Zoho Integration, Slack, Microsoft Teams, Email, and Customwebhook
License	Licensing is based on the no.of IP address	Licensing is based on the no.of endpoints
Performance reports	You can get report based on the available template	You can get report based on the available template
Metrices
	Agent-based	Agentless
CPU Metrics
CPU utilization	Yes	yes
CPU utilization by core	Yes	yes
Idle time, wait time, hardware, and software interrupts time	yes	Yes, if SNMP proprietary OIDs is available.
CPU Temperature	Yes	yes
Memory Metrics
Memory utilization	yes	yes
Swap memory utilization	yes	yes
Free Memory	yes	yes
Disk metrics
Disk utilization	yes	yes
Individual disk utilization	yes	yes
Disk I/O Rate	yes	Yes, if SNMP proprietary OIDs is available.
Process Monitoring
Process memory usage	yes	Yes, if SNMP proprietary OIDs is available.
Process CPU usage	yes	Yes, if SNMP proprietary OIDs is available.
Process stats of each process ( cpu usage, cpu statistics, cpu nice, memory usage, resident set size, virtual memory size)	yes	Yes, if SNMP proprietary OIDs is available.
Interfaces
I/O traffic	yes	yes
Packets received and transmitted	yes	yes
Discards and Errors	yes	yes
Operational state	yes	yes
Printers
Id	yes	No
Name	yes	No
Model	yes	No
Is_shared	yes	No
Local	yes	No
Default	yes	No
BIOS
Vendor	yes	No
Version	yes	No
Release date	yes	No
Revision	yes	No
Graphics
Vendor	yes	No
Model	yes	No
Bus	yes	No
VRAM	yes	No
VRAM_Dynamic	yes	No
Subdevice Id	yes	No
Operating system
Platform	yes	No
Distro	yes	No
Architecture	yes	No
Release	yes	No
Codename	yes	No
Kernel	yes	No
Hostname	yes	No
FQDN	yes	No
Codepage	yes	No
Logofile	yes	No
Serial	yes	No
Build	yes	No
Servicepack	yes	No
UEFI	yes	No
Chassis
Manufacturer	yes	No
Model	yes	No
Type	yes	No
Version	yes	No
Serial	yes	No
Asset_Tag	yes	No
SKU	yes	No
USB
Device_ID	yes	No
ID	yes	No
Name	yes	No
Type	yes	No
Manufacturer	yes	No
Baseboard
Manufacturer	yes	No
Model	yes	No
Version	yes	No
Serial	yes	No
Asset_Tag	yes	No
Maximum Memory	yes	No
Number of Memory Slots	yes	No
Audio
ID	yes	No
Name	yes	No
Manufacturer	yes	No
Status	yes	No
WiFi
ID	yes	No
Iface	yes	No
Model	yes	No
Vendor	yes	No
MAC	yes	No
Docker Monitoring
Docker.info.containers	yes	No
Docker.info.container_running	yes	No
Docker.info.container_paused	yes	No
Docker.info.container_stopped	yes	No
Docker.memPercent	yes	No
Docker.cpuPercent	yes	No
Docker.memUsage	yes	No
Docker.Volume.name	yes	No
Docker.Volume.created	yes	No
Docker.Volume.scope	yes	No
Docker.images.id	yes	No
Docker.images.container	yes	No
Docker.images. os	yes	No
Docker.images.dockerVersion	yes	No
Docker.images.size	yes	No
Docker.netIO	yes	No
Docker.blockIO	yes	No
Docker.containers.mount.name	yes	No
Docker.containers.port	yes	No
Docker.containers.id	yes	No

Related Articles
What are the different modes of monitoring in cloudmon?
There are three modes of monitoring: agent-based and agentless monitoring
How to configure a Monitoring Profile for an agent in cloudmon?
By default, the monitoring profile default is configured for every entity. The default profile includes all the metrics for monitoring and can be modified if required. Follow the steps to change the profile from default to the user-defined profile ...
How to install an agent in cloudmon?
The Agent can be installed on many different platforms directly on the host. Most systems have a one-line install option. Upon successful installation of the Cloudmon Agent, it is automatically discovered by Cloudmon ITIM controller, where you can ...
How to change the Agent name in Cloudmon portal?
It is possible to modify the name of an Agent even after it has been installed. To do so, you can follow these steps in the Cloudmon portal : Go to Settings > Monitoring > Hosts/Agents. Locate the Agent whose name you want to change and click on the ...
what is the purpose of agent in Cloudmon?
The Cloudmon Agent is responsible for collecting system KPIs, example CPU usage, memory utilization, and disk usage for servers, virtual machines (VMs), and hosts. These metrics are periodically pushed to the controller for monitoring and analysis. ...

Agent Vs Agentless Monitoring in cloudmon

Agent Vs Agentless Monitoring in cloudmon

Related Articles

What are the different modes of monitoring in cloudmon?

How to configure a Monitoring Profile for an agent in cloudmon?

How to install an agent in cloudmon?

How to change the Agent name in Cloudmon portal?

what is the purpose of agent in Cloudmon?