Currently I try to find a way to monitor the change of a string-attribute within Spectrum. The attribute is part of a table and I need to monitor all instances.From time to time the device mixes up the instances so a specific string from the table suddenly has a new instance-id. So basically were talking about
an index-shift (well known SNMP issue). Let me make an example:
For this example I would need three events for Instance 1, 2 and 3.
I'm looking for an efficient way to monitor and alarm those changes. I've hundred and more devices which have this issue and the string
values change from device to device. I thought about using SpectroWATCHes but couldn't figure out a way to solve this. I tried it with
one watch polling the instances and comparing this to an on-demand watch which would kinda hold the reference values... that did not work.
Has anyone an idea about this? I know SpectroWATCHes are not very strong when it comes to string attributes as the nature of a watch lies more
in numeric values. At the end I could script something but I rather prefere an out-of-the-box solution with Spectrum.
Thanks a lot for any hint!
Are the strings fixed or flexible? In other words, is FirstStringValue constant relative to itself and when it moves to the wrong index?
Yes the string is fixed, just the position within the tables changes.
I've done something similar with a watch on dskErrorMsg from the ucd-snmp mib disk table.
dskErrorMsgThreshold is just an empty string. That works, so there's got to be a way to do what you want.
Maybe take an approach like the time over threshold watches in the documentation? Or an evaluate on change watch?
Nevermind the evaluate on change, I played around with that some and it only works with database or memory flagged attributes, so I'm guessing it wont apply here.
I've tried out a couple different variations on this, and while I did manage to get watches to record different values for text string list attributes over time, I couldn't get it to do a reasonable comparison.
This was extremely helpful. Thank you for taking the time to answer this.