Graphite vs Nagios: What are the differences?
Graphite: A highly scalable real-time graphing system. Graphite does two things: 1) Store numeric time-series data and 2) Render graphs of this data on demand; 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.
Graphite and Nagios belong to "Monitoring Tools" category of the tech stack.
Some of the features offered by Graphite are:
- carbon - a Twisted daemon that listens for time-series data
- whisper - a simple database library for storing time-series data (similar in design to RRD)
- graphite webapp - A Django webapp that renders graphs on-demand using Cairo
On the other hand, Nagios provides the following key features:
- Monitor your entire IT infrastructure
- Spot problems before they occur
- Know immediately when problems arise
"Render any graph" is the top reason why over 14 developers like Graphite, while over 49 developers mention "It just works" as the leading cause for choosing Nagios.
Graphite and Nagios are both open source tools. Graphite with 4.59K GitHub stars and 1.2K forks on GitHub appears to be more popular than Nagios with 60 GitHub stars and 36 GitHub forks.
According to the StackShare community, Nagios has a broader approval, being mentioned in 177 company stacks & 40 developers stacks; compared to Graphite, which is listed in 97 company stacks and 21 developer stacks.
What is Graphite?
What is Nagios?
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 Graphite?
What are the cons of using Nagios?
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
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.
Utilizando computação em nuvens e o modelo de pagar pelo uso com _graphite _nós conseguimos analisar todos os logs de informação gerada pelo sistema.
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.