alamrs -> alarms (#7637)
Timo committed
Dec 27, 2019 at 18:35 UTC
0823455d9735837652e2ed950e7e8390d3e7dbf2
1 file changed
+1
-1
docs/step-by-step/step-01.md
+1
-1
@@ -76,7 +76,7 @@ Our first principle is per-second data collection for all metrics.
76
That matters because you can't monitor a 2-second service-level agreement (SLA) with 10-second metrics. You can't detect
77
quick anomalies if your metrics don't show them.
78
79
-How do we solve this? By decentralizing monitoring. Each node is responsible for collecting metrics, triggering alamrs,
79
+How do we solve this? By decentralizing monitoring. Each node is responsible for collecting metrics, triggering alarms,
80
and building dashboards locally, and we work hard to ensure it does each step (and others) with remarkable efficiency.
81
For example, Netdata can [collect 100,000 metrics](https://github.com/netdata/netdata/issues/1323) every second while
82
using only 9% of a single server-grade CPU core!