You're a life saver! Some alerts were Critical and others were critical, but the regex was looking for lowercase critical. Adjusting all the rules with the correct severities fixed the issue. Appreciate the tip!
On Friday, June 19, 2020 at 7:57:58 AM UTC-7, Christian Hoffmann wrote: > > Hi, > > On 6/19/20 8:34 AM, Romenyrr wrote: > > I've come across this issue where I'm grouping by 'alertname' but > > nothing is being grouped except for one odd group. When I click on the > > group tab and click on "Enable custom grouping" that seems to sort > > everything by 'alertname'. > > > > This grouping issue is creating an issue where I'm just getting 1 big > > alert in Opsgenie with 74 items in it. Has anyone come across this > before? > > > > 2765A9DC-B163-4D2B-A83B-07D34E71A66F.jpeg > > > > Here's the ouput of Status > Config from the Alertmanager UI > > > > | > > > > route: > > receiver: opsgenie > > routes: > > - receiver: opsgenie > > group_by: > > - alertname > > match_re: > > severity: warning|critical > > group_wait: 10s > > Can you confirm that all of your affected alerts have a severity label > of either warning or critical? > > All others will probably be handled by the default route where you don't > have a group_by config. Maybe you intended to place it there instead? > > If receiver and everything else is identical, I don't think you should > have child routes (routes:) at all. Just place it at the top-level route > instead. > > Kind regards, > Christian > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/ef04b816-8a3e-472a-848b-54a6f42353afo%40googlegroups.com.
