#Data retention with prometheus
1 messages · Page 1 of 1 (latest)
hi @inner minnow Prometheus's default data retention can be found at runtime via http://:9090$prom-ip/status
unless it was changed, the compose workflow should be 15d
in terms of long term retention perhaps this is the thread you were thinking of? https://github.com/NetApp/harvest/discussions/619
Currently I set up 90d via prom-stack.yml, I'll read further the above discussion, thanks
To avoid Prometheus from collecting the same counters repeatedly, you can adjust the scrape_interval parameter in this file: https://github.com/NetApp/harvest/blob/main/container/prometheus/prometheus.yml#L2. It is recommended to increase the duration to be less than a minute (since the performance counter poll schedule is one minute). This way, you can reduce the frequency of data scraping and improve the efficiency of Prometheus.
@vagrant spindle you mean to increase scrape_interval, or decrease? Default is 1m if I'm right