2c60f324ee
* add metadata for learn * first batch of adding metadata to md files * second batch of adding metadata to md files * third batch of adding metadata to md files * test one sidebar_label * add missing sidebar_labels * add missing sidebar_labels to files left behind * test, ansible doc is stubborn * fix * fix * fix * don't use questionmarks in the sidebar label * don't use exclamation marks and symbols in the sidebar label * fix style guide * fixes * fixes |
||
|---|---|---|
| .. | ||
| 1s-granularity.md | ||
| immediate-results.md | ||
| meaningful-presentation.md | ||
| README.md | ||
| unlimited-metrics.md | ||
Why Netdata
Any performance monitoring solution that does not go down to per second collection and visualization of the data, is useless. It will make you happy to have it, but it will not help you more than that.
Netdata is built around 4 principles:
-
Per second data collection for all metrics.
It is impossible to monitor a 2 second SLA, with 10 second metrics.
-
Collect and visualize all the metrics from all possible sources.
To troubleshoot slowdowns, we need all the available metrics. The console should not provide more metrics.
-
Meaningful presentation, optimized for visual anomaly detection.
Metrics are a lot more than name-value pairs over time. The monitoring tool should know all the metrics. Users should not!
-
Immediate results, just install and use.
Most of our infrastructure is standardized. There is no point to configure everything metric by metric.
Unlike other monitoring solutions that focus on metrics visualization, Netdata's helps us troubleshoot slowdowns without touching the console.
So, everything is a bit different.