Page 1 of 1

self service monitoring

Posted: Mon May 22, 2017 2:56 pm
by jkinning
I have a general question. In my environment we have a single monitoring admin, me. I am using templates to monitor basic server "stuff" like CPU, RAM, Disk Space, NSClient++, RDP, etc. What I am wondering is if anyone is doing this or if it is possible to do.

Here is my thought. Have a webpage in which application teams can add additional monitoring like application processes, services are running, website is up, etc. I think more complicated checks should and would go through me like everything is today. Is it possible to read the list of hosts so on a webpage they could select the host from a drop down? Hosts that they currently receive notifications for? They could select the host and then have additional fields for them to key in process name and service name. Then every 4 or 6 hours, whatever is appropriate, Nagios would take this information and add it to the appropriate hosts.

I know several monitoring systems integrate with a ServiceNow but even then I am not sure how that would all play out as I am far from a developer.

Anyone have any thoughts or mind sharing how they are managing the applications running on the servers that you now nothing about. Or how you communicated that you need appliation information so they can be monitored. Everything is good until something isn't running or is down. Then everyone comes to you wondering why no one was notified. I am tring to find a way so I can quit saying it isn't being monitored because no one told me to monitor it. I guess a self-service type of thing if that is possible.

Re: self service monitoring

Posted: Mon May 22, 2017 3:12 pm
by dwhitfield
Most importantly, you can probably do a lot of what you want through XI itself: https://assets.nagios.com/downloads/nag ... Rights.pdf.

To address your suggestion more directly, you could probably do something like what you suggest using the API: http://YOURSERVER/nagiosxi/help/api.php. That said, you'd need to have your own logging in the interface server. I'm thinking a single apiuser account that interfaces with the page you are talking about. You'd really want to lock down access to that server though since API access is pretty broad. Basically, given the fact that you aren't a developer, this is probably not a good idea, ***right now***.

So that right is very important because
New user permission system with more granular, well-defined permissions
is coming in XI 6. that said, it is going to be a while before XI 6. Currently, our public roadmap says Q1 2018, but I wouldn't be surprised if it's later than that. I also wouldn't be surprised if it's sooner. It will depend in large part how big of a change XI 5.5 is and when that will come out. One or both of those is also likely to depend on Core 5.0 coming out. Once Core 5.0 is out, I'll feel a lot more confident about us hitting our XI 6 target, but it's just too early to say right now.