feat(alerts): configure alerts for payment wallet ingestion #2608
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
infantesimone
requested changes
Nov 26, 2024
CianoDanilo
reviewed
Nov 27, 2024
CianoDanilo
previously approved these changes
Nov 28, 2024
infantesimone
previously approved these changes
Nov 29, 2024
|
Apply on hold: alerts will be activated once rollout in production have been completed |
infantesimone
dismissed stale reviews from CianoDanilo and themself
via
d5dbbb6
infantesimone
approved these changes
Dec 17, 2024
|
🎉 This PR is included in version 1.324.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List of changes
Add alerts to monitor:
Motivation and context
Those alerts will monitor payment wallet ingestion dedicated queues checking that onboarded wallet events are processed and sent to data-lake dedicated event hub.
Those events are not linked to opsgenie since they have not to be linked to the on-call system and any eventual ingestion problem will be taken into account during working hours
Type of changes
Does this introduce a change to production resources with possible user impact?
Does this introduce an unwanted change on infrastructure? Check terraform plan execution result
Other information
If PR is partially applied, why? (reserved to mantainers)