Replies: 1 comment
-
Hi @BYT3M3
And then I have this configured like this in the generator.yml:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Host operating system: output of
uname -a
Linux prometheus-01 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux
snmp_exporter version: output of
snmp_exporter --version
snmp_exporter, version 0.25.0 (branch: HEAD, revision: 9c42d6c)
What device/snmpwalk OID are you using?
Not applicable
If this is a new device, please link to the MIB(s).
Not applicable
What did you do that produced an error?
I tried to generate a minimal snmp.yaml file, so I could just query a sysUpTime.
My generator.yml file looks like:
I converted this to snmp.yml using
./generator -g /tmp/generator.yml -o /tmp/snmp.yml
and my snmp.yml looks like:What did you expect to see?
When surfing to hostname:9116/config I expect to see:
And when I try to query a machines sysUpTime, I expect to see:
What did you see instead?
When going to hostname:9116/config I saw:
And querying the ifMib, yielded:
How did I work around this issue?
I just replaced ~ (which is the standard reference to the home directory) with an absolute or a relative path and this did work. This issue is a user friendliness bug. This could be fixed by indicating more clearly that the config file wasn't found or even better: just support using ~.
Beta Was this translation helpful? Give feedback.
All reactions