Thanos allow data selection for cold data via store component (selector.relabel-config)
But there is no alertnative for the hot data, there is no --selector.relabel-config option for query/sidecar/receiver
It is not possible to do tenant partitionning for hot data
Could you think about it ?
This feature would be an alternative to enforce label with prom-label-proxy
The use case is to allow a narrow view of datas, for a specific team, in grafana without having to configure multi remote write with tenants as teams, etc...
Thanos allow data selection for cold data via store component (selector.relabel-config) But there is no alertnative for the hot data, there is no --selector.relabel-config option for query/sidecar/receiver It is not possible to do tenant partitionning for hot data Could you think about it ?
This feature would be an alternative to enforce label with prom-label-proxy
The use case is to allow a narrow view of datas, for a specific team, in grafana without having to configure multi remote write with tenants as teams, etc...