search

ministryofjustice / cloud-platform

Documentation on the MoJ cloud platform
MIT License
87 stars 44 forks source link

New alert routes in alertmanager for legacy-replacement-alerts and legacy-replacement-alerts-non-prod #5362

Closed ldlharper closed 6 months ago

ldlharper commented 7 months ago

Service name

hmpps-adjustments hmpps-adjustments-api hmpps-unused-deductions-listener calculate-release-dates-api calculate-release-dates hmpps-custody-manager-api hmpps-custody-manager-ui

Service environment

Problem description

We would like two new alert severities, legacy-replacement-alerts and legacy-replacements-alerts-non-prod. The slack channels are #legacy-replacement-alerts and #legacy-replacements-alerts-non-prod

I've created secrets containing the webhook URL within hmpps-adjustments-dev for legacy-replacements-alerts-non-prod and hmpps-adjustments-prod for legacy-replacement-alert.

Contact person

Luke Harper luke.harper@digital.justice.co.uk

tmahmood72 commented 7 months ago

The non-prod Alertmanager route is created with severity legacy-replacements-alerts-non-prod

tmahmood72 commented 7 months ago

The Prod Alertmanager route is created with severity legacy-replacements-alerts

ldlharper commented 7 months ago

Thanks for implementing this. I've managed to get alerts through to the non-prod channel. But its not seeming to work for the prod channel.

I think I've been inconsistent with the channel and severity names. They should be #legacy-replacement-alerts-non-prod and #legacy-replacement-alerts (no 's' on the end of replacement).

tmahmood72 commented 7 months ago

Hi Luke,

I have made the severity and slack channel changes as requested, so please can you check the alerts are coming through to both channels.

Thanks