Sina

@valyala I have seen your comment on multilevel vmselect [here](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1767). Do you have plans to support a similar api on vmsingle too? It ends the long running lack of promxy...

I will elaborate on the use-case and it might interest someone: The idea is to have multi zone monitoring system like in [this document](https://sre.google/sre-book/practical-alerting/#fig_borgmon_dataflow). First consider we have one giant...

I support this issue too. StatefulSet does not support changing one pod's configuration despite the stateful nature and it has been a long running thread in k8s. This really happens...

Hey @Amper ,thank you for your meticulously crafted response. > I think that it's a feature, not disadvantage 🙂 I understand your point of view but the need still exists....

We need this too. Our network treats ICMP and TCP differently. Especially sometimes packets are routed base on hash(src_ip,src_port,dst_ip,dst_port), however this does not hold for ICMP.

Actually we can use this too. We have multiple recording rules that sometimes break because of missing data. The data is not actually missing and we deliver it later somehow...

> Aha, I see. I'm asking because I'm not rly sure proposed solution by me is a good one. I'm afraid it could cause more harm by making querying complicated,...

Sorry if this comment is not specifically related to the current issue. I think this one has the best potentials and want to help the issue by providing other use-cases....