My feedback

1 result found

1. Alert and Notify based on Sending Metrics and Usage

   •  

   35 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   14 comments  ·  Feature Requests » New Idea  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   started  ·  AdminTravis Walton (Product Manager, Mailgun) responded

   Hello,

   
   

   As we work through ideation on an alerts feature for Mailgun, I wanted to gauge opinion on the configuration of notification channels. If out of the box, Mailgun allows for configuration of notification channels to include emails addresses, webhooks, and Slack integration where in the flow does it make most sense where the channels are defined.

   
   

   Our position is that the pattern for notification channels is created on the account level. Such that any all alerts created would use the notification channels previously defined. This would be foundational to a future state is which users could have greater control on how Mailgun communicates emergent issues (e.g. some users would like to receive domain disablement or similar notification posted to webhook rather than email).

   
   

   So, for "alert and notify based on sending metrics and usage" is there any reason Mailgun needs to have notification channels defined on a per alert basis or would an account-level, general notification preference work here?

   
   

   Thank you for your time

   
   

   Travis 

   Hello,

   
   

   As we work through ideation on an alerts feature for Mailgun, I wanted to gauge opinion on the configuration of notification channels. If out of the box, Mailgun allows for configuration of notification channels to include emails addresses, webhooks, and Slack integration where in the flow does it make most sense where the channels are defined.

   
   

   Our position is that the pattern for notification channels is created on the account level. Such that any all alerts created would use the notification channels previously defined. This would be foundational to a future state is which users could have greater control on how Mailgun communicates emergent issues (e.g. some users would like to receive domain disablement or similar notification posted to webhook rather than email).

   
   

   So, for "alert and notify based on sending metrics and usage" is there any reason Mailgun needs to have notification channels defined on a per alert… more

   An error occurred while saving the comment
   Ushir Shah commented  ·  Aug 17, 2021  ·  Delete…

   Agreed, same here. If we had received email alerts that emails were being generated at a threshold either we set or based on past history, that would have allowed us to investigate and potentially stop it. This ties with my other feature request is to have a Pause Domain feature so that if alerted, we can immediately go in and pause the domain and stop all sending until an investigation can be carried out.

   Save Submitting...
   Ushir Shah supported this idea  ·  Aug 17, 2021