Tools / Apache HertzBeat Interview Questions
Why is HertzBeat considered agentless compared to Zabbix?
Zabbix's most complete data collection relies on installing the Zabbix Agent on each monitored host to gather low-level OS and application metrics; HertzBeat instead connects outward using protocols the target already exposes.
| Zabbix | HertzBeat |
| Agent installed and maintained on each host for full metric depth. | No agent; connects via HTTP, JMX, SSH, SNMP, JDBC, etc. |
| Agent upgrades needed across the whole fleet. | Only the central manager/collector needs upgrading. |
| Agentless mode exists but is more limited. | Agentless is the default, primary design. |
The trade-off is that some very low-level OS metrics an installed agent can see natively may require SSH command execution in HertzBeat instead, which is slightly heavier per call but avoids fleet-wide agent management entirely.
In Zabbix, the deepest OS-level metrics typically require:
A trade-off of HertzBeat's agentless approach is:
More Related questions...
