Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inputs.snmp not reaching out to collect metrics #16458

Open
Andrene opened this issue Jan 31, 2025 · 0 comments
Open

inputs.snmp not reaching out to collect metrics #16458

Andrene opened this issue Jan 31, 2025 · 0 comments
Labels
bug unexpected problem or unintended behavior

Comments

@Andrene
Copy link

Andrene commented Jan 31, 2025

Relevant telegraf.conf

[agent]
  interval = "10s"
  round_interval = true

  metric_batch_size = 10000

  metric_buffer_limit = 100000

  collection_jitter = "0s"

  flush_interval = "10s"

  flush_jitter = "0s"

  precision = "0s"
  debug = true
  snmp_translator = "gosmi"
  ## Override default hostname, if empty use os.Hostname()
  hostname = ""
  ## If set to true, do no set the "host" tag in the telegraf agent.
  omit_hostname = false

[[outputs.file]]
  files = ["stdout"]

[[inputs.snmp]]
  agents = ["udp://ip-address:161"]
  version = 3
  sec_name = "User"
  auth_protocol = "SHA"
  auth_password = "AuthPass"
  sec_level = "authPriv"
  context_name = ""
  priv_protocol = "AES"
  priv_password = "PrivPass"
  agent_host_tag = "source"
  path = ["/home/me/.snmp/mibs"]

  [[inputs.snmp.table]]
    name = "cpu"
    oid = "1.3.6.1.4.1.14823.2.2.1.2.1.13"
    index_as_tag = true

Logs from Telegraf

[me@metestbox ~]$ telegraf  --config minimal.telegraf.conf --debug
2025-01-31T19:41:11Z I! Loading config: minimal.telegraf.conf
2025-01-31T19:41:11Z I! Starting Telegraf 1.33.0 brought to you by InfluxData the makers of InfluxDB
2025-01-31T19:41:11Z I! Available plugins: 236 inputs, 9 aggregators, 33 processors, 26 parsers, 63 outputs, 6 secret-stores
2025-01-31T19:41:11Z I! Loaded inputs: snmp
2025-01-31T19:41:11Z I! Loaded aggregators:
2025-01-31T19:41:11Z I! Loaded processors:
2025-01-31T19:41:11Z I! Loaded secretstores:
2025-01-31T19:41:11Z I! Loaded outputs: file
2025-01-31T19:41:11Z I! Tags enabled: host=metestbox
2025-01-31T19:41:11Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:"metestbox", Flush Interval:10s
2025-01-31T19:41:11Z D! [agent] Initializing plugins
2025-01-31T19:41:13Z D! [agent] Connecting outputs
2025-01-31T19:41:13Z D! [agent] Attempting connection to [outputs.file]
2025-01-31T19:41:13Z D! [agent] Successfully connected to outputs.file
2025-01-31T19:41:13Z D! [agent] Starting service inputs
2025-01-31T19:41:23Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
2025-01-31T19:41:33Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
2025-01-31T19:41:43Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
2025-01-31T19:41:53Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
2025-01-31T19:42:03Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
2025-01-31T19:42:13Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
^C2025-01-31T19:42:13Z D! [agent] Stopping service inputs
2025-01-31T19:42:13Z D! [agent] Input channel closed
2025-01-31T19:42:13Z I! [agent] Hang on, flushing any cached metrics before shutdown
2025-01-31T19:42:13Z D! [outputs.file] Buffer fullness: 0 / 100000 metrics
2025-01-31T19:42:13Z I! [agent] Stopping running outputs
2025-01-31T19:42:13Z D! [agent] Stopped Successfully

System info

Telegraf 1.33.0, RHEL 9.5

Docker

No response

Steps to reproduce

  1. Install AOS 8.10 mibs in snmp mibs path
  2. Start tcpdump looking for port 161 traffic
  3. Run minimal.telegraf.conf against a Aruba 9240 WIreless controller

Expected behavior

Metrics are collected by telegraf and network traffic is observed in tcpdump

Actual behavior

No metrics are collected and no network traffic is observed

Additional info

This was working when I was using the net-snmp translator, but I've since moved over to gosmi.

Theres no logging telegraf side that indicates it's unhappy with anything I've set so not sure why its not even attempting to reach out

@Andrene Andrene added the bug unexpected problem or unintended behavior label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant