Spelling md (#10508)
* spelling: activity Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: adding Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: addresses Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: administrators Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: alarm Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: alignment Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: analyzing Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: apcupsd Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: apply Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: around Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: associated Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: automatically Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: availability Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: background Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: bandwidth Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: berkeley Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: between Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: celsius Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: centos Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: certificate Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: cockroach Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: collectors Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: concatenation Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: configuration Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: configured Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: continuous Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: correctly Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: corresponding Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: cyberpower Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: daemon Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: dashboard Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: database Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: deactivating Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: dependencies Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: deployment Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: determine Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: downloading Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: either Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: electric Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: entity Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: entrant Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: enumerating Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: environment Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: equivalent Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: etsy Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: everything Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: examining Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: expectations Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: explicit Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: explicitly Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: finally Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: flexible Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: further Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: hddtemp Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: humidity Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: identify Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: importance Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: incoming Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: individual Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: initiate Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: installation Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: integration Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: integrity Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: involuntary Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: issues Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: kernel Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: language Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: libwebsockets Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: lighttpd Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: maintained Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: meaningful Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: memory Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: metrics Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: miscellaneous Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: monitoring Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: monitors Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: monolithic Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: multi Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: multiplier Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: navigation Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: noisy Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: number Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: observing Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: omitted Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: orchestrator Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: overall Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: overridden Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: package Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: packages Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: packet Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: pages Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: parameter Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: parsable Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: percentage Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: perfect Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: phpfpm Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: platform Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: preferred Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: prioritize Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: probabilities Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: process Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: processes Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: program Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: qos Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: quick Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: raspberry Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: received Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: recvfile Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: red hat Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: relatively Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: reliability Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: repository Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: requested Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: requests Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: retrieved Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: scenarios Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: see all Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: supported Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: supports Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: temporary Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: tsdb Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: tutorial Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: updates Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: utilization Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: value Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: variables Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: visualize Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: voluntary Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: your Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Josh Soref committed
Jan 18, 2021 at 07:43 UTC
f4193c3b5c013df00b6d05805bf1cc99bebe02bf
80 files changed
+156
-156
.travis/README.md
+2
-2
@@ -66,7 +66,7 @@ Briefly our activities include:
66
67
## Artifacts validation
68
At this point we know our software is building, we need to go through the a set of checks, to guarantee
69
-that our product meets certain epxectations. At the current stage, we are focusing on basic capabilities
69
+that our product meets certain expectations. At the current stage, we are focusing on basic capabilities
70
like installing in different distributions, running the full lifecycle of install-run-update-install and so on.
71
We are still working on enriching this with more and more use cases, to get us closer to achieving full stability of our software.
72
Briefly we currently evaluate the following activities:
@@ -121,7 +121,7 @@ The following distributions are supported
121
- Bionic
122
- artful
123
124
-- Enterprise Linux versions (Covers Redhat, CentOS, and Amazon Linux with version 6)
124
+- Enterprise Linux versions (Covers Red Hat, CentOS, and Amazon Linux with version 6)
125
- Version 8 (TBD)
126
- Version 7
127
- Version 6
BUILD.md
+3
-3
@@ -57,7 +57,7 @@ cmake -DENABLE_DBENGINE
57
58
### Dependency detection
59
60
-We have a mixture of soft- and hard-depedencies on libraries. For most of these we expect
60
+We have a mixture of soft- and hard-dependencies on libraries. For most of these we expect
61
`pkg-config` information, for some we manually probe for libraries and include files. We
62
should treat all of the external dependencies consistently:
63
@@ -346,10 +346,10 @@ We should follow these steps:
346
9. Deprecate / remove the autotools build-system completely (so that we can support a single
347
build-system).
348
349
-Some smaller miscellaeneous suggestions:
349
+Some smaller miscellaneous suggestions:
350
351
1. Remove the `_Generic` / `strerror_r` config to make the system simpler (use the technique
352
- on the blog post to make the standard version re-enterant so that it is thread-safe).
352
+ on the blog post to make the standard version re-entrant so that it is thread-safe).
353
2. Pull in jemalloc by source into the repo if it is our preferred malloc implementation.
354
355
# Background
CHANGELOG.md
+4
-4
@@ -33,9 +33,9 @@
33
- Exclude autofs by default in diskspace plugin [\#10441](https://github.com/netdata/netdata/pull/10441) ([nabijaczleweli](https://github.com/nabijaczleweli))
34
- New eBPF kernel [\#10434](https://github.com/netdata/netdata/pull/10434) ([thiagoftsm](https://github.com/thiagoftsm))
35
- Update and improve the Netdata style guide [\#10433](https://github.com/netdata/netdata/pull/10433) ([joelhans](https://github.com/joelhans))
36
-- Change HDDtemp to report None instead of 0 [\#10429](https://github.com/netdata/netdata/pull/10429) ([slavox](https://github.com/slavox))
36
+- Change hddtemp to report None instead of 0 [\#10429](https://github.com/netdata/netdata/pull/10429) ([slavox](https://github.com/slavox))
37
- Use bash shell as user netdata for debug [\#10425](https://github.com/netdata/netdata/pull/10425) ([Steve8291](https://github.com/Steve8291))
38
-- Qick and dirty fix for \#10420 [\#10424](https://github.com/netdata/netdata/pull/10424) ([skibbipl](https://github.com/skibbipl))
38
+- Quick and dirty fix for \#10420 [\#10424](https://github.com/netdata/netdata/pull/10424) ([skibbipl](https://github.com/skibbipl))
39
- Add instructions on enabling explicitly disabled collectors [\#10418](https://github.com/netdata/netdata/pull/10418) ([joelhans](https://github.com/joelhans))
40
- Change links at bottom of all install docs [\#10416](https://github.com/netdata/netdata/pull/10416) ([joelhans](https://github.com/joelhans))
41
- Improve configuration docs with common changes and start/stop/restart directions [\#10415](https://github.com/netdata/netdata/pull/10415) ([joelhans](https://github.com/joelhans))
@@ -139,7 +139,7 @@
139
- add `nvidia\_smi` collector data to the dashboard\_info.js [\#10230](https://github.com/netdata/netdata/pull/10230) ([ilyam8](https://github.com/ilyam8))
140
- health: convert `elasticsearch\_last\_collected` alarm to template [\#10226](https://github.com/netdata/netdata/pull/10226) ([ilyam8](https://github.com/ilyam8))
141
- streaming: fix a typo in the README.md [\#10225](https://github.com/netdata/netdata/pull/10225) ([ilyam8](https://github.com/ilyam8))
142
-- collectors/xenstat.plugin: recieved =\> received [\#10224](https://github.com/netdata/netdata/pull/10224) ([ilyam8](https://github.com/ilyam8))
142
+- collectors/xenstat.plugin: received =\> received [\#10224](https://github.com/netdata/netdata/pull/10224) ([ilyam8](https://github.com/ilyam8))
143
- dashboard\_info.js: fix a typo \(vernemq\) [\#10223](https://github.com/netdata/netdata/pull/10223) ([ilyam8](https://github.com/ilyam8))
144
- Fix chart filtering [\#10218](https://github.com/netdata/netdata/pull/10218) ([vlvkobal](https://github.com/vlvkobal))
145
- Don't stop Prometheus remote write collector when data is not available for dimension formatting [\#10217](https://github.com/netdata/netdata/pull/10217) ([vlvkobal](https://github.com/vlvkobal))
@@ -226,7 +226,7 @@
226
- Fix memory mode none not dropping stale dimension data [\#9917](https://github.com/netdata/netdata/pull/9917) ([mfundul](https://github.com/mfundul))
227
- Fix memory mode none not marking dimensions as obsolete. [\#9912](https://github.com/netdata/netdata/pull/9912) ([mfundul](https://github.com/mfundul))
228
- Fix buffer overflow in rrdr structure [\#9903](https://github.com/netdata/netdata/pull/9903) ([mfundul](https://github.com/mfundul))
229
-- Fix missing newline concatentation slash causing rpm build to fail [\#9900](https://github.com/netdata/netdata/pull/9900) ([prologic](https://github.com/prologic))
229
+- Fix missing newline concatenation slash causing rpm build to fail [\#9900](https://github.com/netdata/netdata/pull/9900) ([prologic](https://github.com/prologic))
230
- installer: update go.d.plugin version to v0.22.0 [\#9898](https://github.com/netdata/netdata/pull/9898) ([ilyam8](https://github.com/ilyam8))
231
- Add v2 HTTP message with compression to ACLK [\#9895](https://github.com/netdata/netdata/pull/9895) ([underhood](https://github.com/underhood))
232
- Fix lock order reversal \(Coverity defect CID 361629\) [\#9888](https://github.com/netdata/netdata/pull/9888) ([mfundul](https://github.com/mfundul))
HISTORICAL_CHANGELOG.md
+7
-7
@@ -164,7 +164,7 @@ netdata (1.6.0) - 2017-03-20
164
165
1. number of sensors by state
166
2. number of events in SEL
167
- 3. Temperatures CELCIUS
167
+ 3. Temperatures CELSIUS
168
4. Temperatures FAHRENHEIT
169
5. Voltages
170
6. Currents
@@ -239,7 +239,7 @@ netdata (1.5.0) - 2017-01-22
239
Vladimir Kobal (@vlvkobal) has done a magnificent work
240
porting netdata to FreeBSD and MacOS.
241
242
- Everyhing works: cpu, memory, disks performance, disks space,
242
+ Everything works: cpu, memory, disks performance, disks space,
243
network interfaces, interrupts, IPv4 metrics, IPv6 metrics
244
processes, context switches, softnet, IPC queues,
245
IPC semaphores, IPC shared memory, uptime, etc. Wow!
@@ -382,7 +382,7 @@ netdata (1.4.0) - 2016-10-04
382
cgroups,
383
hddtemp,
384
sensors,
385
- phpfm,
385
+ phpfpm,
386
tc (QoS)
387
388
In detail:
@@ -483,7 +483,7 @@ netdata (1.3.0) - 2016-08-28
483
- hddtemp
484
- mysql
485
- nginx
486
- - phpfm
486
+ - phpfpm
487
- postfix
488
- sensors
489
- squid
@@ -518,7 +518,7 @@ netdata (1.3.0) - 2016-08-28
518
- apps.plugin improvements:
519
520
- can now run with command line argument 'without-files'
521
- to prevent it from enumating all the open files/sockets/pipes
521
+ to prevent it from enumerating all the open files/sockets/pipes
522
of all running processes.
523
524
- apps.plugin now scales the collected values to match the
@@ -575,7 +575,7 @@ netdata (1.2.0) - 2016-05-16
575
20% better performance for the core of netdata.
576
577
- More efficient threads locking in key components
578
- contributed to the overal efficiency.
578
+ contributed to the overall efficiency.
579
580
- netdata now has a CENTRAL REGISTRY !
581
@@ -625,7 +625,7 @@ netdata (1.1.0) - 2016-04-20
625
- Data collection: apps.plugin: grouping of processes now support patterns
626
- Data collection: apps.plugin: now it is faster, after the new features added
627
- Data collection: better auto-detection of partitions for disk monitoring
628
-- Data collection: better fireqos intergation for QoS monitoring
628
+- Data collection: better fireqos integration for QoS monitoring
629
- Data collection: squid monitoring now uses squidclient
630
- Data collection: SNMP monitoring now supports 64bit counters
631
- API: fixed issues in CSV output generation
backends/TIMESCALE.md
+1
-1
@@ -27,7 +27,7 @@ TimescaleDB.
27
Finally, another member of Netdata's community has built a project that quickly launches Netdata, TimescaleDB, and
28
Grafana in easy-to-manage Docker containers. Rune Juhl Jacobsen's
29
[project](https://github.com/runejuhl/grafana-timescaledb) uses a `Makefile` to create everything, which makes it
30
-perferct for testing and experimentation.
30
+perfect for testing and experimentation.
31
32
## Netdata↔TimescaleDB in action
33
backends/opentsdb/README.md
+1
-1
@@ -21,7 +21,7 @@ change the `destination = localhost:4242` line accordingly.
21
22
As of [v1.16.0](https://github.com/netdata/netdata/releases/tag/v1.16.0), Netdata can send metrics to OpenTSDB using
23
TLS/SSL. Unfortunately, OpenTDSB does not support encrypted connections, so you will have to configure a reverse proxy
24
-to enable HTTPS communication between Netdata and OpenTSBD. You can set up a reverse proxy with
24
+to enable HTTPS communication between Netdata and OpenTSDB. You can set up a reverse proxy with
25
[Nginx](/docs/Running-behind-nginx.md).
26
27
After your proxy is configured, make the following changes to `netdata.conf`:
build_external/README.md
+1
-1
@@ -12,7 +12,7 @@ decoupled. This allows:
12
- Cross-compilation (e.g. linux development from macOS)
13
- Cross-distro (e.g. using CentOS user-land while developing on Debian)
14
- Multi-host scenarios (e.g. parent-child configurations)
15
-- Bleeding-edge sceneraios (e.g. using the ACLK (**currently for internal-use only**))
15
+- Bleeding-edge scenarios (e.g. using the ACLK (**currently for internal-use only**))
16
17
The advantage of these scenarios is that they allow **reproducible** builds and testing
18
for developers. This is the first iteration of the build-system to allow the team to use
claim/README.md
+1
-1
@@ -304,7 +304,7 @@ This node no longer has access to the credentials it was claimed with and cannot
304
You will still be able to see this node in your War Rooms in an **unreachable** state.
305
306
If you want to reclaim this node into a different Space, you need to create a new identity by adding `-id=$(uuidgen)` to
307
-the claiming script parameters. Make sure that you have the `uuidgen-runtime` packagen installed, as it is used to run the command `uuidgen`. For example, using the default claiming script:
307
+the claiming script parameters. Make sure that you have the `uuidgen-runtime` package installed, as it is used to run the command `uuidgen`. For example, using the default claiming script:
308
309
```bash
310
sudo netdata-claim.sh -token=TOKEN -rooms=ROOM1,ROOM2 -url=https://app.netdata.cloud -id=$(uuidgen)
collectors/COLLECTORS.md
+5
-5
@@ -222,7 +222,7 @@ configure any of these collectors according to your setup and infrastructure.
222
- [ISC DHCP (Go)](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/isc_dhcpd): Reads a
223
`dhcpd.leases` file and collects metrics on total active leases, pool active leases, and pool utilization.
224
- [ISC DHCP (Python)](/collectors/python.d.plugin/isc_dhcpd/README.md): Reads `dhcpd.leases` file and reports DHCP
225
- pools utiliation and leases statistics (total number, leases per pool).
225
+ pools utilization and leases statistics (total number, leases per pool).
226
- [OpenLDAP](/collectors/python.d.plugin/openldap/README.md): Provides statistics information from the OpenLDAP
227
(`slapd`) server.
228
- [NSD](/collectors/python.d.plugin/nsd/README.md): Monitor nameserver performance metrics using the `nsd-control`
@@ -357,7 +357,7 @@ The Netdata Agent can collect these system- and hardware-level metrics using a v
357
- [BCACHE](/collectors/proc.plugin/README.md): Monitor BCACHE statistics with the the `proc.plugin` collector.
358
- [Block devices](/collectors/proc.plugin/README.md): Gather metrics about the health and performance of block
359
devices using the the `proc.plugin` collector.
360
-- [Btrfs](/collectors/proc.plugin/README.md): Montiors Btrfs filesystems with the the `proc.plugin` collector.
360
+- [Btrfs](/collectors/proc.plugin/README.md): Monitors Btrfs filesystems with the the `proc.plugin` collector.
361
- [Device mapper](/collectors/proc.plugin/README.md): Gather metrics about the Linux device mapper with the proc
362
collector.
363
- [Disk space](/collectors/diskspace.plugin/README.md): Collect disk space usage metrics on Linux mount points.
@@ -445,7 +445,7 @@ The Netdata Agent can collect these system- and hardware-level metrics using a v
445
- [systemd](/collectors/cgroups.plugin/README.md): Monitor the CPU and memory usage of systemd services using the
446
`cgroups.plugin` collector.
447
- [systemd unit states](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/systemdunits): See the
448
- state (active, inactive, activating, deactiviating, failed) of various systemd unit types.
448
+ state (active, inactive, activating, deactivating, failed) of various systemd unit types.
449
- [System processes](/collectors/proc.plugin/README.md): Collect metrics on system load and total processes running
450
using `/proc/loadavg` and the `proc.plugin` collector.
451
- [Uptime](/collectors/proc.plugin/README.md): Monitor the uptime of a system using the `proc.plugin` collector.
@@ -511,10 +511,10 @@ the `go.d.plugin`.
511
512
## Third-party collectors
513
514
-These collectors are developed and maintined by third parties and, unlike the other collectors, are not installed by
514
+These collectors are developed and maintained by third parties and, unlike the other collectors, are not installed by
515
default. To use a third-party collector, visit their GitHub/documentation page and follow their installation procedures.
516
517
-- [CyberPower UPS](https://github.com/HawtDogFlvrWtr/netdata_cyberpwrups_plugin): Polls Cyberpower UPS data using
517
+- [CyberPower UPS](https://github.com/HawtDogFlvrWtr/netdata_cyberpwrups_plugin): Polls CyberPower UPS data using
518
PowerPanel® Personal Linux.
519
- [Logged-in users](https://github.com/veksh/netdata-numsessions): Collect the number of currently logged-on users.
520
- [nim-netdata-plugin](https://github.com/FedericoCeratto/nim-netdata-plugin): A helper to create native Netdata
collectors/README.md
+2
-2
@@ -32,7 +32,7 @@ guide](/collectors/QUICKSTART.md).
32
33
[Monitor Nginx or Apache web server log files with Netdata](/docs/guides/collect-apache-nginx-web-logs.md)
34
35
-[Monitor CockroadchDB metrics with Netdata](/docs/guides/monitor-cockroachdb.md)
35
+[Monitor CockroachDB metrics with Netdata](/docs/guides/monitor-cockroachdb.md)
36
37
[Monitor Unbound DNS servers with Netdata](/docs/guides/collect-unbound-metrics.md)
38
@@ -40,7 +40,7 @@ guide](/collectors/QUICKSTART.md).
40
41
## Related features
42
43
-**[Dashboards](/web/README.md)**: Vizualize your newly-collect metrics in real-time using Netdata's [built-in
43
+**[Dashboards](/web/README.md)**: Visualize your newly-collect metrics in real-time using Netdata's [built-in
44
dashboard](/web/gui/README.md).
45
46
**[Backends](/backends/README.md)**: Extend our built-in [database engine](/database/engine/README.md), which supports
collectors/REFERENCE.md
+2
-2
@@ -46,7 +46,7 @@ However, there are cases that auto-detection fails. Usually, the reason is that
46
allow Netdata to connect. In most of the cases, allowing the user `netdata` from `localhost` to connect and collect
47
metrics, will automatically enable data collection for the application in question (it will require a Netdata restart).
48
49
-View our [collectors quickstart](/collectors/QUICKSTART.md) for explict details on enabling and configuring collector modules.
49
+View our [collectors quickstart](/collectors/QUICKSTART.md) for explicit details on enabling and configuring collector modules.
50
51
## Troubleshoot a collector
52
@@ -112,7 +112,7 @@ This section features a list of Netdata's plugins, with a boolean setting to ena
112
# charts.d = yes
113
```
114
115
-By default, most plugins are enabled, so you don't need to enable them explicity to use their collectors. To enable or
115
+By default, most plugins are enabled, so you don't need to enable them explicitly to use their collectors. To enable or
116
disable any specific plugin, remove the comment (`#`) and change the boolean setting to `yes` or `no`.
117
118
All **external plugins** are managed by [plugins.d](plugins.d/), which provides additional management options.
collectors/apps.plugin/README.md
+1
-1
@@ -59,7 +59,7 @@ Each of these sections provides the same number of charts:
59
- Pipes open (`apps.pipes`)
60
- Swap memory
61
- Swap memory used (`apps.swap`)
62
- - Major page faults (i.e. swap activiy, `apps.major_faults`)
62
+ - Major page faults (i.e. swap activity, `apps.major_faults`)
63
- Network
64
- Sockets open (`apps.sockets`)
65
collectors/cgroups.plugin/README.md
+1
-1
@@ -145,7 +145,7 @@ Support per distribution:
145
|Fedora 25|YES|[here](http://pastebin.com/ax0373wF)||
146
|Debian 8|NO||can be enabled, see below|
147
|AMI|NO|[here](http://pastebin.com/FrxmptjL)|not a systemd system|
148
-|Centos 7.3.1611|NO|[here](http://pastebin.com/SpzgezAg)|can be enabled, see below|
148
+|CentOS 7.3.1611|NO|[here](http://pastebin.com/SpzgezAg)|can be enabled, see below|
149
150
### how to enable cgroup accounting on systemd systems that is by default disabled
151
collectors/ebpf.plugin/README.md
+2
-2
@@ -221,7 +221,7 @@ The following options are available:
221
- `ports`: Define the destination ports for Netdata to monitor.
222
- `hostnames`: The list of hostnames that can be resolved to an IP address.
223
- `ips`: The IP or range of IPs that you want to monitor. You can use IPv4 or IPv6 addresses, use dashes to define a
224
- range of IPs, or use CIDR values. The default behavior is to only collect data for private IP addresess, but this
224
+ range of IPs, or use CIDR values. The default behavior is to only collect data for private IP addresses, but this
225
can be changed with the `ips` setting.
226
227
By default, Netdata displays up to 500 dimensions on network connection charts. If there are more possible dimensions,
@@ -275,7 +275,7 @@ curl -sSL https://raw.githubusercontent.com/netdata/kernel-collector/master/tool
275
276
If this script returns no output, your system is ready to compile and run the eBPF collector.
277
278
-If you see a warning about a missing kerkel configuration (`KPROBES KPROBES_ON_FTRACE HAVE_KPROBES BPF BPF_SYSCALL
278
+If you see a warning about a missing kernel configuration (`KPROBES KPROBES_ON_FTRACE HAVE_KPROBES BPF BPF_SYSCALL
279
BPF_JIT`), you will need to recompile your kernel to support this configuration. The process of recompiling Linux
280
kernels varies based on your distribution and version. Read the documentation for your system's distribution to learn
281
more about the specific workflow for recompiling the kernel, ensuring that you set all the necessary
collectors/freeipmi.plugin/README.md
+1
-1
@@ -25,7 +25,7 @@ The plugin creates (up to) 8 charts, based on the information collected from IPM
25
26
1. number of sensors by state
27
2. number of events in SEL
28
-3. Temperatures CELCIUS
28
+3. Temperatures CELSIUS
29
4. Temperatures FAHRENHEIT
30
5. Voltages
31
6. Currents
collectors/node.d.plugin/stiebeleltron/README.md
+2
-2
@@ -40,7 +40,7 @@ The charts are configurable, however, the provided default configuration collect
40
- Heat circuit 1 room temperature in C (set/actual)
41
- Heat circuit 2 room temperature in C (set/actual)
42
43
-5. **Eletric Reheating**
43
+5. **Electric Reheating**
44
45
- Dual Mode Reheating temperature in C (hot water/heating)
46
@@ -68,7 +68,7 @@ If no configuration is given, the module will be disabled. Each `update_every` i
68
69
Original author: BrainDoctor (github)
70
71
-The module supports any metrics that are parseable with RegEx. There is no API that gives direct access to the values (AFAIK), so the "workaround" is to parse the HTML output of the ISG.
71
+The module supports any metrics that are parsable with RegEx. There is no API that gives direct access to the values (AFAIK), so the "workaround" is to parse the HTML output of the ISG.
72
73
### Testing
74
collectors/perf.plugin/README.md
+1
-1
@@ -64,7 +64,7 @@ enable the perf plugin, edit /etc/netdata/netdata.conf and set:
64
You can use the `command options` parameter to pick what data should be collected and which charts should be
65
displayed. If `all` is used, all general performance monitoring counters are probed and corresponding charts
66
are enabled for the available counters. You can also define a particular set of enabled charts using the
67
-following keywords: `cycles`, `instructions`, `branch`, `cache`, `bus`, `stalled`, `migrations`, `alighnment`,
67
+following keywords: `cycles`, `instructions`, `branch`, `cache`, `bus`, `stalled`, `migrations`, `alignment`,
68
`emulation`, `L1D`, `L1D-prefetch`, `L1I`, `LL`, `DTLB`, `ITLB`, `PBU`.
69
70
## Debugging
collectors/plugins.d/README.md
+1
-1
@@ -79,7 +79,7 @@ Example:
79
```
80
81
The setting `enable running new plugins` sets the default behavior for all external plugins. It can be
82
-overriden for distinct plugins by modifying the appropriate plugin value configuration to either `yes` or `no`.
82
+overridden for distinct plugins by modifying the appropriate plugin value configuration to either `yes` or `no`.
83
84
The setting `check for new plugins every` sets the interval between scans of the directory
85
`/usr/libexec/netdata/plugins.d`. New plugins can be added any time, and Netdata will detect them in a timely manner.
collectors/python.d.plugin/am2320/README.md
+3
-3
@@ -6,7 +6,7 @@ sidebar_label: "AM2320"
6
7
# AM2320 sensor monitoring with netdata
8
9
-Displays a graph of the temperature and humity from a AM2320 sensor.
9
+Displays a graph of the temperature and humidity from a AM2320 sensor.
10
11
## Requirements
12
- Adafruit Circuit Python AM2320 library
@@ -28,10 +28,10 @@ cd /etc/netdata # Replace this path with your Netdata config directory, if dif
28
sudo ./edit-config python.d/am2320.conf
29
```
30
31
-Raspbery Pi Instructions:
31
+Raspberry Pi Instructions:
32
33
Hardware install:
34
-Connect the am2320 to the Raspbery Pi I2C pins
34
+Connect the am2320 to the Raspberry Pi I2C pins
35
36
Raspberry Pi 3B/4 Pins:
37
collectors/python.d.plugin/anomalies/README.md
+7
-7
@@ -134,7 +134,7 @@ local:
134
diffs_n: 1
135
136
# What is the typical proportion of anomalies in your data on average?
137
- # This paramater can control the sensitivity of your models to anomalies.
137
+ # This parameter can control the sensitivity of your models to anomalies.
138
# Some discussion here: https://github.com/yzhao062/pyod/issues/144
139
contamination: 0.001
140
@@ -142,7 +142,7 @@ local:
142
# just the average of all anomaly probabilities at each time step
143
include_average_prob: true
144
145
- # Define any custom models you would like to create anomaly probabilties for, some examples below to show how.
145
+ # Define any custom models you would like to create anomaly probabilities for, some examples below to show how.
146
# For example below example creates two custom models, one to run anomaly detection user and system cpu for our demo servers
147
# and one on the cpu and mem apps metrics for the python.d.plugin.
148
# custom_models:
@@ -161,7 +161,7 @@ local:
161
162
In the `anomalies.conf` file you can also define some "custom models" which you can use to group one or more metrics into a single model much like is done by default for the charts you specify. This is useful if you have a handful of metrics that exist in different charts but perhaps are related to the same underlying thing you would like to perform anomaly detection on, for example a specific app or user.
163
164
-To define a custom model you would include configuation like below in `anomalies.conf`. By default there should already be some commented out examples in there.
164
+To define a custom model you would include configuration like below in `anomalies.conf`. By default there should already be some commented out examples in there.
165
166
`name` is a name you give your custom model, this is what will appear alongside any other specified charts in the `anomalies.probability` and `anomalies.anomaly` charts. `dimensions` is a string of metrics you want to include in your custom model. By default the [netdata-pandas](https://github.com/netdata/netdata-pandas) library used to pull the data from Netdata uses a "chart.a|dim.1" type of naming convention in the pandas columns it returns, hence the `dimensions` string should look like "chart.name|dimension.name,chart.name|dimension.name". The examples below hopefully make this clear.
167
@@ -194,7 +194,7 @@ sudo su -s /bin/bash netdata
194
/usr/libexec/netdata/plugins.d/python.d.plugin anomalies debug trace nolock
195
```
196
197
-## Deepdive turorial
197
+## Deepdive tutorial
198
199
If you would like to go deeper on what exactly the anomalies collector is doing under the hood then check out this [deepdive tutorial](https://github.com/netdata/community/blob/main/netdata-agent-api/netdata-pandas/anomalies_collector_deepdive.ipynb) in our community repo where you can play around with some data from our demo servers (or your own if its accessible to you) and work through the calculations step by step.
200
@@ -206,7 +206,7 @@ If you would like to go deeper on what exactly the anomalies collector is doing
206
- Python 3 is also required for the underlying ML libraries of [numba](https://pypi.org/project/numba/), [scikit-learn](https://pypi.org/project/scikit-learn/), and [PyOD](https://pypi.org/project/pyod/).
207
- It may take a few hours or so (depending on your choice of `train_secs_n`) for the collector to 'settle' into it's typical behaviour in terms of the trained models and probabilities you will see in the normal running of your node.
208
- As this collector does most of the work in Python itself, with [PyOD](https://pyod.readthedocs.io/en/latest/) leveraging [numba](https://numba.pydata.org/) under the hood, you may want to try it out first on a test or development system to get a sense of its performance characteristics on a node similar to where you would like to use it.
209
-- `lags_n`, `smooth_n`, and `diffs_n` together define the preprocessing done to the raw data before models are trained and before each prediction. This essentially creates a [feature vector](https://en.wikipedia.org/wiki/Feature_(machine_learning)#:~:text=In%20pattern%20recognition%20and%20machine,features%20that%20represent%20some%20object.&text=Feature%20vectors%20are%20often%20combined,score%20for%20making%20a%20prediction.) for each chart model (or each custom model). The default settings for these parameters aim to create a rolling matrix of recent smoothed [differenced](https://en.wikipedia.org/wiki/Autoregressive_integrated_moving_average#Differencing) values for each chart. The aim of the model then is to score how unusual this 'matrix' of features is for each chart based on what it has learned as 'normal' from the training data. So as opposed to just looking at the single most recent value of a dimension and considering how strange it is, this approach looks at a recent smoothed window of all dimensions for a chart (or dimensions in a custom model) and asks how unusual the data as a whole looks. This should be more flexibile in capturing a wider range of [anomaly types](https://andrewm4894.com/2020/10/19/different-types-of-time-series-anomalies/) and be somewhat more robust to temporary 'spikes' in the data that tend to always be happening somewhere in your metrics but often are not the most important type of anomaly (this is all covered in a lot more detail in the [deepdive tutorial](https://nbviewer.jupyter.org/github/netdata/community/blob/main/netdata-agent-api/netdata-pandas/anomalies_collector_deepdive.ipynb)).
209
+- `lags_n`, `smooth_n`, and `diffs_n` together define the preprocessing done to the raw data before models are trained and before each prediction. This essentially creates a [feature vector](https://en.wikipedia.org/wiki/Feature_(machine_learning)#:~:text=In%20pattern%20recognition%20and%20machine,features%20that%20represent%20some%20object.&text=Feature%20vectors%20are%20often%20combined,score%20for%20making%20a%20prediction.) for each chart model (or each custom model). The default settings for these parameters aim to create a rolling matrix of recent smoothed [differenced](https://en.wikipedia.org/wiki/Autoregressive_integrated_moving_average#Differencing) values for each chart. The aim of the model then is to score how unusual this 'matrix' of features is for each chart based on what it has learned as 'normal' from the training data. So as opposed to just looking at the single most recent value of a dimension and considering how strange it is, this approach looks at a recent smoothed window of all dimensions for a chart (or dimensions in a custom model) and asks how unusual the data as a whole looks. This should be more flexible in capturing a wider range of [anomaly types](https://andrewm4894.com/2020/10/19/different-types-of-time-series-anomalies/) and be somewhat more robust to temporary 'spikes' in the data that tend to always be happening somewhere in your metrics but often are not the most important type of anomaly (this is all covered in a lot more detail in the [deepdive tutorial](https://nbviewer.jupyter.org/github/netdata/community/blob/main/netdata-agent-api/netdata-pandas/anomalies_collector_deepdive.ipynb)).
210
- You can see how long model training is taking by looking in the logs for the collector `grep 'anomalies' /var/log/netdata/error.log | grep 'training'` and you should see lines like `2020-12-01 22:02:14: python.d INFO: anomalies[local] : training complete in 2.81 seconds (runs_counter=2700, model=pca, train_n_secs=14400, models=26, n_fit_success=26, n_fit_fails=0, after=1606845731, before=1606860131).`.
211
- This also gives counts of the number of models, if any, that failed to fit and so had to default back to the DefaultModel (which is currently [HBOS](https://pyod.readthedocs.io/en/latest/_modules/pyod/models/hbos.html)).
212
- `after` and `before` here refer to the start and end of the training data used to train the models.
@@ -215,8 +215,8 @@ If you would like to go deeper on what exactly the anomalies collector is doing
215
- Typically ~3%-3.5% additional cpu usage from scoring, jumping to ~60% for a couple of seconds during model training.
216
- About ~150mb of ram (`apps.mem`) being continually used by the `python.d.plugin`.
217
- If you activate this collector on a fresh node, it might take a little while to build up enough data to calculate a realistic and useful model.
218
-- Some models like `iforest` can be comparatively expensive (on same n1-standard-2 system above ~2s runtime during predict, ~40s training time, ~50% cpu on both train and predict) so if you would like to use it you might be advised to set a relativley high `update_every` maybe 10, 15 or 30 in `anomalies.conf`.
219
-- Setting a higher `train_every_n` and `update_every` is an easy way to devote less resources on the node to anomaly detection. Specifying less charts and a lower `train_n_secs` will also help reduce resources at the expense of covering less charts and maybe a more noisey model if you set `train_n_secs` to be too small for how your node tends to behave.
218
+- Some models like `iforest` can be comparatively expensive (on same n1-standard-2 system above ~2s runtime during predict, ~40s training time, ~50% cpu on both train and predict) so if you would like to use it you might be advised to set a relatively high `update_every` maybe 10, 15 or 30 in `anomalies.conf`.
219
+- Setting a higher `train_every_n` and `update_every` is an easy way to devote less resources on the node to anomaly detection. Specifying less charts and a lower `train_n_secs` will also help reduce resources at the expense of covering less charts and maybe a more noisy model if you set `train_n_secs` to be too small for how your node tends to behave.
220
221
## Useful links and further reading
222
collectors/python.d.plugin/dovecot/README.md
+2
-2
@@ -38,8 +38,8 @@ Module gives information with following charts:
38
39
5. **Context Switches**
40
41
- - volountary
42
- - involountary
41
+ - voluntary
42
+ - involuntary
43
44
6. **disk** in bytes/s
45
collectors/python.d.plugin/go_expvar/README.md
+1
-1
@@ -69,7 +69,7 @@ Sample output:
69
```json
70
{
71
"cmdline": ["./expvar-demo-binary"],
72
-"memstats": {"Alloc":630856,"TotalAlloc":630856,"Sys":3346432,"Lookups":27, <ommited for brevity>}
72
+"memstats": {"Alloc":630856,"TotalAlloc":630856,"Sys":3346432,"Lookups":27, <omitted for brevity>}
73
}
74
```
75
collectors/python.d.plugin/mongodb/README.md
+1
-1
@@ -80,7 +80,7 @@ Number of charts depends on mongodb version, storage engine and other features (
80
13. **Cache metrics** (WiredTiger):
81
82
- percentage of bytes currently in the cache (amount of space taken by cached data)
83
- - percantage of tracked dirty bytes in the cache (amount of space taken by dirty data)
83
+ - percentage of tracked dirty bytes in the cache (amount of space taken by dirty data)
84
85
14. **Pages evicted from cache** (WiredTiger):
86
collectors/python.d.plugin/mysql/README.md
+3
-3
@@ -67,7 +67,7 @@ This module will produce following charts (if data is available):
67
- immediate
68
- waited
69
70
-6. **Table Select Join Issuess** in joins/s
70
+6. **Table Select Join Issues** in joins/s
71
72
- full join
73
- full range join
@@ -75,7 +75,7 @@ This module will produce following charts (if data is available):
75
- range check
76
- scan
77
78
-7. **Table Sort Issuess** in joins/s
78
+7. **Table Sort Issues** in joins/s
79
80
- merge passes
81
- range
@@ -164,7 +164,7 @@ This module will produce following charts (if data is available):
164
- updated
165
- deleted
166
167
-24. **InnoDB Buffer Pool Pagess** in pages
167
+24. **InnoDB Buffer Pool Pages** in pages
168
169
- data
170
- dirty
collectors/python.d.plugin/postgres/README.md
+1
-1
@@ -22,7 +22,7 @@ Following charts are drawn:
22
23
- active
24
25
-3. **Current Backend Processe Usage** percentage
25
+3. **Current Backend Process Usage** percentage
26
27
- used
28
- available
collectors/python.d.plugin/proxysql/README.md
+2
-2
@@ -31,7 +31,7 @@ It produces:
31
- questions: total number of queries sent from frontends
32
- slow_queries: number of queries that ran for longer than the threshold in milliseconds defined in global variable `mysql-long_query_time`
33
34
-3. **Overall Bandwith (backends)**
34
+3. **Overall Bandwidth (backends)**
35
36
- in
37
- out
@@ -45,7 +45,7 @@ It produces:
45
- `4=OFFLINE_HARD`: when a server is put into OFFLINE_HARD mode, the existing connections are dropped, while new incoming connections aren't accepted either. This is equivalent to deleting the server from a hostgroup, or temporarily taking it out of the hostgroup for maintenance work
46
- `-1`: Unknown status
47
48
-5. **Bandwith (backends)**
48
+5. **Bandwidth (backends)**
49
50
- Backends
51
- in
collectors/python.d.plugin/samba/README.md
+1
-1
@@ -21,7 +21,7 @@ It produces the following charts:
21
1. **Syscall R/Ws** in kilobytes/s
22
23
- sendfile
24
- - recvfle
24
+ - recvfile
25
26
2. **Smb2 R/Ws** in kilobytes/s
27
collectors/python.d.plugin/springboot/README.md
+1
-1
@@ -93,7 +93,7 @@ Please refer [Spring Boot Actuator: Production-ready Features](https://docs.spri
93
- MarkSweep
94
- ...
95
96
-4. **Heap Mmeory Usage** in KB
96
+4. **Heap Memory Usage** in KB
97
98
- used
99
- committed
collectors/statsd.plugin/README.md
+2
-2
@@ -38,7 +38,7 @@ Netdata fully supports the statsd protocol. All statsd client libraries can be u
38
39
`:value` can be omitted and statsd will assume it is `1`. `|c`, `|C` and `|m` can be omitted an statsd will assume it is `|m`. So, the application may send just `name` and statsd will parse it as `name:1|m`.
40
41
- For counters use `|c` (esty/statsd compatible) or `|C` (brubeck compatible), for meters use `|m`.
41
+ For counters use `|c` (etsy/statsd compatible) or `|C` (brubeck compatible), for meters use `|m`.
42
43
Sampling rate is supported (check below).
44
@@ -290,7 +290,7 @@ dimension = [pattern] METRIC NAME TYPE MULTIPLIER DIVIDER OPTIONS
290
291
`pattern` is a keyword. When set, `METRIC` is expected to be a Netdata simple pattern that will be used to match all the statsd metrics to be added to the chart. So, `pattern` automatically matches any number of statsd metrics, all of which will be added as separate chart dimensions.
292
293
-`TYPE`, `MUTLIPLIER`, `DIVIDER` and `OPTIONS` are optional.
293
+`TYPE`, `MULTIPLIER`, `DIVIDER` and `OPTIONS` are optional.
294
295
`TYPE` can be:
296
collectors/tc.plugin/README.md
+1
-1
@@ -172,7 +172,7 @@ And this is what you are going to get:
172
173
## QoS Configuration with tc
174
175
-First, setup the tc rules in rc.local using commands to assign different DSCP markings to different classids. You can see one such example in [github issue #4563](https://github.com/netdata/netdata/issues/4563#issuecomment-455711973).
175
+First, setup the tc rules in rc.local using commands to assign different QoS markings to different classids. You can see one such example in [github issue #4563](https://github.com/netdata/netdata/issues/4563#issuecomment-455711973).
176
177
Then, map the classids to names by creating `/etc/iproute2/tc_cls`. For example:
178
daemon/README.md
+1
-1
@@ -514,7 +514,7 @@ section(s) you need to trace.
514
515
We have made the most to make Netdata crash free. If however, Netdata crashes on your system, it would be very helpful
516
to provide stack traces of the crash. Without them, is will be almost impossible to find the issue (the code base is
517
-quite large to find such an issue by just objerving it).
517
+quite large to find such an issue by just observing it).
518
519
To provide stack traces, **you need to have Netdata compiled with debugging**. There is no need to enable any tracing
520
(`debug flags`).
daemon/config/README.md
+2
-2
@@ -100,7 +100,7 @@ Additionally, there will be the following options:
100
|:-----:|:-----:|:---|
101
| PATH environment variable|`auto-detected`||
102
| PYTHONPATH environment variable||Used to set a custom python path|
103
-| enable running new plugins|`yes`|When set to `yes`, Netdata will enable detected plugins, even if they are not configured explicitly. Setting this to `no` will only enable plugins explicitly configirued in this file with a `yes`|
103
+| enable running new plugins|`yes`|When set to `yes`, Netdata will enable detected plugins, even if they are not configured explicitly. Setting this to `no` will only enable plugins explicitly configured in this file with a `yes`|
104
| check for new plugins every|60|The time in seconds to check for new plugins in the plugins directory. This allows having other applications dynamically creating plugins for Netdata.|
105
| checks|`no`|This is a debugging plugin for the internal latency|
106
@@ -190,7 +190,7 @@ that is information about lines that begin with `dim`, which affect a chart's di
190
You may notice some settings that begin with `dim` beneath the ones defined in the table above. These settings determine
191
which dimensions appear on the given chart and how Netdata calculates them.
192
193
-Each dimension setting has the following structure: `dim [DIMENSION ID] [OPTION] = [VALUE]`. The available options are `name`, `algorithm`, `multipler`, and `divisor`.
193
+Each dimension setting has the following structure: `dim [DIMENSION ID] [OPTION] = [VALUE]`. The available options are `name`, `algorithm`, `multiplier`, and `divisor`.
194
195
| Setting | Function |
196
| :----------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
docs/Running-behind-apache.md
+1
-1
@@ -365,7 +365,7 @@ apache logs accesses and Netdata logs them too. You can prevent Netdata from gen
365
366
## Troubleshooting mod_proxy
367
368
-Make sure the requests reach Netdata, by examing `/var/log/netdata/access.log`.
368
+Make sure the requests reach Netdata, by examining `/var/log/netdata/access.log`.
369
370
1. if the requests do not reach Netdata, your apache does not forward them.
371
2. if the requests reach Netdata but the URLs are wrong, you have not re-written them properly.
docs/collect/container-metrics.md
+1
-1
@@ -65,7 +65,7 @@ collection capabilities.
65
## Collect Kubernetes metrics
66
67
We already have a few complementary tools and collectors for monitoring the many layers of a Kubernetes cluster,
68
-_entirely for free_. These methods work together to help you troubleshoot performance or availablility issues across
68
+_entirely for free_. These methods work together to help you troubleshoot performance or availability issues across
69
your k8s infrastructure.
70
71
- A [Helm chart](https://github.com/netdata/helmchart), which bootstraps a Netdata Agent pod on every node in your
docs/collect/enable-configure.md
+3
-3
@@ -18,10 +18,10 @@ enable or configure a collector to gather all available metrics from your system
18
## Enable a collector or its orchestrator
19
20
You can enable/disable collectors individually, or enable/disable entire orchestrators, using their configuration files.
21
-For example, you can change the behavior of the Go orchestator, or any of its collectors, by editing `go.d.conf`.
21
+For example, you can change the behavior of the Go orchestrator, or any of its collectors, by editing `go.d.conf`.
22
23
Use `edit-config` from your [Netdata config directory](/docs/configure/nodes.md#the-netdata-config-directory) to open
24
-the orchestrator's primary configuration file:
24
+the orchestrator primary configuration file:
25
26
```bash
27
cd /etc/netdata
@@ -29,7 +29,7 @@ sudo ./edit-config go.d.conf
29
```
30
31
Within this file, you can either disable the orchestrator entirely (`enabled: yes`), or find a specific collector and
32
-enable/disable it with `yes` and `no` settings. Uncomment any line you change to ensure the Netdata deamon reads it on
32
+enable/disable it with `yes` and `no` settings. Uncomment any line you change to ensure the Netdata daemon reads it on
33
start.
34
35
After you make your changes, restart the Agent with `service netdata restart`.
docs/collect/how-collectors-work.md
+1
-1
@@ -55,7 +55,7 @@ terms related to collecting metrics.
55
56
- **Modules** are a type of collector.
57
- **Orchestrators** are external plugins that run and manage one or more modules. They run as independent processes.
58
- The Go orchestator is in active development.
58
+ The Go orchestrator is in active development.
59
- [go.d.plugin](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/): An orchestrator for data
60
collection modules written in `go`.
61
- [python.d.plugin](/collectors/python.d.plugin/README.md): An orchestrator for data collection modules written in
docs/export/external-databases.md
+1
-1
@@ -7,7 +7,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/export/exte
7
# Export metrics to external time-series databases
8
9
Netdata allows you to export metrics to external time-series databases with the [exporting
10
-engine](/exporting/README.md). This system uses a number of **connectors** to intiate connections to [more than
10
+engine](/exporting/README.md). This system uses a number of **connectors** to initiate connections to [more than
11
thirty](#supported-databases) supported databases, including InfluxDB, Prometheus, Graphite, ElasticSearch, and much
12
more.
13
docs/guides/collect-apache-nginx-web-logs.md
+1
-1
@@ -10,7 +10,7 @@ performance of their web servers, and Netdata is taking important steps to make
10
11
By parsing web server log files with Netdata, and seeing the volume of redirects, requests, or server errors over time,
12
you can better understand what's happening on your infrastructure. Too many bad requests? Maybe a recent deploy missed a
13
-few small SVG icons. Too many requsests? Time to batten down the hatches—it's a DDoS.
13
+few small SVG icons. Too many requests? Time to batten down the hatches—it's a DDoS.
14
15
Netdata has been capable of monitoring web log files for quite some time, thanks for the [weblog python.d
16
module](/collectors/python.d.plugin/web_log/README.md), but we recently refactored this module in Go, and that effort
docs/guides/longer-metrics-storage.md
+1
-1
@@ -53,7 +53,7 @@ size` and `dbengine multihost disk space`.
53
54
`page cache size` sets the maximum amount of RAM (in MiB) the database engine will use for caching and indexing.
55
`dbengine multihost disk space` sets the maximum disk space (again, in MiB) the database engine will use for storing
56
-compressed metrics. The default settings retain about two day's worth of metris on a system collecting 2,000 metrics
56
+compressed metrics. The default settings retain about two day's worth of metrics on a system collecting 2,000 metrics
57
every second.
58
59
[**See our database engine
docs/guides/monitor/kubernetes-k8s-netdata.md
+2
-2
@@ -13,7 +13,7 @@ troubleshoot issues with your cluster.
13
14
Some k8s providers, like GKE (Google Kubernetes Engine), do deploy clusters bundled with monitoring capabilities, such
15
as Google Stackdriver Monitoring. However, these pre-configured solutions might not offer the depth of metrics,
16
-customization, or integration with your perferred alerting methods.
16
+customization, or integration with your preferred alerting methods.
17
18
Without this visibility, it's like you built an entire house and _then_ smashed your way through the finished walls to
19
add windows.
@@ -23,7 +23,7 @@ you actively troubleshoot anomalies or outages. Better yet, this toolkit include
23
let you monitor the many layers of a Kubernetes cluster entirely for free.
24
25
We already have a few complementary tools and collectors for monitoring the many layers of a Kubernetes cluster,
26
-_entirely for free_. These methods work together to help you troubleshoot performance or availablility issues across
26
+_entirely for free_. These methods work together to help you troubleshoot performance or availability issues across
27
your k8s infrastructure.
28
29
- A [Helm chart](https://github.com/netdata/helmchart), which bootstraps a Netdata Agent pod on every node in your
docs/guides/monitor/pi-hole-raspberry-pi.md
+2
-2
@@ -31,7 +31,7 @@ directly using a keyboard, mouse, and monitor.
31
Netdata helps you monitor and troubleshoot all kinds of devices and the applications they run, including IoT devices
32
like the Raspberry Pi and applications like Pi-hole.
33
34
-After a two-minute installation and with zero configuration, you'll be able to seeall of Pi-hole's metrics, including
34
+After a two-minute installation and with zero configuration, you'll be able to see all of Pi-hole's metrics, including
35
the volume of queries, connected clients, DNS queries per type, top clients, top blocked domains, and more.
36
37
With Netdata installed, you can also monitor system metrics and any other applications you might be running. By default,
@@ -107,7 +107,7 @@ walkthrough of all its features. For a more expedited tour, see the [get started
107
You need to manually enable Netdata's built-in [temperature sensor
108
collector](https://learn.netdata.cloud/docs/agent/collectors/charts.d.plugin/sensors) to start collecting metrics.
109
110
-> Netdata uses a few plugins to manage its [collectors](/collectors/REFERENCE.md), each using a different lanaguge: Go,
110
+> Netdata uses a few plugins to manage its [collectors](/collectors/REFERENCE.md), each using a different language: Go,
111
> Python, Node.js, and Bash. While our Go collectors are undergoing the most active development, we still support the
112
> other languages. In this case, you need to enable a temperature sensor collector that's written in Bash.
113
docs/guides/monitor/process.md
+5
-5
@@ -15,7 +15,7 @@ and performance of your infrastructure.
15
One of these layers is the _process_. Every time a Linux system runs a program, it creates an independent process that
16
executes the program's instructions in parallel with anything else happening on the system. Linux systems track the
17
state and resource utilization of processes using the [`/proc` filesystem](https://en.wikipedia.org/wiki/Procfs), and
18
-Netdata is designed to hook into those metrics to create meaningul visualizations out of the box.
18
+Netdata is designed to hook into those metrics to create meaningful visualizations out of the box.
19
20
While there are a lot of existing command-line tools for tracking processes on Linux systems, such as `ps` or `top`,
21
only Netdata provides dozens of real-time charts, at both per-second and event frequency, without you having to write
@@ -86,7 +86,7 @@ Linux systems:
86
- Pipes open (`apps.pipes`)
87
- Swap memory
88
- Swap memory used (`apps.swap`)
89
- - Major page faults (i.e. swap activiy, `apps.major_faults`)
89
+ - Major page faults (i.e. swap activity, `apps.major_faults`)
90
- Network
91
- Sockets open (`apps.sockets`)
92
- eBPF file
@@ -132,7 +132,7 @@ sudo ./edit-config apps_groups.conf
132
133
Inside the file are lists of process names, oftentimes using wildcards (`*`), that the Netdata Agent looks for and
134
groups together. For example, the Netdata Agent looks for processes starting with `mysqld`, `mariad`, `postgres`, and
135
-others, and groups them into `sql`. That makes sense, since all these procesess are for SQL databases.
135
+others, and groups them into `sql`. That makes sense, since all these processes are for SQL databases.
136
137
```conf
138
sql: mysqld* mariad* postgres* postmaster* oracle_* ora_* sqlservr
@@ -247,7 +247,7 @@ metrics](https://user-images.githubusercontent.com/1153921/101411810-d08fb800-38
247
248
### Using Netdata's eBPF collector (`ebpf.plugin`)
249
250
-Netdata's eBPF collector puts its charts in two places. Of most imporance to process monitoring are the **ebpf file**,
250
+Netdata's eBPF collector puts its charts in two places. Of most importance to process monitoring are the **ebpf file**,
251
**ebpf syscall**, **ebpf process**, and **ebpf net** sub-sections under **Applications**, shown in the above screenshot.
252
253
For example, running the above workload shows the entire "story" how MySQL interacts with the Linux kernel to open
@@ -274,7 +274,7 @@ piece of data needed to discover the root cause of an incident. See our [collect
274
setup](/docs/collect/enable-configure.md) doc for details.
275
276
[Create new dashboards](/docs/visualize/create-dashboards.md) in Netdata Cloud using charts from `apps.plugin`,
277
-`ebpf.plugin`, and application-specific collectors to build targeted dashboards for monitoring key procesess across your
277
+`ebpf.plugin`, and application-specific collectors to build targeted dashboards for monitoring key processes across your
278
infrastructure.
279
280
Try running [Metric Correlations](https://learn.netdata.cloud/docs/cloud/insights/metric-correlations) on a node that's
docs/guides/step-by-step/step-05.md
+1
-1
@@ -11,7 +11,7 @@ To accurately monitor the health of your systems and applications, you need to k
11
strange going on. Netdata's alarm and notification systems are essential to keeping you informed.
12
13
Netdata comes with hundreds of pre-configured alarms that don't require configuration. They were designed by our
14
-community of system adminstrators to cover the most important parts of production systems, so, in many cases, you won't
14
+community of system administrators to cover the most important parts of production systems, so, in many cases, you won't
15
need to edit them.
16
17
Luckily, Netdata's alarm and notification system are incredibly adaptable to your infrastructure's unique needs.
docs/guides/step-by-step/step-06.md
+1
-1
@@ -34,7 +34,7 @@ underlying architecture.
34
35
By default, Netdata collects a lot of metrics every second using any number of discrete collector. Collectors, in turn,
36
are organized and manged by plugins. **Internal** plugins collect system metrics, **external** plugins collect
37
-non-system metrics, and **orchestrator** plugins group individal collectors together based on the programming language
37
+non-system metrics, and **orchestrator** plugins group individual collectors together based on the programming language
38
they were built in.
39
40
These modules are primarily written in [Go](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/) (`go.d`) and
docs/guides/step-by-step/step-08.md
+1
-1
@@ -76,7 +76,7 @@ following:
76
</html>
77
```
78
79
-Try visiting `http://HOST:19999/custom-dashbord.html` in your browser.
79
+Try visiting `http://HOST:19999/custom-dashboard.html` in your browser.
80
81
If you get a blank page with this text: `Access to file is not permitted: /usr/share/netdata/web/custom-dashboard.html`.
82
You can fix this error by changing the dashboard file's permissions to make it owned by the `netdata` user.
docs/guides/step-by-step/step-09.md
+1
-1
@@ -143,7 +143,7 @@ Add the following section to the file:
143
```
144
145
[Restart](/docs/getting-started.md#start-stop-and-restart-netdata) Netdata to enable the MongoDB exporting connector.
146
-Click on the **Netdata Montioring** menu and check out the **exporting my mongo instance** sub-menu. You should start
146
+Click on the **Netdata Monitoring** menu and check out the **exporting my mongo instance** sub-menu. You should start
147
seeing these charts fill up with data about the exporting process!
148
149
docs/guides/step-by-step/step-10.md
+1
-1
@@ -65,7 +65,7 @@ Check out [Nginx's installation
65
instructions](https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/) for details on
66
other Linux distributions.
67
68
-Certbot is a tool to help you create and renew certiciate+key pairs for your domain. Visit their
68
+Certbot is a tool to help you create and renew certificate+key pairs for your domain. Visit their
69
[instructions](https://certbot.eff.org/instructions) to get a detailed installation process for your operating system.
70
71
### Fully qualified domain name
docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+2
-2
@@ -120,7 +120,7 @@ calls to open/close files, call functions like `do_fork`, IO activity on the VFS
120
See the [eBPF collector documentation](/collectors/ebpf.plugin/README.md#integration-with-appsplugin) for the full list
121
of per-application charts.
122
123
-Let's show some examples of how you can first identify normal eBPF patterns, then use that knowledge to idenfity
123
+Let's show some examples of how you can first identify normal eBPF patterns, then use that knowledge to identify
124
anomalies in a few simulated scenarios.
125
126
For example, the following screenshot shows the number of open files, failures to open files, and closed files on a
@@ -252,7 +252,7 @@ Debugging and troubleshooting an application takes a special combination of prac
252
Netdata's eBPF metrics to back you up, you can rest assured that you see every minute detail of how your application
253
interacts with the Linux kernel.
254
255
-If you're still trying to wrap your head aroud what we offer, be sure to read up on our accompanying documentation and
255
+If you're still trying to wrap your head around what we offer, be sure to read up on our accompanying documentation and
256
other resources on eBPF monitoring with Netdata:
257
258
- [eBPF collector](/collectors/ebpf.plugin/README.md)
docs/netdata-security.md
+2
-2
@@ -131,7 +131,7 @@ to IP addresses within the `160.1.x.x` range and that reverse DNS is setup for t
131
132
#### Use an authenticating web server in proxy mode
133
134
-Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers). Instructions are provided on how to set the proxy configuration to have Netdata run behind [nginx](Running-behind-nginx.md), [Apache](Running-behind-apache.md), [lighthttpd](Running-behind-lighttpd.md) and [Caddy](Running-behind-caddy.md).
134
+Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers). Instructions are provided on how to set the proxy configuration to have Netdata run behind [nginx](Running-behind-nginx.md), [Apache](Running-behind-apache.md), [lighttpd](Running-behind-lighttpd.md) and [Caddy](Running-behind-caddy.md).
135
136
To use this method, you should firewall protect all your Netdata servers, so that only the web server IP will allowed to directly access Netdata. To do this, run this on each of your servers (or use your firewall manager):
137
@@ -212,7 +212,7 @@ If sending this information to the central Netdata registry violates your securi
212
Starting with v1.12, Netdata collects anonymous usage information by default and sends it to Google Analytics. Read
213
about the information collected, and learn how to-opt, on our [anonymous statistics](anonymous-statistics.md) page.
214
215
-The usage statistics are _vital_ for us, as we use them to discover bugs and priortize new features. We thank you for
215
+The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
216
_actively_ contributing to Netdata's future.
217
218
## Netdata directories
exporting/README.md
+3
-3
@@ -92,7 +92,7 @@ X seconds (though, it can send them per second if you need it to).
92
93
## Configuration
94
95
-Here are the configruation blocks for every supported connector. Your current `exporting.conf` file may look a little
95
+Here are the configuration blocks for every supported connector. Your current `exporting.conf` file may look a little
96
different.
97
98
You can configure each connector individually using the available [options](#options). The
@@ -234,7 +234,7 @@ Configure individual connectors and override any global settings with the follow
234
235
- `prefix = Netdata`, is the prefix to add to all metrics.
236
237
-- `update every = 10`, is the number of seconds between sending data to the external datanase. Netdata will add some
237
+- `update every = 10`, is the number of seconds between sending data to the external database. Netdata will add some
238
randomness to this number, to prevent stressing the external server when many Netdata servers send data to the same
239
database. This randomness does not affect the quality of the data, only the time they are sent.
240
@@ -266,7 +266,7 @@ Configure individual connectors and override any global settings with the follow
266
- `send configured labels = yes | no` controls if labels defined in the `[host labels]` section in `netdata.conf`
267
should be sent to the external database
268
269
-- `send automatic labels = yes | no` controls if automatially created labels, like `_os_name` or `_architecture`
269
+- `send automatic labels = yes | no` controls if automatically created labels, like `_os_name` or `_architecture`
270
should be sent to the external database
271
272
> Starting from Netdata v1.20 the host tags (defined in the `[backend]` section of `netdata.conf`) are parsed in
exporting/TIMESCALE.md
+1
-1
@@ -39,7 +39,7 @@ TimescaleDB.
39
Finally, another member of Netdata's community has built a project that quickly launches Netdata, TimescaleDB, and
40
Grafana in easy-to-manage Docker containers. Rune Juhl Jacobsen's
41
[project](https://github.com/runejuhl/grafana-timescaledb) uses a `Makefile` to create everything, which makes it
42
-perferct for testing and experimentation.
42
+perfect for testing and experimentation.
43
44
## Netdata↔TimescaleDB in action
45
health/REFERENCE.md
+3
-3
@@ -21,7 +21,7 @@ You can configure the Agent's health watchdog service by editing files in two lo
21
altogether, run health checks more or less often, and more. See [daemon
22
configuration](/daemon/config/README.md#health-section-options) for a table of all the available settings, their
23
default values, and what they control.
24
-- The individual `.conf` files in `health.d/`. These health entitiy files are organized by the type of metric they are
24
+- The individual `.conf` files in `health.d/`. These health entity files are organized by the type of metric they are
25
performing calculations on or their associated collector. You should edit these files using the `edit-config`
26
script. For example: `sudo ./edit-config health.d/cpu.conf`.
27
@@ -241,7 +241,7 @@ A `calc` is designed to apply some calculation to the values or variables availa
241
calculation will be made available at the `$this` variable, overwriting the value from your `lookup`, to use in warning
242
and critical expressions.
243
244
-When paired with `lookup`, `calc` will perform the calculation just after `lookup` has retreived a value from Netdata's
244
+When paired with `lookup`, `calc` will perform the calculation just after `lookup` has retrieved a value from Netdata's
245
database.
246
247
You can use `calc` without `lookup` if you are using [other available variables](#variables).
@@ -340,7 +340,7 @@ delay: [[[up U] [down D] multiplier M] max X]
340
will delay the notification by 1 minute. This is used to prevent notifications for flapping
341
alarms. The default `D` is zero.
342
343
-- `mutliplier M` multiplies `U` and `D` when an alarm changes state, while a notification is
343
+- `multiplier M` multiplies `U` and `D` when an alarm changes state, while a notification is
344
delayed. The default multiplier is `1.0`.
345
346
- `max X` defines the maximum absolute notification delay an alarm may get. The default `X`
health/notifications/alerta/README.md
+2
-2
@@ -29,7 +29,7 @@ The easiest way to install Alerta is to use the Docker image available
29
on [Docker hub][1]. Alternatively, follow the ["getting started"][2]
30
tutorial to deploy Alerta to an Ubuntu server. More advanced
31
configurations are out os scope of this tutorial but information
32
-about different deployment scenaries can be found in the [docs][3].
32
+about different deployment scenarios can be found in the [docs][3].
33
34
[1]: https://hub.docker.com/r/alerta/alerta-web/
35
@@ -86,7 +86,7 @@ We can test alarms using the standard approach:
86
87
Note: Netdata will send 3 alarms, and because last alarm is "CLEAR"
88
you will not see them in main Alerta page, you need to select to see
89
-"closed" alarma in top-right lookup. A little change in `alarm-notify.sh`
89
+"closed" alarm in top-right lookup. A little change in `alarm-notify.sh`
90
that let us test each state one by one will be useful.
91
92
For more information see <https://docs.alerta.io>
health/notifications/awssns/README.md
+1
-1
@@ -37,7 +37,7 @@ Once that's done, you're ready to go and can specify the desired topic ARN as a
37
Notes:
38
39
- Netdata's native email notification support is far better in almost all respects than it's support through Amazon SNS. If you want email notifications, use the native support, not SNS.
40
- - If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration. This variable supports all the same vairiables you can use in custom notifications.
40
+ - If you need to change the notification format for SNS notifications, you can do so by specifying the format in `AWSSNS_MESSAGE_FORMAT` in the configuration. This variable supports all the same variables you can use in custom notifications.
41
- While Amazon SNS supports sending differently formatted messages for different delivery methods, Netdata does not currently support this functionality.
42
43
[](<>)
health/notifications/email/README.md
+1
-1
@@ -55,7 +55,7 @@ sendmail="/usr/bin/msmtp"
55
(sudo) su -s /bin/bash netdata
56
```
57
- Configure `~/.msmtprc` as shown [in the documentation](https://marlam.de/msmtp/documentation/).
58
-- Finaly set the appropriate permissions on the `.msmtprc` file :
58
+- Finally set the appropriate permissions on the `.msmtprc` file :
59
```sh
60
chmod 600 ~/.msmtprc
61
```
health/notifications/irc/README.md
+1
-1
@@ -29,7 +29,7 @@ Set the path for `nc` in `/etc/netdata/health_alarm_notify.conf` (to edit it on
29
nc="/usr/bin/nc"
30
```
31
32
-2. Αn `IRC_NETWORK` to which your preffered channels belong to.
32
+2. Αn `IRC_NETWORK` to which your preferred channels belong to.
33
3. One or more channels ( `DEFAULT_RECIPIENT_IRC` ) to post the messages to.
34
4. An `IRC_NICKNAME` and an `IRC_REALNAME` to identify in IRC.
35
health/notifications/prowl/README.md
+2
-2
@@ -6,7 +6,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notificat
6
# Prowl
7
8
[Prowl](https://www.prowlapp.com/) is a push notification service for iOS devices. Netdata
9
-supprots delivering notifications to iOS devices through Prowl.
9
+supports delivering notifications to iOS devices through Prowl.
10
11
Because of how Netdata integrates with Prowl, there is a hard limit of
12
at most 1000 notifications per hour (starting from the first notification
@@ -20,7 +20,7 @@ the alert, directly to the chart that it triggered on.
20
21
## configuration
22
23
-To use this, you will need a Prowl API key, which can be rquested through
23
+To use this, you will need a Prowl API key, which can be requested through
24
the Prowl website after registering.
25
26
Once you have an API key, simply specify that as a recipient for Prowl
health/notifications/rocketchat/README.md
+1
-1
@@ -47,6 +47,6 @@ role_recipients_rocketchat[webmaster]="marketing development"
47
```
48
49
The keywords `systems`, `databases`, `marketing`, `development` are RocketChat channels (they should already exist).
50
-Both public and private channels can be used, even if they differ from the channel configured in yout RocketChat incomming webhook.
50
+Both public and private channels can be used, even if they differ from the channel configured in your RocketChat incoming webhook.
51
52
[](<>)
health/notifications/stackpulse/README.md
+2
-2
@@ -7,7 +7,7 @@ custom_edit_url: https://github.com/netdata/netdata/edit/master/health/notificat
7
8
# Send notifications to StackPulse
9
10
-[StackPulse](https://stackpulse.com/) is a software-as-a-service platform for site reliablility engineering.
10
+[StackPulse](https://stackpulse.com/) is a software-as-a-service platform for site reliability engineering.
11
It helps SREs, DevOps Engineers and Software Developers reduce toil and alert fatigue while improving reliability of
12
software services by managing, analyzing and automating incident response activities.
13
@@ -18,7 +18,7 @@ Sending Netdata alarm notifications to StackPulse allows you to create smart aut
18
- Performing triage actions and analyzing their results
19
- Orchestrating incident management and notification flows
20
- Performing automatic and semi-automatic remediation actions
21
-- Analzying incident data and remediation patterns to improve reliability of your services
21
+- Analyzing incident data and remediation patterns to improve reliability of your services
22
23
To send the notification you need:
24
packaging/DISTRIBUTIONS.md
+1
-1
@@ -19,7 +19,7 @@ have complete visibility over the range of support.
19
- **Family**: The family that the OS belongs to
20
- **CI: Smoke Testing**: Smoke testing has been implemented on our CI, to prevent broken code reaching our users
21
- **CI: Testing**: Testing has been implemented to prevent broken or problematic code reaching our users
22
-- **CD**: Continious deployment support has been fully enabled for this operating system
22
+- **CD**: Continuous deployment support has been fully enabled for this operating system
23
- **.DEB**: We provide a `.DEB` package for that particular operating system
24
- **.RPM**: We provide a `.RPM` package for that particular operating system
25
- **Installer**: Running netdata from source, using our installer, is working for this operating system
packaging/docker/README.md
+2
-2
@@ -15,7 +15,7 @@ Starting with v1.12, Netdata collects anonymous usage information by default and
15
about the information collected, and learn how to-opt, on our [anonymous statistics](/docs/anonymous-statistics.md)
16
page.
17
18
-The usage statistics are _vital_ for us, as we use them to discover bugs and priortize new features. We thank you for
18
+The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
19
_actively_ contributing to Netdata's future.
20
21
## Limitations running the Agent in Docker
@@ -107,7 +107,7 @@ You can control how the health checks run by using the environment variable `NET
107
correctly or not. This is sufficient to ensure that Netdata did not
108
hang during startup, but does not provide a rigorous verification
109
that the daemon is collecting data or is otherwise usable.
110
-- If set to anything else, the health check will treat the vaule as a
110
+- If set to anything else, the health check will treat the value as a
111
URL to check for a 200 status code on. In most cases, this should
112
start with `http://localhost:19999/` to check the agent running in
113
the container.
packaging/installer/REINSTALL.md
+1
-1
@@ -11,7 +11,7 @@ Netdata Agent on your node.
11
12
Before you try reinstalling Netdata, figure out which [installation method you
13
used](/packaging/installer/UPDATE.md#determine-which-installation-method-you-used) if you do not already know. This will
14
-deterimine the reinstallation method.
14
+determine the reinstallation method.
15
16
## One-line installer script (`kickstart.sh`)
17
packaging/installer/UPDATE.md
+2
-2
@@ -26,7 +26,7 @@ most installations, this is `/etc/netdata`.
26
Use `cd` to navigate to the Netdata config directory, then use `ls -a` to look for a file called `.environment`.
27
28
- If the `.environment` file _does not_ exist, reinstall with your [package manager](#deb-or-rpm-packages).
29
-- If the `.environtment` file _does_ exist, check its contents with `less .environment`.
29
+- If the `.environment` file _does_ exist, check its contents with `less .environment`.
30
- If `IS_NETDATA_STATIC_BINARY` is `"yes"`, update using the [pre-built static
31
binary](#pre-built-static-binary-for-64-bit-systems-kickstart-static64sh).
32
- In all other cases, update using the [one-line installer script](#one-line-installer-script-kickstartsh).
@@ -118,7 +118,7 @@ installation instructions](/packaging/docker/README.md#create-a-new-netdata-agen
118
119
## macOS
120
121
-If you installed Netdata on your macOS system using Homebrew, you can explictly request an update:
121
+If you installed Netdata on your macOS system using Homebrew, you can explicitly request an update:
122
123
```bash
124
brew upgrade netdata
packaging/installer/methods/cloud-providers.md
+1
-1
@@ -89,7 +89,7 @@ to create a new firewall rule.
89
#### Amazon Web Services (AWS) / EC2
90
91
Sign in to the [AWS console](https://console.aws.amazon.com/) and navigate to the EC2 dashboard. Click on the **Security
92
-Groups** link in the naviagtion, beneath the **Network & Security** heading. Find the Security Group your instance
92
+Groups** link in the navigation, beneath the **Network & Security** heading. Find the Security Group your instance
93
belongs to, and either right-click on it or click the **Actions** button above to see a dropdown menu with **Edit
94
inbound rules**.
95
packaging/installer/methods/freebsd.md
+2
-2
@@ -80,7 +80,7 @@ The `netdata-updater.sh` script will update your Agent.
80
| `--dont-wait` | Run installation in non-interactive mode|
81
| `--auto-update` or `-u` | Install netdata-updater in cron to update netdata automatically once per day|
82
| `--stable-channel` | Use packages from GitHub release pages instead of GCS (nightly updates). This results in less frequent updates|
83
-| `--nightly-channel` | Use most recent nightly udpates instead of GitHub releases. This results in more frequent updates|
83
+| `--nightly-channel` | Use most recent nightly updates instead of GitHub releases. This results in more frequent updates|
84
| `--disable-go` | Disable installation of go.d.plugin|
85
| `--disable-ebpf` | Disable eBPF Kernel plugin (Default: enabled)|
86
| `--disable-cloud` | Disable all Netdata Cloud functionality|
@@ -103,6 +103,6 @@ The `netdata-updater.sh` script will update your Agent.
103
| `--disable-lto` | Disable Link-Time-Optimization. Default: enabled|
104
| `--disable-x86-sse` | Disable SSE instructions. By default SSE optimizations are enabled|
105
| `--zlib-is-really-here` or `--libs-are-really-here` | If you get errors about missing zlib or libuuid but you know it is available, you might have a broken pkg-config. Use this option to proceed without checking pkg-config|
106
-|`--disable-telemetry` | Use this flag to opt-out from our anonymous telemetry progam. (DO_NOT_TRACK=1)|
106
+|`--disable-telemetry` | Use this flag to opt-out from our anonymous telemetry program. (DO_NOT_TRACK=1)|
107
108
[](<>)
packaging/installer/methods/kickstart-64.md
+3
-3
@@ -37,7 +37,7 @@ The `kickstart.sh` script does the following after being downloaded and run:
37
added.
38
- Installs `netdata-updater.sh` to `cron.daily` to enable automatic updates, unless you added the `--no-updates`
39
option.
40
-- Prints a message about whether the insallation succeeded for failed for QA purposes.
40
+- Prints a message about whether the installation succeeded for failed for QA purposes.
41
42
If your shell fails to handle the above one-liner, you can download and run the `kickstart-static64.sh` script manually.
43
@@ -65,7 +65,7 @@ your installation. Here are a few important parameters:
65
Netdata better.
66
- `--no-updates`: Prevent automatic updates of any kind.
67
- `--reinstall`: If an existing installation is detected, reinstall instead of attempting to update it. Note
68
- that this cannot be used to switch betwen installation types.
68
+ that this cannot be used to switch between installation types.
69
- `--local-files`: Used for [offline installations](/packaging/installer/methods/offline.md). Pass four file paths:
70
the Netdata tarball, the checksum file, the go.d plugin tarball, and the go.d plugin config tarball, to force
71
kickstart run the process using those files. This option conflicts with the `--stable-channel` option. If you set
@@ -73,7 +73,7 @@ your installation. Here are a few important parameters:
73
74
## Verify script integrity
75
76
-To use `md5sum` to verify the intregity of the `kickstart-static64.sh` script you will download using the one-line
76
+To use `md5sum` to verify the integrity of the `kickstart-static64.sh` script you will download using the one-line
77
command above, run the following:
78
79
```bash
packaging/installer/methods/kickstart.md
+1
-1
@@ -56,7 +56,7 @@ installation. Here are a few important parameters:
56
57
## Verify script integrity
58
59
-To use `md5sum` to verify the intregity of the `kickstart.sh` script you will download using the one-line command above,
59
+To use `md5sum` to verify the integrity of the `kickstart.sh` script you will download using the one-line command above,
60
run the following:
61
62
```bash
packaging/installer/methods/kubernetes.md
+3
-3
@@ -89,7 +89,7 @@ applications](https://github.com/netdata/helmchart#service-discovery-and-support
89
by our [generic Prometheus collector](https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus).
90
91
If you haven't changed listening ports, image names, or other defaults, service discovery should find your pods, create
92
-the proper configurations based on the service that pod runs, and begin monitoring them immediately after depolyment.
92
+the proper configurations based on the service that pod runs, and begin monitoring them immediately after deployment.
93
94
However, if you have changed some of these defaults, you need to copy a file from the Netdata Helm chart repository,
95
make your edits, and pass the changed file to `helm install`/`helm upgrade`.
@@ -188,7 +188,7 @@ Cloud](https://user-images.githubusercontent.com/1153921/94497340-c1f49880-01ab-
188
## Update/reinstall the Netdata Helm chart
189
190
If you update the Helm chart's configuration, run `helm upgrade` to redeploy your Netdata service, replacing `netdata`
191
-with the name of the release, if you changed it upon installtion:
191
+with the name of the release, if you changed it upon installation:
192
193
```bash
194
helm upgrade netdata netdata/netdata
@@ -203,7 +203,7 @@ Check out our [infrastructure](/docs/quickstart/infrastructure.md) for details a
203
and learn more about [configuring the Netdata Agent](/docs/configure/nodes.md) to better understand the settings you
204
might be interested in changing.
205
206
-To futher configure Netdata for your cluster, see our [Helm chart repository](https://github.com/netdata/helmchart) and
206
+To further configure Netdata for your cluster, see our [Helm chart repository](https://github.com/netdata/helmchart) and
207
the [service discovery repository](https://github.com/netdata/agent-service-discovery/).
208
209
[](<>)
packaging/installer/methods/manual.md
+2
-2
@@ -32,7 +32,7 @@ and other operating systems and is regularly tested. You can find this tool [her
32
33
- **Debian** Linux and its derivatives (including **Ubuntu**, **Mint**)
34
35
-- **Redhat Enterprise Linux** and its derivatives (including **Fedora**, **CentOS**, **Amazon Machine Image**)
35
+- **Red Hat Enterprise Linux** and its derivatives (including **Fedora**, **CentOS**, **Amazon Machine Image**)
36
- Please note that for RHEL/CentOS you need
37
[EPEL](http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/).
38
In addition, RHEL/CentOS version 6 also need
@@ -147,7 +147,7 @@ And install the minimum required dependencies.
147
### CentOS / RHEL 8.x
148
149
For CentOS / RHEL 8.x a lot of development packages have moved out into their
150
-own separate repositories. Some other dependeicies are either missing completely
150
+own separate repositories. Some other dependencies are either missing completely
151
or have to be sourced by 3rd-parties.
152
153
CentOS 8.x:
packaging/installer/methods/packages.md
+2
-2
@@ -28,8 +28,8 @@ package downloads.
28
If you are using such a setup, there are a couple of ways to work around this:
29
30
- Configure your proxy to automatically pass through HTTPS connections without caching them. This is the simplest
31
- solution, but means that downloads of Netdata pacakges will not be cached.
32
-- Mirror the respository locally on your proxy system, and use that mirror when installing on other systems. This
31
+ solution, but means that downloads of Netdata packages will not be cached.
32
+- Mirror the repository locally on your proxy system, and use that mirror when installing on other systems. This
33
requires more setup and more disk space on the caching host, but it lets you cache the packages locally.
34
- Some specific caching proxies may have alternative configuration options to deal with these issues. Find
35
such options in their documentation.
packaging/installer/methods/pfsense.md
+1
-1
@@ -48,7 +48,7 @@ pkg add http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/py37-yaml-5.3.1.txz
48
> Python from the FreeBSD repository as instructed above.
49
50
> ⚠️ If you are using the `apcupsd` collector, you need to make sure that apcupsd is up before starting Netdata.
51
-> Otherwise a infinitely running `cat` process triggered by the default activated apcuspd charts plugin will eat up CPU
51
+> Otherwise a infinitely running `cat` process triggered by the default activated apcupsd charts plugin will eat up CPU
52
> and RAM (`/tmp/.netdata-charts.d-*/run-*`). This also applies to `OPNsense`.
53
54
## Install Netdata
packaging/installer/methods/source.md
+11
-11
@@ -62,9 +62,9 @@ Netdata Cloud functionality. To prepare this library for the build system:
62
of `packaging/mosquitto.version` in your Netdata sources.
63
2. Obtain the sources for that version by either:
64
- Navigating to https://github.com/netdata/mosquitto/releases and
65
- donwloading and unpacking the source code archive for that release.
65
+ downloading and unpacking the source code archive for that release.
66
- Cloning the repository with `git` and checking out the required tag.
67
-3. If building on a platfom other than Linux, prepare the mosquitto
67
+3. If building on a platform other than Linux, prepare the mosquitto
68
sources by running `cmake -D WITH_STATIC_LIBRARIES:boolean=YES .` in
69
the mosquitto source directory.
70
4. Build mosquitto by running `make -C lib` in the mosquitto source directory.
@@ -89,9 +89,9 @@ library for the build system:
89
of `packaging/libwebsockets.version` in your Netdata sources.
90
2. Obtain the sources for that version by either:
91
- Navigating to https://github.com/warmcat/libwebsockets/releases and
92
- donwloading and unpacking the source code archive for that release.
92
+ downloading and unpacking the source code archive for that release.
93
- Cloning the repository with `git` and checking out the required tag.
94
-3. Prepare the libweboskcets sources by running `cmake -D
94
+3. Prepare the libwebsockets sources by running `cmake -D
95
LWS_WITH_SOCKS5:bool=ON .` in the libwebsockets source directory.
96
4. Build libwebsockets by running `make` in the libwebsockets source
97
directory.
@@ -112,7 +112,7 @@ you can do the following to prepare a copy for the build system:
112
1. Verify the tag that Netdata expects to be used by checking the contents
113
of `packaging/jsonc.version` in your Netdata sources.
114
2. Obtain the sources for that version by either:
115
- - Navigating to https://github.com/json-c/json-c and donwloading
115
+ - Navigating to https://github.com/json-c/json-c and downloading
116
and unpacking the source code archive for that release.
117
- Cloning the repository with `git` and checking out the required tag.
118
3. Prepare the JSON-C sources by running `cmake -DBUILD_SHARED_LIBS=OFF .`
@@ -201,7 +201,7 @@ NPM. Once you have the required tools, do the following:
201
1. Verify the release version that Netdata expects to be used by checking
202
the contents of `packaging/dashboard.version` in your Netdata sources.
203
2. Obtain the sources for that version by either:
204
- - Navigating to https://github.com/netdata/dashboard and donwloading
204
+ - Navigating to https://github.com/netdata/dashboard and downloading
205
and unpacking the source code archive for that release.
206
- Cloning the repository with `git` and checking out the required tag.
207
3. Run `npm install` in the dashboard source tree.
@@ -216,7 +216,7 @@ and are developed in a separate repository from the mian Netdata code.
216
An installation without these collectors is still usable, but will be
217
unable to collect metrics for a number of network services the system
218
may be providing. You can either install a pre-built copy of these
219
-eollectors, or build them locally.
219
+collectors, or build them locally.
220
221
#### Installing the pre-built Go collectors
222
@@ -229,7 +229,7 @@ we officially support. To use one of these:
229
required release, and download the `go.d.plugin-*.tar.gz` file
230
for your system type and CPu architecture and the `config.tar.gz`
231
configuration file archive.
232
-3. Extract the `go.d.plugin-*.tar.gz` archive into a temprary
232
+3. Extract the `go.d.plugin-*.tar.gz` archive into a temporary
233
location, and then copy the single file in the archive to
234
`/usr/libexec/netdata/plugins.d` or the equivalent location for your
235
build of Netdata and rename it to `go.d.plugin`.
@@ -246,12 +246,12 @@ newer. Once you have the required tools, do the following:
246
1. Verify the release version that Netdata expects to be used by checking
247
the contents of `packaging/go.d.version` in your Netdata sources.
248
2. Obtain the sources for that version by either:
249
- - Navigating to https://github.com/netdata/go.d.plugin and donwloading
249
+ - Navigating to https://github.com/netdata/go.d.plugin and downloading
250
and unpacking the source code archive for that release.
251
- Cloning the repository with `git` and checking out the required tag.
252
3. Run `make` in the go.d.plugin source tree.
253
4. Copy `bin/godplugin` to `/usr/libexec/netdata/plugins.d` or th
254
- eequivalent location for your build of Netdata and rename it to
254
+ equivalent location for your build of Netdata and rename it to
255
`go.d.plugin`.
256
5. Copy the contents of the `config` directory to `/etc/netdata` or the
257
equivalent location for your build of Netdata.
@@ -274,7 +274,7 @@ using glibc or musl. To use one of these:
274
the contents of `packaging/ebpf.version` in your Netdata sources.
275
2. Go to https://github.com/netdata/kernel-collector/releases, select the
276
required release, and download the `netdata-kernel-collector-*.tar.xz`
277
- file for the libc variant your system uses (eithe rmusl or glibc).
277
+ file for the libc variant your system uses (either rmusl or glibc).
278
3. Extract the contents of the archive to a temporary location, and then
279
copy all of the `.o` and `.so.*` files and the contents of the `library/`
280
directory to `/usr/libexec/netdata/plugins.d` or the equivalent location
packaging/maintainers/README.md
+1
-1
@@ -22,7 +22,7 @@ This page tracks the package maintainers for Netdata, for various operating syst
22
| Debian | Release | @lhw @FedericoCeratto | [netdata @ debian](http://salsa.debian.org/debian/netdata) |
23
| Slackware | Release | @willysr | [netdata @ slackbuilds](https://slackbuilds.org/repository/14.2/system/netdata/) |
24
| Ubuntu | | | |
25
-| Red Hat / Fedora / Centos | | | |
25
+| Red Hat / Fedora / CentOS | | | |
26
| SUSE SLE / openSUSE Tumbleweed & Leap | | | [netdata @ SUSE OpenBuildService](https://software.opensuse.org/package/netdata) |
27
28
---
packaging/makeself/README.md
+1
-1
@@ -49,6 +49,6 @@ If Netdata crashes, `valgrind` will print a stack trace of the issue. Open a git
49
50
To stop Netdata while it runs under `valgrind`, press Control-C on the console.
51
52
-> If you omit the parameter `--undef-value-errors=no` to valgrind, you will get hundreds of errors about conditional jumps that depend on uninitialized values. This is normal. Valgrind has heuristics to prevent it from printing such errors for system libraries, but for the static Netdata binary, all the required libraries are built into Netdata. So, valgrind cannot appply its heuristics and prints them.
52
+> If you omit the parameter `--undef-value-errors=no` to valgrind, you will get hundreds of errors about conditional jumps that depend on uninitialized values. This is normal. Valgrind has heuristics to prevent it from printing such errors for system libraries, but for the static Netdata binary, all the required libraries are built into Netdata. So, valgrind cannot apply its heuristics and prints them.
53
54
[](<>)
parser/README.md
+3
-3
@@ -6,7 +6,7 @@ Usage
6
7
1. Define a structure that will be used to share user state across calls
8
1. Initialize the parser using `parser_init`
9
-2. Register keywords and assosiated callback function using `parser_add_keyword`
9
+2. Register keywords and associated callback function using `parser_add_keyword`
10
3. Register actions on the keywords
11
4. Start a loop until EOF
12
1. Fetch the next line using `parser_next`
@@ -79,11 +79,11 @@ Input
79
* PARSER_RC_ERROR -- Callback failed, exit
80
81
Output
82
-- The correspoding keyword and callback will be registered
82
+- The corresponding keyword and callback will be registered
83
84
Returns
85
- 0 maximum callbacks already registered for this keyword
86
-- > 0 which is the number of callbacks assosiated with this keyword.
86
+- > 0 which is the number of callbacks associated with this keyword.
87
88
89
----
streaming/README.md
+1
-1
@@ -287,7 +287,7 @@ Now you update the list of certificates running the following, again either as `
287
```
288
289
> Some Linux distributions have different methods of updating the certificate list. For more details, please read this
290
-> guide on [addding trusted root certificates](https://github.com/Busindre/How-to-Add-trusted-root-certificates).
290
+> guide on [adding trusted root certificates](https://github.com/Busindre/How-to-Add-trusted-root-certificates).
291
292
Once you update your certificate list, you can set the stream parameters for Netdata to trust the parent certificate. Open `stream.conf` for editing and change the following lines:
293
web/api/badges/README.md
+5
-5
@@ -188,10 +188,10 @@ These are options dedicated to badges:
188
The following parameters specify colors of each individual part of the badge. Each parameter is documented in detail
189
below.
190
191
- | Area of badge | Backgroud color parameter | Text color parameter |
192
- | ---: | :-----------------------: | :------------------: |
193
- | Label (left) part | `label_color` | `text_color_lbl` |
194
- | Value (right) part | `value_color` | `text_color_val` |
191
+ | Area of badge | Background color parameter | Text color parameter |
192
+ | ---: | :------------------------: | :------------------: |
193
+ | Label (left) part | `label_color` | `text_color_lbl` |
194
+ | Value (right) part | `value_color` | `text_color_val` |
195
196
- `label_color=COLOR`
197
@@ -223,7 +223,7 @@ These are options dedicated to badges:
223
224
The above will set `grey` if no value exists (not collected within the `gap when lost iterations above` in
225
`netdata.conf` for the chart), `green` if the value is less than 10, `yellow` if the value is less than 100, and
226
- so on. Netdata will use `red` if no other conditions match. Only integers are suported as values.
226
+ so on. Netdata will use `red` if no other conditions match. Only integers are supported as values.
227
228
The supported operators are `<`, `>`, `<=`, `>=`, `=` (or `:`), and `!=` (or `<>`).
229
web/api/health/README.md
+1
-1
@@ -75,7 +75,7 @@ curl "http://NODE:19999/api/v1/manage/health?cmd=RESET" -H "X-Auth-Token: Mytoke
75
By default access to the health management API is only allowed from `localhost`. Accessing the API from anything else will return a 403 error with the message `You are not allowed to access this resource.`. You can change permissions by editing the `allow management from` variable in `netdata.conf` within the [web] section. See [web server access lists](/web/server/README.md#access-lists) for more information.
76
77
The command `RESET` just returns Netdata to the default operation, with all health checks and notifications enabled.
78
-If you've configured and entered your token correclty, you should see the plain text response `All health checks and notifications are enabled`.
78
+If you've configured and entered your token correctly, you should see the plain text response `All health checks and notifications are enabled`.
79
80
### Disable or silence all alarms
81
web/gui/custom/README.md
+1
-1
@@ -324,7 +324,7 @@ Netdata supports a number of chart libraries. The default chart library is
324
Each chart library has a number of specific settings. To learn more about them,
325
you should investigate the documentation of the given chart library, or visit
326
the appropriate JavaScript file that defines the library's options. These files
327
-are concatenated into the monolithin `dashboard.js` for deployment.
327
+are concatenated into the monolithic `dashboard.js` for deployment.
328
329
- [Dygraph](https://github.com/netdata/netdata/blob/5b57fc441c40959514c4e2d0863be2e6a417e352/web/gui/dashboard.js#L2034)
330
- [d3](https://github.com/netdata/netdata/blob/5b57fc441c40959514c4e2d0863be2e6a417e352/web/gui/dashboard.js#L4095)
web/server/static/README.md
+1
-1
@@ -1,6 +1,6 @@
1
<!--
2
title: "`static-threaded` web server"
3
-description: "The Netdata Agent's static-threaded web server spawns a fixed nubmer of threads that listen to web requests and uses non-blocking I/O."
3
+description: "The Netdata Agent's static-threaded web server spawns a fixed number of threads that listen to web requests and uses non-blocking I/O."
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/web/server/static/README.md
5
-->
6