So the grafana suggested use of rate proved flaky in prod for what we need for the tekton results api success rate for basic debug, which includes historical
If we were ever to use this for alerts, we'll add a panel that does the increase(...) to adjust for resets, etc.
So the grafana suggested use of rate proved flaky in prod for what we need for the tekton results api success rate for basic debug, which includes historical
If we were ever to use this for alerts, we'll add a panel that does the
increase(...)to adjust for resets, etc.for more on rate vs. increase some internet searching will get you deep dive break downs like https://stackoverflow.com/questions/54494394/do-i-understand-prometheuss-rate-vs-increase-functions-correctly
We now have
@jkhelil @enarha ptal
@savitaashture fyi
rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED