snmp gloriously broken in 1.22 again.

[bunnyevans]

Relevant telegraf.conf

# This config was made after the grand gosnmp borkage and has worked from March 22nd~
# regressions like this are annoying and make one never want to update ever.
# 
# It might have to be changed, IF SO, some clueful error messages would help.
#
[[inputs.snmp]]
   agents = [ "10.0.0.1" ]
   interval = "60s" timeout = "10s" retries = 2 version = 2 community = "public" max_repetitions = 10
   name_override = "snmp.rtx830" # name = "snmp.rtx830"
   tagexclude=["agent_host"]
# can't find ifTable without this!
   path = ["/usr/local/share/snmp/mibs"]

   [[inputs.snmp.field]] is_tag = true oid = "sysName.0"

Logs from Telegraf

/usr/local/bin/telegraf --config=/usr/local/etc/telegraf.conf --config-directory=/usr/local/etc/telegraf.conf.TEST --test --debug --input-filter snmp


2022-04-10T21:55:50+09:00 E! [telegraf] Error running agent: could not initialize input inputs.snmp: initializing field : translating: sysName.0: Unknown Object Identifier (Sub-id not found: (top) -> sysName): exit status 2

System info

Telegraf-1.22.0 freebsd 13

Docker

No response

Steps to reproduce

have working snmp on previous version (where MIB filenames need to match.)

upgrade

borked.

Expected behavior

It to work.

Actual behavior

competely uninformative crash.
There are zero clues in that error message as to what is going wrong.

Additional info

Nightly;
37236416 Apr 10 16:42 telegraf-nightly_freebsd_amd64.tar.gz = NG (1.23)
Freebsd pkg:
telegraf-1.22.0_16ff3f32db5.pkg = NG
telegraf-1.21.419d92c9d00.pkg = OK

[reimda]

1.22.0 switched back to using netsnmp for oid translation because there was so much trouble with telegraf's gosmi translator. See #10802. This was announced in the release notes for 1.22.0: https://github.com/influxdata/telegraf/releases/tag/v1.22.0

If you want to stick with gosmi, add the setting translator = "gosmi" in your agent config. Otherwise you can switch back to config you used before 1.21.0.

Your sarcastic tone is rude. You included these phrases in the issue: "gloriously broken", "borked", "grand gosnmp borkage", and you described expected behavior "it to work". Of course it's supposed to work. Saying it's not working for you in multiple sarcastic ways doesn't help anything. In the future please be less sarcastic.

[bunnyevans]

Indeed you are correct.
I think the problem here was caused by freebsd's pkg upgrate thing giving zero warnings of show stopping changes. Just like the initial change to gosmi.

What are the plans regarding gosmi/netsnmp going forward?
I spent ages struggling with gosmi to get working configurations and I would hope that it will continue to be developed/maintained.

[Hipska]

Our goal for gosmi is for it to become the default translator again in future releases.

[telegraf-tiger]

Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you!