Is Zabbix Resource-Intensive for Small Docker Monitoring Setups?

Hi everyone,

I’m looking for advice on using Zabbix for monitoring a small Docker setup. We currently have two hosts, each running one container, and we’re considering extending our existing Zabbix setup to monitor Docker metrics and logs.

I’d like to know if Zabbix is considered resource-intensive for a setup of this size. Here are our requirements:

  • Metrics and Logs: We need visibility into container metrics like CPU and memory.
  • Alerting: Real-time alerts for any threshold breaches.
  • Data Retention: Retention of historical data for about 15-30 days.
  • Security: SSL/TLS and access control features.

Has anyone used Zabbix in a similar small-scale Docker environment?

Thanks in advance for your insights!

Maybe you can find someone who uses Zabbix and Docker, but wouldn’t it be better to ask the question on the Zabbix forum?

https://www.zabbix.com/forum/

Zabbix users could know more about the system requirements

I assume it depends more on the number of services you want to monitor tthan on Docker.

1 Like