-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat: update alerts summary #1967
Conversation
Thank you for your interest in contributing to the Harvest project! We require contributors to sign our Corporate contributor license agreement (CCLA), and we don"t have the user(s) @7840vz on file. In order for us to review and merge your code, please follow the instructions in step 6 of creating a pull request. |
To use proper labels
@cla-bot check |
The cla-bot has been summoned, and re-checked this pull request! |
Thanks @7840vz we received the CCLA and will review. Thanks for your contribution! |
@cla-bot check |
The cla-bot has been summoned, and re-checked this pull request! |
@@ -402,7 +402,7 @@ groups: | |||
labels: | |||
severity: "error" | |||
annotations: | |||
summary: "Storage VM stop succeeded for instance uuid [{{ $labels.instuuid }}]" | |||
summary: "Storage VM stop succeeded for instance uuid [{{ $labels.inst_uuid }}]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
svm_uuid
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the original message is related to instance uuid, and I received actual messages from EMS where it is inst_uuid
not instuuid
. So unsure if svm_uuid is related to this template.
To use proper label names