Dan Williams

https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.6/guide/use_cases/self_managed_lb/

I’m getting the same issue with an EKS cluster v1.25

I'm experiencing a similar issue using the following config ``` global: resolve_timeout: 5m route: receiver: default group_by: - alertname routes: - receiver: DevOutOfHours matchers: - namespace=~".+dev|.+uat" active_time_intervals: - outofhours -...

thanks for the reply, I'll give it a go. I was using the example found here https://prometheus.io/docs/alerting/latest/configuration/#example ``` # All alerts with the service=inhouse-service label match this sub-route # the...

just saw this bit `Additionally, the root node cannot have any active times.` let me try it with different subroutes

not having much luck. Shouldn't the below just route to the default receiver? It seems like the time_intervals aren't having any impact. Running it using `{ namespace="app-dev", label_team="TeamA"}` routes to...

this doesn't work either. This should route to TeamC on weekends and TeamD in office hours, but it always routes to TeamC. Are my time_intervals set correctly?? ``` global: resolve_timeout:...

i have a similar problem with time intervals. Tried using the https://prometheus.io/webtools/alerting/routing-tree-editor/ to parse it using `{ namespace="app-dev", label_team="TeamA"}` as the label set, but it always routes to TeamC when...

any progress on this?