
global:
scrape_interval: 1m
scrape_timeout: 10s
evaluation_interval: 1m
external_labels:
prometheus: monitoring/k8s
alerting:
alert_relabel_configs:
- separator: ;
regex: prometheus_replica
replacement: $1
action: labeldrop
rule_files:
- /etc/prometheus/rules/prometheus-k8s-rulefiles-0/*.yaml
remote_read:
- url: http://data-influxdb.tick:8086/api/v1/prom/read?db=monitoringdb&rp=rp_1h&u=<user>&p=<pass>=
remote_timeout: 1m
read_recent: true
.png?part=0.2&view=1)
For example, even with the read_recent: true, when a certain time-series has stopped being appended in remote_storage, Prometheus(the one which remote_reads) is still able to return the result at least for 5 to 6 minutes later. The last point for below time-series is ~5 minutes old in influxDB but it still shows up in Prometheus.
This is expected. When you query Prometheus for the current value
of a metric it will actually look back up to five minutes to find
it. After this point the time series is marked as stale. This is
because it is pretty unlikely that a scrape will fall exactly
"now", and could have last been scraped several minutes ago.
-- Stuart Clark