Hi Dmitry, Since alert labelling has the same configuration as target relabelling, you should put an example data point & relabelling rules into PromLab's amazing relabeller tool <https://relabeler.promlabs.com/>. It will show you exactly what is happening to each label and in what order.
Best, Ian On Thu, Jun 17, 2021 at 9:00 AM Dmitry Kundo <[email protected]> wrote: > Hi all, > > I generate alerts from EC2 instances using metrics reported by node > exporter. > For some EC2 instances, which are tagged with "low_priority_alerts: 1" > tag, I'd like reduce the alert severity. > To achieve this I'm trying to make use of the 'alert_relabel_configs', > like this: > > alert_relabel_configs: > - source_labels: [ low_priority_alerts ] > regex: 1 > target_label: severity > replacement: info > > But it seems to have no effect, and the alerts are still reported with the > original severity of 'error'. > Am I using it right? > Is there another possibility to achieve what I want? > > -- > 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/cbf49574-0f81-46af-a0aa-1fa003492c6fn%40googlegroups.com > <https://groups.google.com/d/msgid/prometheus-users/cbf49574-0f81-46af-a0aa-1fa003492c6fn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CADoMBNXgfPnJh-4zaRRJdXSHT8T7oQG14HwHxQWZEab7iR%3DQxw%40mail.gmail.com.
