New alert route in Alertmanager for namespaces laa-provider-details-api-dev , laa-provider-details-api-uat , laa-provider-details-api-preprod

[rajindersinghsandhu]

Service name

laa-provider-details-api

Service environment

• [X] Dev / Development
• [ ] Staging
• [ ] Prod / Production
• [ ] Other

Impact on the service

NA

Problem description

The CP guide found at https://user-guide.cloud-platform.service.justice.gov.uk/documentation/monitoring-an-app/how-to-create-alarms.html#creating-your-own-custom-alerts has been followed to establish custom alerts for the service deployed on CP. Alerts are intended to be sent to a Slack channel in the event of errors, warnings, and occasionally informational messages.

Preferably, a single non-production Slack app would be utilized to dispatch alerts to a specific channel designated for development, user acceptance testing (UAT), and pre-production environments.

namespace name : laa-provider-details-api-dev , laa-provider-details-api-uat , laa-provider-details-api-preprod team name : laa-cwa-data-api-admin-team application name : Provider Details Api slack channel : laa-provider-data-api-alerts-nonprod kubernetes secret name where the webhook url is stored : laa-provider-details-api-secrets.SLACK_WEBHOOK severity level (warning/information) : error/warning/information

Contact person

[email protected]

[timckt]

Please use severity: laa-provider-data-api-alerts-nonprod for PrometheusRule yaml file

[rajindersinghsandhu]

The integration is working successfully now. Ticket can be closed. Many Thanks @timckt for your help