Hi,
We are making extensive use of SNMP tables for monitoring things like CPU, RAM, PSU, fan and HDD/SDD health.
Threshold triggering in tables appears to be a bit hit and miss though.
For example right now I have a system with a disk that reports "Predictive Failure" in the HP System Management Homepage on the server itself.
Our NetXMS picks this up, transforms the numerical value reported into a string to match "Predictive Failure" - and shoul dthen alert on this.
The latter part is not working. I have seen this before with string matching and "equal to" and sometimes switching to "like" worked. In this particular case that didn't work either. Changing to "not like" just for testing triggered an immediate alarm, so it sure looks like what I am looking for does not match what NetXMS finds in the database?
See attached images showing the collected data (note: Display Name matches Column Name) as well as the configured Thresholds.
I also attached the template - nothing special really.
Now I am not sure if there may be other items in an unhealthy state right now, where NetXMS just doesn't create an alarm. The only reason I picked this one up was because I just added the system as a node to NetXMS while it was in that state already.
Thanks
We are making extensive use of SNMP tables for monitoring things like CPU, RAM, PSU, fan and HDD/SDD health.
Threshold triggering in tables appears to be a bit hit and miss though.
For example right now I have a system with a disk that reports "Predictive Failure" in the HP System Management Homepage on the server itself.
Our NetXMS picks this up, transforms the numerical value reported into a string to match "Predictive Failure" - and shoul dthen alert on this.
The latter part is not working. I have seen this before with string matching and "equal to" and sometimes switching to "like" worked. In this particular case that didn't work either. Changing to "not like" just for testing triggered an immediate alarm, so it sure looks like what I am looking for does not match what NetXMS finds in the database?
See attached images showing the collected data (note: Display Name matches Column Name) as well as the configured Thresholds.
I also attached the template - nothing special really.
Now I am not sure if there may be other items in an unhealthy state right now, where NetXMS just doesn't create an alarm. The only reason I picked this one up was because I just added the system as a node to NetXMS while it was in that state already.
Thanks