Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create new alertmanager route for non-prod environments for multiple send-legal-mail environments/namespaces #6706

Closed
2 of 4 tasks
psoleckimoj opened this issue Jan 24, 2025 · 5 comments
Assignees

Comments

@psoleckimoj
Copy link

Service name

Visits (Send Legal Mail)

Service environment

  • Dev / Development
  • Staging
  • Prod / Production
  • Other (Preprod_)

Impact on the service

Move non-prod alerts out of prod alerts channel

Problem description

namespace name: send-legal-mail-to-prisons-dev, send-legal-mail-to-prisons-preprod
team name: [hmpps-prison-visits-booking]
application name: Multiple send-legal-mail-*
slack channel: #send-legal-mail-alerts-nonprod
kubernetes secret name where the webhook url is stored: alertmanager-nonprod-webhook
severity level (warning/information): information

Contact person

Paul Solecki, @psoleckimoj

@FolarinOyenuga
Copy link
Contributor

@psoleckimoj this ticket has now been actioned.

The custom severity levels are:

Dev: hmpps-visits-send-legal-email-dev

Preprod: hmpps-visits-send-legal-email-preprod

@FolarinOyenuga FolarinOyenuga moved this from 🏗 In Progress to 👀 Review/QA in Cloud Platform Jan 24, 2025
@psoleckimoj
Copy link
Author

Can I check they're pointing at the right channels as normally I've just had a single sev created for nonprod. Also it was just send-legal-mail not email but as long as it works that's fine.

@github-project-automation github-project-automation bot moved this from 👀 Review/QA to 🥇 Done in Cloud Platform Jan 24, 2025
@github-project-automation github-project-automation bot moved this from 🥇 Done to 🏗 In Progress in Cloud Platform Jan 24, 2025
@FolarinOyenuga
Copy link
Contributor

@psoleckimoj they should work just fine. This ticket will remain open until you confirm everything works as expected.

@FolarinOyenuga FolarinOyenuga moved this from 🏗 In Progress to 👀 Review/QA in Cloud Platform Jan 24, 2025
@psoleckimoj
Copy link
Author

TY, will get my products updated 🙂

@psoleckimoj
Copy link
Author

@FolarinOyenuga happy for you to close 👍

@FolarinOyenuga FolarinOyenuga moved this from 👀 Review/QA to 🥇 Done in Cloud Platform Jan 27, 2025
@FolarinOyenuga FolarinOyenuga closed this as completed by moving to 🥇 Done in Cloud Platform Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🥇 Done
Development

No branches or pull requests

2 participants