[Platform] Fix regression with backup failure email #6461
Assignees
Labels
area/platform
Yugabyte Platform
Comments
daniel-yb
added a commit
that referenced
this issue
Nov 24, 2020
Summary: When implementing replication lag alerting, I caused a regression with backup failure alerting. Need to fix field names in the alert payload. @CNarang noticed that emails weren't being sent when testing this feature on 2.5.1. Tested the feature on his installation of the platform and saw ``` Invalid alert_info_json ``` being logged for cluster_health.py when running it manually with the logged payload from the platform. This should resolve the issue. Test Plan: Test backup failure alert Reviewers: arnav, wesley, sanketh Reviewed By: sanketh Subscribers: cnarang, jenkins-bot, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D9972
daniel-yb
added a commit
that referenced
this issue
Dec 5, 2020
Summary: When implementing replication lag alerting, I caused a regression with backup failure alerting. Need to fix field names in the alert payload. @CNarang noticed that emails weren't being sent when testing this feature on 2.5.1. Tested the feature on his installation of the platform and saw ``` Invalid alert_info_json ``` being logged for cluster_health.py when running it manually with the logged payload from the platform. This should resolve the issue. Test Plan: Test backup failure alert Reviewers: arnav, wesley, sanketh Reviewed By: sanketh Subscribers: cnarang, jenkins-bot, yugaware Differential Revision: https://phabricator.dev.yugabyte.com/D9972
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When implementing replication lag alerting, I caused a regression with backup failure alerting. Need to fix field names in the alert payload.
The text was updated successfully, but these errors were encountered: