Hi Team,
We did bulk deployment of 100s of Servers by cloning so we end up configuring only C:\ on all servers , and missing any other drives whether D: E: etc associated with each of Servers.
Is there any easy way to bring all those associated Drives as part of monitoring , instead of running the ncpa wizard for each of Host ?
--Vamsi
Nagios xi - Missing Disks to Monitor
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Nagios xi - Missing Disks to Monitor
HI Vamsi,
Hopefully, I got this right but correct me if I'm wrong. Do all the cloned servers have the same drive structure, C, D , E..etc.?
If that's the case you could group them into one large host group, and create a new service for those drives and assign it to the hostgroup.
Check out the following video for an explanation of the process.
https://www.youtube.com/watch?v=Qj_HALNyWvc
Benjamin
Hopefully, I got this right but correct me if I'm wrong. Do all the cloned servers have the same drive structure, C, D , E..etc.?
If that's the case you could group them into one large host group, and create a new service for those drives and assign it to the hostgroup.
Check out the following video for an explanation of the process.
https://www.youtube.com/watch?v=Qj_HALNyWvc
Benjamin
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
veeravamsi
- Posts: 136
- Joined: Wed Jan 23, 2019 3:35 am
Re: Nagios xi - Missing Disks to Monitor
Thats more of bulk deployment/cloning. We have varying Disks E: F: I: etc.
-
dchurch
- Posts: 858
- Joined: Wed Oct 07, 2020 12:46 pm
- Location: Yo mama
Re: Nagios xi - Missing Disks to Monitor
What you could do is add all your hosts with a D drive to a Host Group called "With Drive D" and assign the active NCPA check "Disk Usage on Drive D" to that group (don't assign it individually to each host, only to the host group), then do the same for the rest of the drive letters.
The check would look something like this:
Then on each of the monitored machines:
This necessitates having the community_string (ncpa.cfg) being the same on each of the monitored hosts.
The advantage of this is that it centralizes the setup and management. If a host drops their Drive D:, simply remove them from the "With Drive D" group, and they'll no longer receive that check.
The check would look something like this:
Code: Select all
/usr/local/nagios/libexec/check_ncpa.py -H 127.0.0.1 -t 'some-shared-token-bla-blu-blarg' -P 5693 -M 'disk/logical/D:|' -w '70' -c '90'Code: Select all
# C:\Program Files (x86)\Nagios\NCPA\etc\ncpa.cfg (Windows)
# or /usr/local/ncpa/etc/ncpa.cfg (Linux)
[api]
community_string =some-shared-token-bla-blu-blarg
The advantage of this is that it centralizes the setup and management. If a host drops their Drive D:, simply remove them from the "With Drive D" group, and they'll no longer receive that check.
If you didn't get an 8% raise over the course of the pandemic, you took a pay cut.
Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.
Discussion of wages is protected speech under the National Labor Relations Act, and no employer can tell you you can't disclose your pay with your fellow employees.