Hosted Graphite vs Nagios: What are the differences?
Developers describe Hosted Graphite as "Graphite as a service". Hosted Graphite is the powerful open-source application metrics system used by hundreds of companies. We take away the headaches of scaling, maintenance, and upgrades and let you do what you do best - write great software. On the other hand, Nagios is detailed as "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.
Hosted Graphite and Nagios can be categorized as "Monitoring" tools.
Some of the features offered by Hosted Graphite are:
- Dashboards- Standard Graphite and Tasseo dashboards out of the box
- Account Sharing- Allow team members to customise graphs and dashboards
- Access Keys- Export data to external monitoring systems, dashboards and alerting systems
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
"Great customer support" is the top reason why over 3 developers like Hosted Graphite, while over 49 developers mention "It just works" as the leading cause for choosing Nagios.
Nagios is an open source tool with 60 GitHub stars and 36 GitHub forks. Here's a link to Nagios's open source repository on GitHub.
What is Hosted 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 Hosted 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
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.