Trial user of NagiosXI. I feel lost. Am I?
Posted: Mon Jan 04, 2016 2:41 pm
Hi there folks
I'm currently evaluating NagiosXI and had hoped that it would fill all my needs. Have had it installed for a while but haven't had the time to conf it until now when I've had a few days away from work. I have to say, I'm a bit surprised over how complicated and tedious it is. I'm writing this post in the hope that I have missed something and that you can point me in the right direction.
The environment I want to monitor isn't that complicated. It consists of:
* Few OSX clients/servers
* Few switches, mellanox and HP
* 2 x Synology NAS
* HW Group poseidon 3266 with four sensor connected. 1 humidity and 3 temp.
* 2 x APC NetBotz 200
* 2 x APC ACRC301S, in-row coolers
* 16 x APC PDU AP8981
* 1 x APC Smart-UPS VT 40 kVA
* 1 x DDN NAS solution with 3 chassis
* 1 x Postgress database
* 1 x ftp
* 1 x http
Many of these I can monitor out of the box. Other's like the APC machines I have to resort to third party scripts for. And that's my first encounter with exchange.nagios.org. Was happy to see that there were loads of scripts for APC hardware but just as sad to see that most was abandoned skeletons that once worked or that just works for EOL models.
I have installed three scripts that works with the UPS (over snmp) to various extent. But there's really no way to in the GUI easily configure and manage graphs from what I can see? I have to set that up with templates that I have to script/code myself...? I would have expected a GUI for building graphs and relations.
When investigating graphing I tested nagiosgraph, since one apc script came with templates for it, but after a day of wrestling with it I disabled it again. When active it broke the regular graphs and either there's not a good installation guide or I'm stupid and incapable of reading and of basic understanding. Not sure if it's abandoned or not, but almost feels like it when looking at date's for releases? Same with PNP4Nagios.
For my ACRC301 in-row coolers there's no working script available that I can find. Looked at how to fix my own. But jesus christ that seems like a big endeavour. Sure, I can SNMP walk a device but to take that output and put it into the blender with MIB & OID's and then make something with perl that works with Nagios... Jeez. Tried the snmp walk wizard with the hope that it would give me an easy GUI to build something I could monitor. Couldn't find a way to force feed it just the APC MIB so what it found and the fields it populated didn't seem to make sense.
While sobbing over my failures here I instead looked at how to configure SNMP traps. Because that' a nice thing to have. But hey, the only trap here was the SNMP trap wizard. From what I can see the wizard does 0.4% of the setup and for the rest I once again have to study MIB's, OID's and endless of documentation. =/
Yes, I understand that this is a powerful front end to loads of misc tools and that this makes it very powerful. But at the same time, for a novice, it makes it into an unmanageable beast. And, yes... You might argue that "this *** is for grown up with huge unix beards, step aside puny n00b!". And you might very well have a good point there. But should it really have to be that way...?
There's a few things I fail to understand here. I'm not asking as an ***, I'm asking because I feel lost and I genuinely wonder.
* Why should I pay a premium for NagiosXI instead of using one of the various forks/clones or free solutions. Feels like I have to put in a ton of work no matter what solution I go for...?
* Have I missed something regarding my setup or is it really this tedious and complicated to get your devices monitored?
Cheers and thanks.
/Henrik
Moderator's Note: I had to edit your post a bit. Please use respectable language on our forum. Thank you!
I'm currently evaluating NagiosXI and had hoped that it would fill all my needs. Have had it installed for a while but haven't had the time to conf it until now when I've had a few days away from work. I have to say, I'm a bit surprised over how complicated and tedious it is. I'm writing this post in the hope that I have missed something and that you can point me in the right direction.
The environment I want to monitor isn't that complicated. It consists of:
* Few OSX clients/servers
* Few switches, mellanox and HP
* 2 x Synology NAS
* HW Group poseidon 3266 with four sensor connected. 1 humidity and 3 temp.
* 2 x APC NetBotz 200
* 2 x APC ACRC301S, in-row coolers
* 16 x APC PDU AP8981
* 1 x APC Smart-UPS VT 40 kVA
* 1 x DDN NAS solution with 3 chassis
* 1 x Postgress database
* 1 x ftp
* 1 x http
Many of these I can monitor out of the box. Other's like the APC machines I have to resort to third party scripts for. And that's my first encounter with exchange.nagios.org. Was happy to see that there were loads of scripts for APC hardware but just as sad to see that most was abandoned skeletons that once worked or that just works for EOL models.
I have installed three scripts that works with the UPS (over snmp) to various extent. But there's really no way to in the GUI easily configure and manage graphs from what I can see? I have to set that up with templates that I have to script/code myself...? I would have expected a GUI for building graphs and relations.
When investigating graphing I tested nagiosgraph, since one apc script came with templates for it, but after a day of wrestling with it I disabled it again. When active it broke the regular graphs and either there's not a good installation guide or I'm stupid and incapable of reading and of basic understanding. Not sure if it's abandoned or not, but almost feels like it when looking at date's for releases? Same with PNP4Nagios.
For my ACRC301 in-row coolers there's no working script available that I can find. Looked at how to fix my own. But jesus christ that seems like a big endeavour. Sure, I can SNMP walk a device but to take that output and put it into the blender with MIB & OID's and then make something with perl that works with Nagios... Jeez. Tried the snmp walk wizard with the hope that it would give me an easy GUI to build something I could monitor. Couldn't find a way to force feed it just the APC MIB so what it found and the fields it populated didn't seem to make sense.
While sobbing over my failures here I instead looked at how to configure SNMP traps. Because that' a nice thing to have. But hey, the only trap here was the SNMP trap wizard. From what I can see the wizard does 0.4% of the setup and for the rest I once again have to study MIB's, OID's and endless of documentation. =/
Yes, I understand that this is a powerful front end to loads of misc tools and that this makes it very powerful. But at the same time, for a novice, it makes it into an unmanageable beast. And, yes... You might argue that "this *** is for grown up with huge unix beards, step aside puny n00b!". And you might very well have a good point there. But should it really have to be that way...?
There's a few things I fail to understand here. I'm not asking as an ***, I'm asking because I feel lost and I genuinely wonder.
* Why should I pay a premium for NagiosXI instead of using one of the various forks/clones or free solutions. Feels like I have to put in a ton of work no matter what solution I go for...?
* Have I missed something regarding my setup or is it really this tedious and complicated to get your devices monitored?
Cheers and thanks.
/Henrik
Moderator's Note: I had to edit your post a bit. Please use respectable language on our forum. Thank you!