This seems super useful to zoom in one some performance characteristics of a single server to debug some issues!
For historical "monitoring", alerts, I still need my NewRelic / ELK kind of tools.
With netdata, there is no need to centralize anything for performance monitoring. You view everything directly from their source. Still, with netdata you can build dashboards with charts from any number of servers. And these charts will be connected to each other much like the ones that come from the same server.
So seems like this is on purpose. And if I understand this correctly, I can just build custom HTML dashboard to connect to multiple machines?
Case in point: https://github.com/Shopify/dashing
Here's the presumed knowledge:
* Ruby
* Sinatra
* CofeeScript
* JavaScript
* HTML
* CSS
* SCSS
* Rufus
* Sprockets
Nine different languages and libraries! Jesus H. Christ!It's plain to see why outfits like Splunk can get away with charging as much as they do - visualizing metrics in that app is as simple as installing a deb package, logging in, and pointing it at your data source.
Setting up Dashing by hand is comparatively ...difficult.
There's a much more approachable all-JS Riemann clone called Godot that I've successfully used on multiple projects, but it still requires some work to make the frontend look good.
Notable features that I would need all relate to multi-server usage:
- central config across hosts
- alerting when values go over or under thresholds
- a mode for automatically selecting and viewing the machines which are working hardest, or not working
- a mode for viewing of a few stats across all machines
- a mode for slide-show viewing of a few stats across all machines