Spike: report #cms-notifications alerts into their own targeted channels

[timcosgrove]

User Story or Problem Statement

CMS-related alerts should go into dedicated channels in addition to the #cms-notifications channel, so that CMS Support and Devops engineers can quickly become aware of and respond to problems with CMS-related systems.

Description or Additional Context

The utility & specifics of this ticket will be evaluated in the context of UX-based recommendations re: notifications.

#cms-notifications is a hard channel to follow because of the wide variety of information posted there, which is of varying levels of urgency. It would be helpful to have channels specifically dedicated to alerts about specific systems so that Support and Devops can more readily see and respond to problems.

This would not replace #cms-notifications; that channel is used by a number of people as a single location to keep abreast of CMS-related information.

The work of the UX spike will inform this work.

Steps for Implementation

Acceptance Criteria

• #cms-notifications alerts and information are assessed for type of alert, origin, level of urgency
• Channels are created for each type or system that creates alerts
• The systems that are reporting into #cms-notifications are updated to also report into a more specific channel
• Requires UX review