slashdoom / aruba_exporter

Prometheus exporter for Aruba switches, instant APs and controllers
MIT License
8 stars 6 forks source link

Failed to scrape content with empty command match and no metrics output #4

Open liam-ng opened 6 months ago

liam-ng commented 6 months ago

Hello team, Did anyone run into the same issue? could anyone share some insight how to troubleshoot this? Thank you all in advance!

Error Message / Output:

Only aruba_up gauge is scraped after 15 minutes aruba_exporter metrics output.txt

Many empty command match:, ran commands every 5 minutes or so, and finally timeout. aruba_exporter service status.txt

Config file

./aruba_exporter -config.file=config.yaml


level: debug timeout: 180 batch_size: 20000 username: operator password: P@ssw0rd!

key_file: /path/to/key

devices:

  • host: 192.168.90.15

features: system: true environment: false interfaces: true optics: false routes: false wireless: false

Hardware-wise

Update

slashdoom commented 5 months ago

Was your main.go modified? In the source, line 75 is whitespace and line 76 is devices, err = devicesForConfig(c) but it looks like there is a typo in yours, defvicesForConfig.

newArubaCollector comes from aruba_collector.go

liam-ng commented 3 months ago

Thank you so much for the response. I revisited the issue today, the main.go is not modified, sorry for the typo:

# command-line-arguments
./main.go:75:17: undefined: devicesForConfig
./main.go:156:7: undefined: newArubaCollector

I downloaded and re-built the aruba_exporter again. It has the same issue with empty command match. From the Aruba 8100 log, I can see the operator user from my config.yml logged in and out when I go to http://:9909/metrics

Please let me know if there is anything I should try, thank you!