Page 1 of 1

Bug Report

Posted: Tue Sep 01, 2015 1:55 pm
by weveland
Team,

Just wanted to submit an issue that I was able to replicate on the Log Server.

OS: Default Appliance CentOS 6.7

Software: Nagios Log Server Version 2015R2.2

Issue: If there are input/filter configuration problems and you click save&apply they are ignored and the user isn't notified of failure.

Steps to Reproduce-
Administration=>Global Configuration
Add Input or Filter entry with syntax errors
Click apply & save.
System verifies then applies configuration.
SSH into server.
cat /usr/local/nagioslogserver/logstash/etc/conf.d/{000_inputs,500_filters}.conf
See that the changes you just made are not reflected in the file
Go back to the system and make other changes to the input/filters
Save and apply those changes.
Look around bewildered at why your parsing isn't working
Click verify and track down errors
click save
click Apply Configuration
Click Yes
go back to ssh terminal
cat /usr/local/nagioslogserver/logstash/etc/conf.d/{000_inputs,500_filters}.conf
See that changes are now included.

Re: Bug Report

Posted: Tue Sep 01, 2015 1:59 pm
by jolson
Thank you for the bug report. The 'verify' button in the Nagios Log Server Web GUI does a good job at detecting any configuration faults - I will let the developers know your thoughts and file a bug report if they deem it appropriate. Thanks!

Re: Bug Report

Posted: Tue Sep 01, 2015 2:15 pm
by weveland
I agree, the verify button does work well. My concern here is that there is no feedback to the user that there is any configuration issues as the system just doesn't apply the changes. However it happily tells you that it does.

Re: Bug Report

Posted: Tue Sep 01, 2015 4:45 pm
by jolson
I spoke with the developers about this particular problem - it looks like the functionality is already mostly built-in, and you'll be happy to hear that a bug report was submitted. The task ID of the bug report is 6385, feel free to reference this number to any Nagios Technician and we'll be happy to check on the status of the bug fix for you. Thanks!