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
{{ message }}
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.
Prometheus currently has no downsampling support. It can be achived via federation, but it's way too messy.
Maybe now it is possible to integrate downsampling support into compaction process?
Another usefull feature would be to have different ttl for different metrics.
For example in our setup, a lot of metrics are aggregated via recording rules, and after "recording" they are never queried again.
The text was updated successfully, but these errors were encountered:
The new storage certainly makes it easy to add such things to the compaction process. Same with dynamic retention policies. Both have been thought about and are somewhat semi-planned either as a core feature or potentially by an external process.
On requirement for downsampling to work properly is staleness handling, which we luckily started working on just recently.
Prometheus currently has no downsampling support. It can be achived via federation, but it's way too messy.
Maybe now it is possible to integrate downsampling support into compaction process?
Another usefull feature would be to have different ttl for different metrics.
For example in our setup, a lot of metrics are aggregated via recording rules, and after "recording" they are never queried again.
The text was updated successfully, but these errors were encountered: