Nagios vs NetData: What are the differences?
Nagios: Complete monitoring and alerting for servers, switches, applications, and services. Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License; NetData: Real-time performance monitoring, done right!. Netdata is distributed, real-time, performance and health monitoring for systems and applications. It is a highly optimized monitoring agent you install on all your systems and containers.
Nagios and NetData belong to "Monitoring Tools" category of the tech stack.
"It just works" is the top reason why over 49 developers like Nagios, while over 8 developers mention "Free" as the leading cause for choosing NetData.
Nagios and NetData are both open source tools. It seems that NetData with 39.4K GitHub stars and 3.48K forks on GitHub has more adoption than Nagios with 60 GitHub stars and 36 GitHub forks.
Uber Technologies, Dropbox, and 9GAG are some of the popular companies that use Nagios, whereas NetData is used by Augmedix, Kistriver, and Veaver Inc.. Nagios has a broader approval, being mentioned in 177 company stacks & 40 developers stacks; compared to NetData, which is listed in 8 company stacks and 11 developer stacks.
What is Nagios?
What is NetData?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Nagios?
What are the cons of using NetData?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:
By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.
To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...
(GitHub : https://github.com/m3db/m3)
We use Nagios to monitor our stack and alert us when problems arise. Nagios allows us to monitor every aspect of each of our servers such as running processes, CPU usage, disk usage, and more. This means that as soon as problems arise, we can detect them and call out an engineer to resolve the issues as soon as possible.
We use Nagios to monitor customer instances of Bridge and proactively alert us about issues like queue sizes, downed services, errors in logs, etc.
We use nagios based OpsView to monitor our server farm and keep everything running smoothly.