Why thanos ruler needs to send TSDB blocks to remote storage #3996
-
|
The receiver pushes TSDB blocks to remote storage already, why do we need ruler to ship TSDB blocks to remote location. How ruler shipped block is different from receiver shipped block. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The TSDB blocks generated from receivers contain samples sent by other clients via remote write. And the TSDB blocks generated by the ruler contain samples generated from the ruler itself. So if you want to persist the metrics generated by the ruler for a longer time, you have to upload them to the remote storage. But you are right, we are currently working on a stateless ruler which leverages the Thanos receiver for Ruler storage. Please take a look at https://thanos.io/tip/proposals/202005_scalable-rule-storage.md/. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @yeya24. |
Beta Was this translation helpful? Give feedback.
The TSDB blocks generated from receivers contain samples sent by other clients via remote write. And the TSDB blocks generated by the ruler contain samples generated from the ruler itself.
If you have alerting rules, the ruler creates two metrics
ALERTSandALERTS_FOR_STATEfor the current alert status. If you have recording rules, the ruler evaluates the recording rules and generates new metrics. So that's what its TSDB blocks for.So if you want to persist the metrics generated by the ruler for a longer time, you …