Problem / Motivation

While running the Celo Oracles, it can happen that the Oracles fail to send reports due to the max price cross-sectional deviation being too large. In such a case, the logs of the Oracle will show something like Max price cross-sectional deviation too large (0.1} >= 0.01).

With monitoring and alerting for the metric oracle_transaction_success_count, an alert is triggered once the oracle fails to send reports.

In my case, this leads to alerts being triggered because the max price cross-sectional deviation is too large. In my opinion, this case should not trigger an alert, since the oracle works as expected. It's not sending reports due to the deviation being too large. I'd like to avoid being alerted in a case like this.

Proposed Solution

The basic problem is, that currently there is no way to find out (by metrics) if the oracle stopped sending reports because of the deviation being too large. This can be solved by adding a metric for the current max percentage deviation. This way, the alert could be triggered only if the oracle fails to send reports, and the max percentage deviation is below a defined threshold.

I will create a PR for this.