Filippo Giunchedi

I can echo the request, and would also like to see this feature (or suggestions on how to do achieve it if already possible!)

@prymitive I'm interested in working on this as we have multiple receivers and the dashboard is getting confusing pretty fast now. I'd like some guidance on what do you think...

Here's what I came up with as a possible solution: * Extend `receivers` configuration with sth like `strip_if_duplicated`, it is a list of receiver names * Semantics are similar to...

Thank you for your ideas and input @craized ! I agree that merging receivers is more intuitive, though as far as I can see it would be a more invasive...

Please see #5144, the same issue is tracked there

Definitely +1 to a common `tls` configuration object! Somewhat related, I proposed to client authentication to `socket_server` in #2294 and common `tls` handling would have definitely helped there.

With a little more logs, still an issue though AFAICS ``` Feb 15 12:34:24 titan2001 thanos-compact[924]: level=info ts=2024-02-15T12:34:24.841167079Z caller=compact.go:1005 group="0@{prometheus=\"k8s\", replica=\"a\", site=\"eqiad\"}" groupKey=0@12299621920028672149 msg="compaction available and planned; downloading blocks" plan="[01HPNBA4N2H37RG1GDQWA2K6MJ...

I would normally take a pprof dump of what goroutines are active to understand better the problem, in this case though the http server has shutdown already. Any pointers/ideas on...

I like the `--check` and looking at exit code idea! Would make it easy to run e.g. in CI across mcrouter versions to detect regressions.

Hello, I found this issue while investigating why `repeat_interval` is seemingly not honored, e.g. this is at the top route in alertmanager configuration: ``` - match: alertname: 'SystemdUnitFailed' repeat_interval: 24h...