docs(inputs.snmp): Explain different snmp backends (#12627)

This commit is contained in:
Joshua Powers 2023-02-07 09:19:29 -07:00 committed by GitHub
parent 80b48774ac
commit 3894ca6b91
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 30 additions and 2 deletions

View File

@ -18,6 +18,20 @@ See the [CONFIGURATION.md][CONFIGURATION.md] for more details.
[CONFIGURATION.md]: ../../../docs/CONFIGURATION.md#plugins
## SNMP backend: gosmi and netsnmp
Telegraf has two backends to translate SNMP objects. By default, Telegraf will
use `netsnmp`, however, this option is deprecated and it is encouraged that
users migrate to `gosmi`. If users find issues with `gosmi` that do not occur
with `netsnmp` please open a project issue on GitHub.
The SNMP backend setting is a global-level setting that applies to all use of
SNMP in Telegraf. Users can set this option in the `[agent]` configuration via
the `snmp_translator` option. See the [agent configuration][AGENT] for more
details.
[AGENT]: ../../../docs/CONFIGURATION.md#agent
## Configuration
```toml @sample.conf

View File

@ -29,6 +29,20 @@ to use them.
[SECRETSTORE]: ../../../docs/CONFIGURATION.md#secret-store-secrets
## SNMP backend: gosmi and netsnmp
Telegraf has two backends to translate SNMP objects. By default, Telegraf will
use `netsnmp`, however, this option is deprecated and it is encouraged that
users migrate to `gosmi`. If users find issues with `gosmi` that do not occur
with `netsnmp` please open a project issue on GitHub.
The SNMP backend setting is a global-level setting that applies to all use of
SNMP in Telegraf. Users can set this option in the `[agent]` configuration via
the `snmp_translator` option. See the [agent configuration][AGENT] for more
details.
[AGENT]: ../../../docs/CONFIGURATION.md#agent
## Configuration
```toml @sample.conf