I might be covering old ground, but based on what I can see (migging columns) in order for custom polling to work you have to have a few things:
1. A mib expression. This can be a single oid or mathmatical calculation involving multiple oOIDs constants and operands.
2. A polling policy. this says use a particular mib expression apply it to a defined group of elements t what interval.
3. Threshold (time or counter) or Comparison Matrix. These are the values you want to compare with the value you obtained with your polling policy. Thresholds are seeing if a returned polled value is greater than or less than a number you defined. they can be upper and lower but you must specify a rearm number (the value at which the condition is no longer valid usually one less or one more). Comparison Matricies allow you to set specific conditions and state values (normal , major critical, etc) for returned numbers. This is more helpful when you have a tabular set of conditions from the MIB.
I dont see #3 as being applied in your jpg.
Component Gage alarming is an out of the box ability configured by vendor in a binary file that you cannot modify or read. I order for this out of the box alarming to function you must have "Enable Node Component Polling" for the node or element enabled in Monitoring Settings, as well as the associated Management event under Incidents.
Have a nice day :)
Andy Kemp I've lasted longer in the technology industry than most certifications.
I found the problem that will not collect data and this is by Custom Poller and had to delete and recreate collections and policies. Still do not know why the Custom poller not work until you reconfigure.