Feature summary (what you would like to be able to do and where):
Frequently the web team often gets alerts for errors in banners related to newly deployed banners. To save the web team unnecessarily investigating these error spikes it would be helpful for banner errors to be logged into a separate channel.
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
- I received an email alert today.
- I dropped everything to investigate
- From several stack traces I realized it was a banner.
Benefits (why should this be implemented?):
- It's low effort to do this
- The web team doesn't unnecessarily get notified about potential errors in software
- The fundraising tech team does not get pinged about banners that do not relate to fundraising campaigns.
- The fundraising team can monitor errors themselves without needing web team.