Nagios XI vs. Splunk Infrastructure Monitoring

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

Splunk Infrastructure Monitoring is well suited for any complicated environment where you have apps and servers across multiple clouds and platforms and products. If you have a data centre where all your apps and servers are in one single network, you could probably get away with older solutions. But for any modern, complex, hybrid-cloud microservices environment, Splunk Infrastructure Monitoring is a must-have.

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

• SignalFX handles historical metric aggregation exceptionally well, providing a multifaceted approach to event detection based on anomalies.
• SignalFX's cost is incredibly flexible with their pricing model of DPM (data-point per minute) vs the traditional "per host" model that most monitoring SaaS use.
• SignalFX support is responsive and knowledgeable, very eager to help solve your immediate problems.
• SignalFX integrations is vast and constantly growing, making adoption easy even when multiple different open-source technologies are used in your stack.

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

• Better integration with our clients (native mobile clients SDKs will be great).
• A way to easily tag filters and move them across metrics/formula.
• Alert system to easy false [alarm] and hard to configure.
• Be able to have group more dimensions (and have more values on each).

Incentivized

Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net

Incentivized

I find that learning the interface can take some time. We need a better show-and-tell on how the Teams pages, Dashboard Groups, Dashboards and charts delay. Advance SignalFlow is sometimes hard to build. Some better samples of advanced SignalFlow would be helpful. For example, Splunk SPL has a vast resource of examples.

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

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

They’re not for the same purpose but we’re using NewRelic and Honeycomb for monitoring purposes. NewRelic is used for HTTP client monitoring for system related throughput, error, database and external client monitoring. Honeycomb is used to monitor actual HTTP request/response values. Splunk [Infrastructure Monitoring] is used for real-time application related throughout and error monitoring.

Incentivized

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

Incentivized

• Reduced downtime.
• Caused us to get a lot of spam when we redeployed apps and old instances stopped sending metrics. Muting alerts solves this, but people often forget to do it or do it incorrectly.
• Helped us find historical info about instances/apps.

Incentivized