Hello Andrew,
thank you for your KB-Post.
While you've already "answered it yourself", allow me to explain why it is like this. :) - Please refer to the following:
Specifically, to the "The issue with state averages" section. The printer sensor does some internal calculations, but essentially it's based on this OID:
prtMarkerSuppliesLevel 1.3.6.1.2.1.43.11.1.1.9 |
The current level if this supply is a container; remaining space if this supply is a receptacle. If this supply container/receptacle can reliably sense this value, the value is reported by the printer and is read- only; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (- 1) means other and specifically indicates that the sub- unit places no restrictions on this parameter. The value (-2) means unknown. A value of (-3) means that the printer knows that there is some supply/remaining space, respectively. |
This means that we need to take into account the following states:
- (- 1) means other and specifically indicates that the sub- unit places no restrictions on this parameter.
- The value (-2) means unknown.
- A value of (-3) means that the printer knows that there is some supply/remaining space, respectively.
To handle these values the sensor uses a Range-based lookup. This allows the sensor to evaluate tonner usage exactly* like channel limits would, but "messes-up" the calculation of the averages in graphs because of the dilemma with "state averages".
Keep in mind however that if you use lower warning/error limits in the sensor, you may get an "incorrect alert" if the printer ever reports -1, -2 and -3 (since it's probably lower than your set lower limit, but doesn't necessarily mean that you're out of toner).
Cheers!
Luciano Lingnau [Paessler Support]
Add comment