'Monitoring server file systems from a Zabbix agent in a container?
I recently noticed that the file systems automatically discovered on a server I was monitoring made no sense and looked like regular files..
After banging my head a bit, I realized it was because the Zabbix Agent on that server is run inside a container, and the file systems it is listing are the file systems that container can see, including docker file mounts! This of course defeats the purpose of monitoring that server..
I think of a couple of options, neither satisfactory:
• I can explicitly mount some of the server file systems for the agent to discover and correctly monitor, but now I have to keep this up to date • I can run the agent directly on the server, but the container route seems so clean..
Am I missing something?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
