Nagios Support Forum

I feel there are several things needed to advance Nagios Log Server outlined below:
1.) Incorporate latest technologies:
a.) Latest stable ELK stack (5.0.1)
b.) Latest PHP 7 stack.
c.) Postfix over Sendmail.

2.) Provide detailed instructions OR FIX INSTALL SCRIPT for installation on Enterprise-grade OS/systems. (Are you really going to run a central-logging solution on un-hardened servers or a desktop OS?)
(Current NLS install script does not work on hardened systems with SEL, DoD STIG'd, etc.
NLS does not work correctly after install because of SEL permissions/ACLs on /usr/local/nagioslogserver directories presumably.)
a.) CentOS 7 / RHEL7 with SELinux enabled.
b.) SLES with SEL / AppArmor configured.
c.) Install script on CentOS7/RHEL7 should recognize latest software versions and not try to re-install old/outdated packages.
(i.e: CentOS7 with PHP 5.6 installed, the install script tries to install PHP 5.4, the way-out-dated default from CentOS/RH.)

3.) Provide actual administrator guides to NLS. Not the "dumbed-down" end-user guide that gives no details to what is happening on the system, or what to do if "click here" doesn't work.
a.) Explain the contents/purpose of each directory tree and what processes/user accounts need access to them. (/usr/local/nagioslogserver; /store; /var/www/html/nagioslogserver; &etc.
b.) Please explain how to set the most restrictive permissions, etc. on each directory, etc. (This should be set by default with the installation script.)
c.) Provide "sizing/capacity" recommendations for deployments. (i.e.: [Not an actual answer] For 50,000,000 entries per second with 1yr log retention, you should have an 8-node NLS cluster of 8GB/2CPU/2TB CentOS 7/RHEL7 64-bit each.)

All of the above facilitates deployment in commercial deployments, as well as supporting them in enterprise-wide deployments.

Thank you.

We will leave this open for a additional response, but you can now see some of our future NLS plans (and possible release dates) at https://www.nagios.com/roadmaps/

To specifically address your concerns:
1. a. since our components are modified, they get updated individually. We are targeting Elasticsearch 1.7.5 and Logstash 2.x.
1. b. currently, we do not have specific plans for PHP7. Once we do have specific plans, they will be added to the roadmap.
1. c. mail can be set up to use different MTAs. Are you having a specific problem or just wanting us to change defaults? If you can explain what you want out of the mail situation in more detail, than I am happy to put in an internal feature request on your behalf.

2. a. The problem is each group will set things differently and it will be impossible to support. We do have some individuals working with SELinux on some of our software, but it remains unsupported, and will for the foreseeable future.
2. b. For the foreseeable future, we will not support SLES. It is something we would like to do in the future, but again, it will not be in the foreseeable future. We have no issue with other distributions and OSes (Solaris, BSD, AIX, etc.), it's just a matter of developer time.
2. c. Generally speaking, our software installs old versions if it was coded with old versions in mind. If you have a specific version that is not needed for our software, we can certainly test and file an internal feature request for an upgrade.

3. Our documentation is currently undergoing a massive overhaul. If you have specific documents you thing need fixed, we can certainly take a look at them. One thing to consider too is that we do offer consulting. That's obviously you-specific, rather than waiting for us to upgrade and complete documentation. Please let us know if that is something that would interest you.