Nagios Core vs. VictoriaMetrics Community

Nagios monitoring is well suited for any mission critical application that requires per/second (or minute) monitoring. This would probably include even a shuttle launch. As Nagios was built around Linux, most (85%) plugins are Linux based, therefore its more suitable for a Linux environment.

As Nagios (and dependent components) requires complex configurations & compilations, an experienced Linux engineer would be needed to install all relevant components.

Any company that has hundreds (or thousands) of servers & services to monitor would require a stable monitoring solution like Nagios. I have seen Nagios used in extremely mediocre ways, but the core power lies when its fully configured with all remaining open-source components (i.e. MySQL, Grafana, NRDP etc). Nagios in the hands of an experienced Linux engineer can transform the organizations monitoring by taking preventative measures before a disaster strikes.

Incentivized

Best suited, where your data is highly cardinal since it does a better job at maintaining it than other competitors. It is also well suited if you are using Prometheus and are looking for something that is less hungry for resources in comparison since the migration would be easier. But in case the company is small and wants a solution which is cheap and relies on built-in visualizations, it is not something that is suited. Although it takes fewer resources than Prometheus, it is still resource-intensive and attracts a high cost for maintenance.

Incentivized

• Monitoring of services is one of the biggest benefits for our company. Being able to respond in a timely fashion keeps business smooth.
• Hardware and device monitoring are easy to set up with proper parameters.
• Notification to key staff to be able to respond quickly makes issues go away faster.

Incentivized

• Easy to configure and manage
• Ready to be configured at cloud and microservices
• Easy to scale vertically and horizontally

Incentivized

• Nagios could use core improvements in HA, though, Nagios itself recommends monitoring itself with just another Nagios installation, which has worked fine for us. Given its stability, and this work-around, a minor need.
• Nagios could also use improvements, feature wise, to the web gui. There is a lot in Nagios XI which I felt were almost excluded intentionally from the core project. Given the core functionality, a minor need. We have moved admin facing alerts to appear as though they originate from a different service to make interacting with alerts more practical.

Incentivized

• Community and Eco system -> Although it supports the ecosystem of Prometheus, it is still troublesome for someone who's not using Prometheus
• Configuration is not so easy, especially if you are a beginner, you will struggle a bit. Even the documentation is not so welcoming for beginners
• Built-in Visualisation is bare minimal, leading almost everyone to use some other extension/tool

Incentivized

We're currently looking to combine a bunch of our network montioring solutions into a single platform. Running multiple unique solutions for monitoring, data collection, compliance reporting etc has become a lot to manage.

Incentivized

The Nagios UI is in need of a complete overhaul. Nice graphics and trendy fonts are easy on the eyes, but the menu system is dated, the lack of built in graphing support is confusing, and the learning curve for a new user is too steep.

Incentivized

I haven't had to use support very often, but when I have, it has been effective in helping to accomplish our goals. Since Nagios has been very popular for a long time, there is also a very large user base from which to learn from and help you get your questions answered.

Incentivized

Because we get all we required in Nagios [Core] and for npm, we have to do lots of configuration as it is not as easy as Comair to Nagios [Core]. On npm UI, there is lots of data, so we are not able to track exact data for analysis, which is why we use Nagios [Core].

Prometheus only support PromQL and it is very complex with different exporter required for different requirement like Windowsexporter,linixexporter,sqlexporter etc but VictoriaMetrics is very simple comapred to it. VictoriaMetrics support both PromQL and MetricQL and can be integrated with Graphana easily. It is very easy to setup and learn compared to mutiple Prometheus exporters

Incentivized

• With it being a free tool, there is no cost associated with it, so it's very valuable to an organization to get something that is so great and widely used for free.
• You can set up as many alerts as you want without incurring any fees.

Incentivized

• Lowered our infra costs in comparison with our older tools
• Need minimal effort for migration since it already supports Prometheus ecosystem
• Saved on Storage costs

Incentivized