You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EXECUTION_DURATION is written only after the indexer succeeds, this means that when it is not running, or erroring, the last successful duration is exposed via the /metrics endpoint. Grafana will continue to scrape this metric giving the appearance that the given indexer is running at a constant duration.
We need to somehow filter out these duplicate metrics. Reseting the metric to 0 on error/skip doesn’t work as it will be reset almost instantly after a successful run, and because Grafana scrapes infrequently, it is likely that the actual successful metric will be missed.
The text was updated successfully, but these errors were encountered:
This PR migrates the `EXECUTION_DURATION` to `Histogram` from `Gauge`.
With `Gauge`s, the previously recorded metric value will continue to be
scraped creating a flat-line graph in Grafana. Histograms allow us to
better approximate the metric over a specific time range, removing these
flat-lines.
Resolves#208
Description
The EXECUTION_DURATION is written only after the indexer succeeds, this means that when it is not running, or erroring, the last successful duration is exposed via the /metrics endpoint. Grafana will continue to scrape this metric giving the appearance that the given indexer is running at a constant duration.
We need to somehow filter out these duplicate metrics. Reseting the metric to 0 on error/skip doesn’t work as it will be reset almost instantly after a successful run, and because Grafana scrapes infrequently, it is likely that the actual successful metric will be missed.
The text was updated successfully, but these errors were encountered: