DXO2 alarm thresholds not inverted for operator "less than"

Products

• DX Operational Observability

Issue/Introduction

If changing the alarm comparison operator from the default "greater than" to "less than", then the order of the thresholds stays the same and requires that the critical threshold "Value must be less than Major Threshold". Actually with "less than" the major threshold should be lower than the critical threshold.

Resolution

Workaround: Use the comparison operator “Equal To” and set critical = 1 and major = 2 (You may want to set major to a higher value if there are issues.)

Additional Information

UMA metric: Kubernetes|Namespaces|<namespace>|Pods|<pod>:Pod Ready State
Values:
0 = not ready
1 = ready

Use case:

Want to alarm when the value is < 1. Tried using the “less than” operator.

But it requires good value > major/warning threshold > critical threshold.

This is not possible with integer threshold values. If the critical threshold<1, major threshold would have to be <2 but that would raise an alarm for a value of 1 which is not correct.

 

Notes:

• The “less than” operator does not work for the (not so infrequent) semantics of 0 = not ok/1 = ok. Use “Equal To” operator in that case
• Critical is a more severe condition than Major. So in case of 'Less than', Critical threshold is expected to be lesser than Major.