Thanks for the update Brian. I tried your suggestion but that didn't work 
as alertmanager failed to start and I had to revert to the working state. 
The version of my alertmanager is 
Build* 2.18.1 *and thinking this might be the problem. Any ideas??

On Friday, 28 January 2022 at 00:59:16 UTC-8 Brian Candler wrote:

> Thanks for the update.  A couple of minor notes:
>
>  - match_re:
>       instance: ~"A1,B2"  #This is to include email-it in all alerts for 
> multiple instances A1 and B2
>
> Are you sure that's right?  I think it should be
>
>  - match_re:
>       instance: A1|B2
>
> Note that if you want to include alerts of *all* severity, then you don't 
> need the "severity: critical|warning|high" condition.  Just leave it out.  
> Then you will match all alerts regardless of severity (even no severity 
> set).
>
> Incidentally, there's a new matcher 
> <https://prometheus.io/docs/alerting/latest/configuration/#matcher> 
> syntax which is more like normal PromQL label matching:
>
>  - matchers:
>      - 'instance =~ "A1|B2"'
>
> match and match_re are deprecated in favour of this, although I don't 
> expect they'll be removed for a long time, if ever.
>
> On Thursday, 27 January 2022 at 23:13:15 UTC Ade wrote:
>
>> Sorry it took so long to get back to this but wanted to update the group 
>> incase anyone else is facing this same issue. The below worked for me:
>>  
>> routes:
>>   - match_re:
>>       instance: ~"A1,B2"  #This is to include email-it in all alerts for 
>> multiple instances A1 and B2
>>       severity: critical|warning|high #This picks all severity i.e 
>> critical or warning or high
>>     receiver:  email-it
>>   - match_re:
>>       instance: A2 # This is to include email-de in alert for only 
>> instance A2
>>       severity: critical|warning|high
>>     receiver: email-de
>>
>> Thanks,
>> Ade
>>
>>
>> On Friday, 21 May 2021 at 09:33:04 UTC-7 [email protected] wrote:
>>
>>> Hi,
>>>
>>> I think 
>>> https://www.prometheus.io/docs/alerting/latest/configuration/#example 
>>> should help.
>>> If you don't want to receive emails to the 2 email addresses at the same 
>>> time, you have to define 2 different receivers:
>>>
>>> receivers:
>>> - name: email-it
>>>   email_configs:
>>>   - to: [email protected] <https://groups.google.com/> 
>>>     from: [email protected] <https://groups.google.com/>
>>> - name: email-de
>>>   email_configs:
>>>   - to: [email protected] <https://groups.google.com/> 
>>>     from: [email protected] <https://groups.google.com/>
>>>
>>> And then, in section "route:" > "routes:", you will have some blocks 
>>> including "match_re:" to route alerts matching some labels to the 
>>> appropriate receiver, so something like:
>>> - match_re:
>>>   instance: A1
>>>   receiver: email-it
>>> - match_re:
>>>   instance: A2
>>>   receiver: email-de
>>>
>>>
>>> Le jeudi 20 mai 2021 à 05:04:42 UTC+2, Ade a écrit :
>>>
>>>> Hello,
>>>>
>>>> I have configured my *prometheus.yml* and *alertmanager.yml* file to 
>>>> look like below but I need help with making alert manager send email 
>>>> alerts 
>>>> to different users per instance(i.e email alerts for instance A1 goes to 
>>>> only [email protected] and  instance B2 goes only to [email protected]). I 
>>>> currently have all email alert sent to  [email protected] and  
>>>> [email protected] at the same time which seem too noisy at times.
>>>>
>>>> *  prometheus.yml   *
>>>>
>>>> global:
>>>>   scrape_interval:     15s 
>>>>   evaluation_interval: 15s 
>>>>
>>>> # Alertmanager configuration
>>>> alerting:
>>>>   alertmanagers:
>>>>   - static_configs:
>>>>     - targets:
>>>>       # - alertmanager:9093
>>>>         - localhost:9093
>>>>
>>>> # Load rules once and periodically evaluate them according to the 
>>>> global 'evaluation_interval'.
>>>> rule_files:
>>>>   # - "first_rules.yml"
>>>>   # - "second_rules.yml"
>>>>     - "alert_rules.yml"
>>>> # A scrape configuration containing exactly one endpoint to scrape:
>>>> # Here it's Prometheus itself.
>>>> scrape_configs:
>>>>   # The job name is added as a label `job=<job_name>` to any timeseries 
>>>> scraped from this config.
>>>>   - job_name: 'prometheus'
>>>>
>>>>     # metrics_path defaults to '/metrics'
>>>>     # scheme defaults to 'http'.
>>>>
>>>>     static_configs:
>>>>     - targets: ['A1:9182','B2:9182'']
>>>>     
>>>>   - job_name: "ssl"
>>>>     metrics_path: /probe
>>>>     static_configs:
>>>>       - targets:
>>>>           - A1:1667
>>>>           - B2:1667
>>>>
>>>>
>>>> *alertmanager.yml*
>>>> route:
>>>>   group_by: [Alertname]
>>>>   receiver: email
>>>>   group_wait: 10s
>>>>   group_interval: 5m
>>>>   repeat_interval: 10m
>>>>
>>>> receivers:
>>>> - name: email
>>>>   email_configs:
>>>>   - to: [email protected], [email protected] 
>>>>     from: [email protected] 
>>>>
>>>> Any suggestion would be highly appreciated.
>>>>
>>>> Regards,
>>>>
>>>>
>>>>

-- 
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/877a719d-f3be-427c-be55-c87e4594f521n%40googlegroups.com.

Reply via email to