0
Vote

To many email Alerts...

We get way to many email Alerts which is causing a lot of noise. Unfortunately due to that no one is paying attention to it anymore.
Is there a way to reduce the noise?

Comments 1 comment
  • Hi Rick,

    here are a couple bullet points you can follow to better manage your email settings and when you receive Alerts:

    • Check subscriptions across keys, and verify that the email alert settings suit your needs (see: Managing Alerts)
    • Remove irrelevant alerts by creating custom Views based on event types (such as Uncaught/Swallowed Exceptions), specific applications or packages for which they are responsible.
    • Determine which other communication channels are preferable to your workflow. Example slack, Jira, others.
      Explore if you can use visualization tool as a better option to handle some type of issues vs email.
    • Determine where is the noise generated. Blacklist the packages or libraries that may create a lot of noise, but don’t necessarily find relevant events.
    • Hide events that require no action or are used for flow control.
    • What is irrelevant about these alerts? Is it important to see new events, spikes in activity, or anomalies? Cover the relevant feature sets for these.
    • Determine the workflow. If OverOps is used as a part of the testing process, use “Introduced By” deployments is a big feature to cover here.
    • How are your keys set up? Is noise merely being unable to distinguish between critical production errors and a backlog of development errors? Make sure that they are splitting up keys by environment or another practical manner and not lumping them all in the same OverOps dashboard. This could also be done with custom views.
    • Have the opposite problem/not getting anything from OverOps? Check to make sure that we are not hitting the spam folder and are whitelisted.

     

    I hope these give you a couple ideas where to start and reduce the noise.

Please sign in to leave a comment.

Join conversation