Today we have a single thanos ruler instance, however it would be quite useful to be able to deploy certain recording rules with a unique external label so they are easier to find/manage/cleanup in thanos storage. The immediate use case for this is piloting recording rules using production metrics
Description
Details
Event Timeline
Change #1192209 had a related patch set uploaded (by Herron; author: Herron):
[operations/puppet@production] thanos-rule: add pilot instance
Change #1188441 had a related patch set uploaded (by Herron; author: Herron):
[operations/puppet@production] thanos-rule: add support for multiple instances
Change #1188441 merged by Herron:
[operations/puppet@production] thanos-rule: add support for multiple instances
Change #1197326 had a related patch set uploaded (by Herron; author: Herron):
[operations/alerts@master] ThanosRecordingRuleGaps: update thanos-rule to thanos-rule@main
Change #1197326 merged by jenkins-bot:
[operations/alerts@master] ThanosRecordingRuleGaps: update thanos-rule to thanos-rule@main
Change #1197669 had a related patch set uploaded (by Herron; author: Herron):
[operations/puppet@production] profile::thanos::query::store_config: add define
Change #1197669 merged by Herron:
[operations/puppet@production] profile::thanos::query::store_config: add define
Change #1192209 merged by Herron:
[operations/puppet@production] thanos-rule: add pilot instance
We now have two thanos rule instances running, "main" (the pre-existing instance) and a new instance called "pilot"
Each instance is configured to attach a unique external label recorder=thanos-rule@main, recorder=thanos-rule@pilot etc.
titan1001:~$ systemctl status thanos-rule@pilot
● thanos-rule@pilot.service - Thanos rule (instance pilot)
Loaded: loaded (/lib/systemd/system/thanos-rule@pilot.service; static)
Active: active (running) since Thu 2025-10-23 20:04:17 UTC; 41min agoI think we're good to go here!