Nagios XI vs. Splunk On-Call

Nagios is best suited in an large organization where it is production 24/7, but in SME (small/medium enterprise) you have to pay a lot to the administrator. Instead use some graphical and easy to use tool like IDERA.

Incentivized

I recommend Splunk on-call is more suited where there are high incident queues; multiple teams need to be involved in handling a P1 severity issue. Multiple levels of escalation are needed environment where automated action is required. I recommend the solution for large-scale & medium-scale business units. For small-scale business units, I see the functional value is less.

Incentivized

• 3rd party integrations via open API.
• Extremely flexible and configurable long term storage of the very detailed performance information (years of per 1-5 min perf data numbers).
• Small Nagios XI footprint (very efficient MySQL DB and flat files for perf data), making it powerful tool for thousands of checks and hundreds of reports.
• Responsive support, willing to provide resolution outside the box and by various means possible.

Incentivized

• Easily assign work/tickets between multiple users
• Supports a wide variety of software integrations
• Easy to manage scheduling tool
• As part of the Splunk toolset, provides detailed levels of data analysis at our engineers fingertips

Incentivized

• The mobile interface is newly developed and needs more development. It should provide more options for the audit log and add more detail for the configuration rollback options.
• The scheduled report should be included in standard edition.
• Master Node is configurable on LINUX platform only. We had to hire a Linux administrator

Incentivized

• The user interface can be furthe improved
• Licensing needs to be simplified and packaged as a bundle with other Splunk product like Enterprise Security
• Customer outreach can be further enhanced

Incentivized

It was a good solution with a good comprimise prize/features for our use cases

Incentivized

Good usability, it could be improved

Incentivized

Only because I never give out 10s. Nagios support goes above and beyond in helping with issues, workarounds, specific cases and requirements. Tracks customer implementation and history of the most important issues. Can’t complain (except that the team is small and quite probably overworked). Time to resolution could be much improved if only there were more folks to help around.

Incentivized

VictorOps support has proven excellent for us. Because it is such a widely used tool, there is a lot of documentation on usage, and a large community of users to lean on. Also, many engineers have had experience working with VictorOps already, and the tool is so easy to setup / manage that much support isn't really necessary.

Incentivized

It was a good solution with a good comprimise prize/features for our use cases

Incentivized

Cost efficiency is the main reason which we opted [for] Nagios as we were previously using IDERA tool with comprehensive database monitoring solutions, but the slow performance we are getting while monitoring the instance of the database.

Incentivized

Splunk On-Call integrates better with our Splunk Cybersecurity and Reporting products due to the same family tree of the same eco system. We were previously using built-in on-call from individual applications and while adequate, they were difficult to manage and support SLA varied greatly across different applications. In addition we also used xMatters which did not integrate well with SAP products nor Citrix products so we were still using more than a single on-call product which was solved by implementing Splunk On-Call

Incentivized

• Reduction of at least 10% of false alarms.
• Increased network traffic by 5%.

Incentivized

• It runs our on call rotation so it makes it easy for us.
• It integrates with Slack so it makes it easy for us to manage through Slack.

Incentivized