[inputs.snmp_trap] Error resolving OID oid=.1.3.6.1.2.1.1.3.0

Anaisdg · November 27, 2023, 8:36pm

Hello @Vasa,
I’m not sure but it looks similar to:

github.com/influxdata/telegraf

exec plugin: allow using glob pattern in command list

influxdata:master ← peekeri:exec_glob

opened 09:05AM - 03 May 16 UTC

peekeri

+91 -8

Allow using glob pattern in the command list in configuration. This enables for …example placing all commands in a single directory and using /path/to/dir/*.sh as one of the commands to run all shell scripts in that directory. Glob patterns are applied on every run of the commands, so matching commands can be added without restarting telegraf. This is a second try for this change. The previous PR #1127 broke existing functionality in two ways: - commands with arguments got ignored - commands in PATH got ignored These issues are addressed now by: - splitting the command into actual command and arguments before globbing - using the command as-is in case glob returns no matches. Added also a couple of tests to see that those are actually fixed. Not sure though if we can assume presence of `/bin/echo`?

And

What version of telegraf are you using?

Topic		Replies	Views
SNMP_TRAP : Error resolving OID Telegraf	3	932	August 8, 2022
[inputs.snmp_trap] Error resolving OID oid=.1.3.6.1.2.1.1.3.0, source=192.168.1.19: not found Telegraf	9	651	February 27, 2024
Telegraf v1.22.0 , translating traps with netsnmp not working Telegraf	3	966	April 14, 2022
E! [inputs.snmp_trap] Error resolving OID oid=.1.3.6.1.2.1.1.3.0, source=w.x.y.z.: not found Telegraf smnp	6	113	June 5, 2024
Telegraf 1.20.4 some SNMP traps failing whilst no issues with 1.18 Telegraf telegraf , smnp	16	1511	May 20, 2022

[inputs.snmp_trap] Error resolving OID oid=.1.3.6.1.2.1.1.3.0

Related topics