Grafana vs Nagios: What are the differences?
Grafana: Open source Graphite & InfluxDB Dashboard and Graph Editor. Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins; 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.
Grafana and Nagios belong to "Monitoring Tools" category of the tech stack.
Some of the features offered by Grafana are:
- Create, edit, save & search dashboards
- Change column spans and row heights
- Drag and drop panels to rearrange
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
"Beautiful" is the primary reason why developers consider Grafana over the competitors, whereas "It just works" was stated as the key factor in picking Nagios.
Grafana and Nagios are both open source tools. It seems that Grafana with 29.7K GitHub stars and 5.63K forks on GitHub has more adoption than Nagios with 60 GitHub stars and 36 GitHub forks.
Uber Technologies, 9GAG, and Harvest are some of the popular companies that use Grafana, whereas Nagios is used by Uber Technologies, Dropbox, and 9GAG. Grafana has a broader approval, being mentioned in 577 company stacks & 325 developers stacks; compared to Nagios, which is listed in 177 company stacks and 40 developer stacks.
What is Grafana?
What is Nagios?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Grafana?
What are the cons of using Nagios?
What tools integrate with Nagios?
analyze heap dump and many logging or traces
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 Grafana to view live stats relating to our servers such as memory and CPU usage. We also use Grafana to monitor our gaming servers for data such as latency and player counts. This allows us to generate effective analytics and see when problems arise.
Everyone likes graphs, right?! This isn't a tool we actively use right now, but paired with Prometheus we want to use it to have visual monitors on things like API cluster health, status, queue stats, DB/redis query and cache stats etc.
Grafana is used in combination with Prometheus to display the gathered stats and to monitor our physical servers aswell as their virtual applications. We also use Grafana to get notifications about irregularities.
Grafana takes the data from InfluxDB and presents it in a nice flexible format. Bonus points for built-in alerts and playlists (cycles through different dashboards automatically)
- Graph report with many panels and Dashboard.
- Easy to deploy, and view performance of system.
- Intergrating with many datasource: Prometheus, CloudWatch
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.