Reporting on SCheduled Downtime
Re: Reporting on SCheduled Downtime
That might have to do with external commands, which would not be tied to a specific XI user that could be identified. Just a guess though - we'll leave this open for Troy's comments.
Former Nagios employee
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Reporting on SCheduled Downtime
Glad it works as expected 
Yeah I could not determine who the user is that submits these actions. The user is not recorded in nagios.log and more specifically it not recorded in the database from whence I pull the data. I think this needs to be a nagios core feature request. I did see an old feature request for Nagios 3.3.1 that was submittied in 2011 but nothing happened with it http://tracker.nagios.org/view.php?id=236
Yeah I could not determine who the user is that submits these actions. The user is not recorded in nagios.log and more specifically it not recorded in the database from whence I pull the data. I think this needs to be a nagios core feature request. I did see an old feature request for Nagios 3.3.1 that was submittied in 2011 but nothing happened with it http://tracker.nagios.org/view.php?id=236
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
Fred Kroeger
- Posts: 588
- Joined: Wed Oct 19, 2011 11:36 pm
- Location: Perth, Western Australia
- Contact:
Re: Reporting on SCheduled Downtime
Thanks Troy .
Nagios - Can this be progressed? I can't see much point in submitting feature requests for this if they get ignored for 4years?
If we're promoting Nagios as an Enterprise monitoring solution, then all user actions need to be logged eg: Start/End/cancelling downtime, Enable/disable notifications,etc.
regards... Fred
Nagios - Can this be progressed? I can't see much point in submitting feature requests for this if they get ignored for 4years?
If we're promoting Nagios as an Enterprise monitoring solution, then all user actions need to be logged eg: Start/End/cancelling downtime, Enable/disable notifications,etc.
regards... Fred
Re: Reporting on SCheduled Downtime
As the disable notifications is getting abused sometimes by colleagues who don't understand downtime and acknowledgments, it does seem like a nice feature to know who did it. It would maybe be worth to make a new feature request for Nagios Core 4 or so? I'll +1 it if someone makes it. 
Nagios XI 5.8.1
https://outsideit.net
https://outsideit.net
Re: Reporting on SCheduled Downtime
Willem, this info is available in the "Audit Log", i.e.
Code: Select all
2015-05-21 09:47:48 24056 Nagios XI SECURITY adele 192.168.x.x User logged out
2015-05-21 09:47:44 24055 Nagios XI INFO localhost cmdsubsys: User submitted a command to Nagios Core: DISABLE_HOST_NOTIFICATIONS;CentOS-NCPA
2015-05-21 09:47:44 24054 Nagios XI INFO adele 192.168.x.x User submitted a command to the subsystem (ID=16)
2015-05-21 09:46:40 24053 Nagios XI SECURITY adele 192.168.x.x User 'nagiosadmin' masqueraded as user 'adele'Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Reporting on SCheduled Downtime
I'm glad I could help! 
Be sure to check out our Knowledgebase for helpful articles and solutions!
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Reporting on SCheduled Downtime
Thanks Ludmill, I did not think to look in the Audit Log.
I had a look at the audit log and the possibility of updating the History Tab to include this information.
I have decided not to, based on two reasons.
1) The Audit Log in the Admin menu is an "Enterprise License" feature. Hence I feel that this is a license value add which my free component should not contradict.
2) The Audit Log is only available to Admins. The History tab can be used by read-only users so providing information which is only accessible via the Admin tab would feel like a security/privacy hole.
At least we know the information is available, it's just an extra click or two away.
However ... maybe Nagios Enterprises could acquire the History Tab from me (at a nominal fee), improve it to include this information (and take into account security/privacy stuff) and make it part of the XI Product .... we can dream anyway

I had a look at the audit log and the possibility of updating the History Tab to include this information.
I have decided not to, based on two reasons.
1) The Audit Log in the Admin menu is an "Enterprise License" feature. Hence I feel that this is a license value add which my free component should not contradict.
2) The Audit Log is only available to Admins. The History tab can be used by read-only users so providing information which is only accessible via the Admin tab would feel like a security/privacy hole.
At least we know the information is available, it's just an extra click or two away.
However ... maybe Nagios Enterprises could acquire the History Tab from me (at a nominal fee), improve it to include this information (and take into account security/privacy stuff) and make it part of the XI Product .... we can dream anyway
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.