Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Check Docker
Current Version
1.0.3
Last Release Date
2017-07-01
Compatible With
- Nagios 3.x
Owner
License
GPL
Hits
53898
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
memory
restarts
status
health-check results
restarts
uptime
image version(experimental)
Reviews (3)
bynebu, May 21, 2020
Hello Tim,
I managed to get it integrated into nagios core. However, i had following issues, that needed additional configuration for this plugin
1. usermod -aG docker nations (you already mentioned it)
2. i had to create a sudoers file(/etc/sudoers.d/nagios) to allow the plugin to run.
Not sure if the second point is really needed.
I managed to get it integrated into nagios core. However, i had following issues, that needed additional configuration for this plugin
1. usermod -aG docker nations (you already mentioned it)
2. i had to create a sudoers file(/etc/sudoers.d/nagios) to allow the plugin to run.
Not sure if the second point is really needed.
My devs are happy that they're getting docker alerts before the endusers can report problems which makes me happy
As already mentioned whatever use you have in nrpe.cfg to execute commands will need to be in the docker group. One thing that threw me is that I was still getting permission errors when I added my nagios user to Docker even though the user wasn't logged in. Locally executing the command after su nagios worked just fine by my NRPE checks from my Nagios server were all giving the same permissions error. I wound up having to restart the nrpe service and it resolved my issue.
I'd love some more clarification or a link to relevant Docker documentation on what exactly the --restarts flag is checking, how far back it's checking for restarts, etc.
As already mentioned whatever use you have in nrpe.cfg to execute commands will need to be in the docker group. One thing that threw me is that I was still getting permission errors when I added my nagios user to Docker even though the user wasn't logged in. Locally executing the command after su nagios worked just fine by my NRPE checks from my Nagios server were all giving the same permissions error. I wound up having to restart the nrpe service and it resolved my issue.
I'd love some more clarification or a link to relevant Docker documentation on what exactly the --restarts flag is checking, how far back it's checking for restarts, etc.
If you use nrpe you'll have an Unable to read output error
Owner's reply
You may have a user permission problem. On Ubuntu at least the NRPE daemon runs as the user 'nagios'. Docker, by default protects it's socket file by requiring membership in the docker group. Try the following
sudo usermod -a -G docker nagios
I will add logic to check for this and give a clearer error in the next release.
