Double Alerts Transport - Transport Group not Honoured

Hi All,

We have been having a strange issue for a month or so where all of our Alerts transport 2 emails. After some testing today I think it is becuase the Transport Group is not honoured;

The tool tip says - Restrict this alert to specified Trasnports.
With the following set

The alerts trasnports to OpsGenie and the system Default.

:: Transport mail => Attempting to email Alert for device gwr-mh-sslvis - P3 - Warning - Network - Processor Usage Over 99% got acknowledged to: [email protected]

:: Transport mail => Attempting to email Alert for device gwr-mh-sslvis - P3 - Warning - Network - Processor Usage Over 99% got acknowledged to: [email protected]

I have set the defaults to not copy the default contact;

If I then add the Transport Group with our default email address in again and test I get the following;

When I test, it sends twice to our default alerts address;

:: Transport mail => SQL[SELECT transport_config FROM alert_transports WHERE transport_id=? [4] 0.22ms]

Attempting to email Alert for device gwr-mh-sslvis - P3 - Warning - Network - Processor Usage Over 99% got acknowledged to: [email protected]
OKSQL[SELECT devices.*, location, lat, lng FROM devices LEFT JOIN locations ON devices.location_id=locations.id WHERE device_id = ? [85] 0.4ms]

SQL[SELECT * FROM devices_attribs WHERE device_id = ? [85] 0.22ms]

SQL[SELECT * FROM vrf_lite_cisco WHERE device_id = ? [85] 0.23ms]

SQL[INSERT IGNORE INTO eventlog (device_id,reference,type,datetime,severity,message,username) VALUES (:device_id,:reference,:type,:datetime,:severity,:message,:username) {“device_id”:85,“reference”:null,“type”:“alert”,“datetime”:“2019-03-19 20:10:28”,“severity”:1,“message”:“Issued acknowledgment for rule ‘P3 - Warning - Network - Processor Usage Over 99%’ to transport ‘mail’”,“username”:“”} 2.35ms]

:: Transport mail => SQL[SELECT transport_config FROM alert_transports WHERE transport_id=? [1] 0.2ms]

Attempting to email Alert for device gwr-mh-sslvis - P3 - Warning - Network - Processor Usage Over 99% got acknowledged to: [email protected]
OKSQL[INSERT IGNORE INTO eventlog (device_id,reference,type,datetime,severity,message,username) VALUES (:device_id,:reference,:type,:datetime,:severity,:message,:username) {“device_id”:85,“reference”:null,“type”:“alert”,“datetime”:“2019-03-19 20:10:28”,“severity”:1,“message”:“Issued acknowledgment for rule ‘P3 - Warning - Network - Processor Usage Over 99%’ to transport ‘mail’”,“username”:“”} 1.7ms]

:: Transport msteams => SQL[SELECT transport_config FROM alert_transports WHERE transport_id=? [2] 0.2ms]

OKSQL[INSERT IGNORE INTO eventlog (device_id,reference,type,datetime,severity,message,username) VALUES (:device_id,:reference,:type,:datetime,:severity,:message,:username) {“device_id”:85,“reference”:null,“type”:“alert”,“datetime”:“2019-03-19 20:10:28”,“severity”:1,“message”:“Issued acknowledgment for rule ‘P3 - Warning - Network - Processor Usage Over 99%’ to transport ‘msteams’”,“username”:“”} 2.17ms]

:: Transport mail => Attempting to email Alert for device gwr-mh-sslvis - P3 - Warning - Network - Processor Usage Over 99% got acknowledged to: [email protected]
OKSQL[INSERT IGNORE INTO eventlog (device_id,reference,type,datetime,severity,message,username) VALUES (:device_id,:reference,:type,:datetime,:severity,:message,:username) {“device_id”:85,“reference”:null,“type”:“alert”,“datetime”:“2019-03-19 20:10:28”,“severity”:1,“message”:“Issued acknowledgment for rule ‘P3 - Warning - Network - Processor Usage Over 99%’ to transport ‘mail’”,“username”:“”} 2.05ms]

All I can think is that it ignores the Transport group settings and sends to the System Default and the configured group.

Any idea why this is. It hasn’t always done this.

The email transport has a known bug right now where it cannot de-duplicate emails. If a user is listed twice, they will get two emails.

Been trying to rework it to do that, but it is a nightmare right now.

Hi Murrant.

Thanks for the confirmation.

Duncan