diff options
| author | Olivier Lambert <olivier.lambert@vates.fr> | 2018-09-23 01:26:58 +0200 |
|---|---|---|
| committer | Costa Tsaousis <costa@tsaousis.gr> | 2018-09-23 02:26:58 +0300 |
| commit | 644307a4a5cab23fd858c2e140705c957b5be9a0 (patch) | |
| tree | 3e24a74923028d826906cc5c720d9279d78fdfce | |
| parent | daaa9cd82fb31bf4413fa0d9e451f6ab31c8bbf1 (diff) | |
Fix typo in documentation (#4255)
| -rw-r--r-- | conf.d/node.d/snmp.conf.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/conf.d/node.d/snmp.conf.md b/conf.d/node.d/snmp.conf.md index e5243afcac..d75c962b6b 100644 --- a/conf.d/node.d/snmp.conf.md +++ b/conf.d/node.d/snmp.conf.md @@ -177,7 +177,7 @@ If it works, restart netdata to activate the snmp collector and refresh the dash ## Data collection speed -Keep in mind that many SNMP switches are routers are very slow. They may not be able to report values per second. If you run `node.d.plugin` in `debug` mode, it will report the time it took for the SNMP device to respond. My switch, for example, needs 7-8 seconds to respond for the traffic on 24 ports (48 OIDs, in/out). +Keep in mind that many SNMP switches and routers are very slow. They may not be able to report values per second. If you run `node.d.plugin` in `debug` mode, it will report the time it took for the SNMP device to respond. My switch, for example, needs 7-8 seconds to respond for the traffic on 24 ports (48 OIDs, in/out). Also, if you use many SNMP clients on the same SNMP device at the same time, values may be skipped. This is a problem of the SNMP device, not this collector. |