diff options
| author | Timo <timotej@netdata.cloud> | 2019-12-27 18:35:12 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-27 18:35:12 +0100 |
| commit | 0823455d9735837652e2ed950e7e8390d3e7dbf2 (patch) | |
| tree | ab478ce63e5484e9801b633096525bb72c75ea39 /docs | |
| parent | 7d00d16e984645a368c67d0177f4f181d9722b78 (diff) | |
alamrs -> alarms (#7637)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/step-by-step/step-01.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/step-by-step/step-01.md b/docs/step-by-step/step-01.md index fedf3ea0e2..fb959c07e8 100644 --- a/docs/step-by-step/step-01.md +++ b/docs/step-by-step/step-01.md @@ -76,7 +76,7 @@ Our first principle is per-second data collection for all metrics. That matters because you can't monitor a 2-second service-level agreement (SLA) with 10-second metrics. You can't detect quick anomalies if your metrics don't show them. -How do we solve this? By decentralizing monitoring. Each node is responsible for collecting metrics, triggering alamrs, +How do we solve this? By decentralizing monitoring. Each node is responsible for collecting metrics, triggering alarms, and building dashboards locally, and we work hard to ensure it does each step (and others) with remarkable efficiency. For example, Netdata can [collect 100,000 metrics](https://github.com/netdata/netdata/issues/1323) every second while using only 9% of a single server-grade CPU core! |