Julien

Yes, unless your mark the PR as draft.

We have looked at this pull request during our bug scrub. Given the lack of response, I have marked the issue as `help wanted`, and we have decided to close...

This is a sane request, I would love to see it solved. We know that there is some kind of de facto stop the world in Prometheus at that time...

> There is no stop the world in compaction - only a few places where mutexes are very briefly taken to switch out state. Compaction is an asynchronous process during...

Yes, I think that keeping blocks aligned as they are now is important, and let's have the ability to add jitter-delay to the compaction, like we do now for scrape.

This is interesting. Can you workaround the issue by taking multiple labels in input_labels and use regexes ? e.g. can you find which container is attached to which network based...

Indeed, you would need to hardcode them: ``` - source_labels: [__meta_docker_network_name,__meta_docker_container_label_prometheus_network] regex: frontend;frontend target_label: __tmp_docker_keep replacement: keep - source_labels: [__meta_docker_network_name,__meta_docker_container_label_prometheus_network] regex: backend_backend target_label: __tmp_docker_keep replacement: keep - source_labels: [__tmp_docker_keep] regex:...

okay. I think we could have a networks array where we take a list of networks. For each container, we add its target on that network. If not network is...

We could implement/explore with an alternative mode, like we do for kubernetes, where one target has the addresses over all the networks. I have tagged this issue as P3.

If we break, we should order them. We should also have one label for each network address (without port).