Open rkferreira opened 2 years ago
Hi @rkferreira Thanks for reporting this issue! Would you like to contribute your fix and/or the proposed improvement?
The reason why the metrics are getting discarded is because your scraping interval is > 30 seconds and 1 - avg by (instance) (irate(node_cpu_seconds_total{mode=\"idle\"}[1m]))
is an Prometheus iRate query requires at least 2 data points to calculate the rate.
I however agree that there should be a provision to change the duration based on your scraping interval.
Hi,
During the setup of Cruise Control using "PrometheusMetricSampler" I see on issue collecting data from AWS MSK cluster.
CC VERSION="2.5.42"
DefaultPrometheusQuerySupplier.java proposes "BROKER_CPU_UTIL" query using time range window of 1 minute, but MSK reports CPU metrics as of 5 minutes window.
The result is you always get discarded metrics due to missing BROKER_CPU_UTIL metric:
My current fix:
An improvement would be a configurable prometheus window.
Thanks, Rodrigo Kellermann Ferreira