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
Powervault ME Sensors #15814
base: master
Are you sure you want to change the base?
Powervault ME Sensors #15814
Conversation
Hi @TheMysteriousX |
Any reason this can't be done in yaml? |
You have to know in advance what type of sensor is at an OID to use YAML. The sensors presented are not tabulated - you have to poll it, then parse it to see what type of sensor you got. |
4954305
to
eccd379
Compare
This is good to go, thought there was an issue with discovery but it's down to a database column being too small. |
The example this was duplicated from will be fixed in another PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
99% sure this can be in yaml.
You use skip_values to reject everything not of the type for that sensor.
I'm going to need an example because I've found no documented way to parse descriptions with YAML. |
I've tested it with skip values as you suggested, and on every poll there is a sensor update message logged for every single sensor as the sensor description changes. Unless I've missed something, there's no support in simple template for what you're asking me to do: All it supports are simple substitutions. |
Wouldn't this work? current:
data:
-
oid: FCMGMT-MIB::connUnitSensorTable
value: FCMGMT-MIB::connUnitSensorMessage
num_oid: '.1.3.6.1.3.94.1.8.1.6.{{ $index }}'
descr: FCMGMT-MIB::connUnitSensorName
skip_values:
-
oid: FCMGMT-MIB::connUnitSensorCharacteristic
op: '!='
value: 6 # might be currentValue instead |
The device does not produce a value that is valid for YAML. You can't graph "24-port Expander, Right Sideplane: 43 C 109.40F". Your example is essentially what I did, but it doesn't work due to the values needing to be parsed.
Slightly broken formatting as snmp:walk doesn't actually print anything, despite walking successfully:
|
Please give a short description what your pull request is for
DO NOT DELETE THE UNDERLYING TEXT
Please note
Testers
If you would like to test this pull request then please run:
./scripts/github-apply <pr_id>
, i.e./scripts/github-apply 5926
After you are done testing, you can remove the changes with
./scripts/github-remove
. If there are schema changes, you can ask on discord how to revert.