You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BCDA-8777: Update alert destinations for workflows and lambdas (#1175)
## 🎫 Ticket
https://jira.cms.gov/browse/BCDA-8777
## 🛠 Changes
**Admin Lambdas:**
- Updated slack alerts to be triggered in the `handle` function
- All status updates will go to operations channel
**Workflows**:
- Deploy related workflows have had destination channels updated to
deploy channel
**General**:
- Added slack utils package and constants for slack messages to reduce
duplicate code
## ℹ️ Context
Alerting channels are currently getting status and informational
messages that don't pertain to alerts. To better manage alerts and
critical infrastructure related monitoring, our alerting channel should
be free of messages that do not indicate an issue. Deploy related
updates will only be in the deploy channel and admin lambdas will report
status updates to the operations channel, including run failures, since
those are expected.
<!-- If any of the following security implications apply, this PR must
not be merged without Stephen Walter's approval. Explain in this section
and add @SJWalter11 as a reviewer.
- Adds a new software dependency or dependencies.
- Modifies or invalidates one or more of our security controls.
- Stores or transmits data that was not stored or transmitted before.
- Requires additional review of security implications for other reasons.
-->
## 🧪 Validation
Integration tests are passing, workflows in expected channels. Looking
to verify:
- lambdas that run on a schedule (non-admin) route failures to the
alerts channel but route success to operations
- admin lambdas route all statuses to operations
- deploy workflows and related workflows route only to deploy channel
- `Starting..` messages removed to reduce noise
0 commit comments