-
Notifications
You must be signed in to change notification settings - Fork 289
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
Update prometheus message format #966
Conversation
@mszostok tested locally, and it works 🚀 |
Source: %s | ||
Alert Name: %s | ||
State: %s | ||
|
||
Description: |
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.
What would happen if we used bold for keys? Like:
Source: %s | |
Alert Name: %s | |
State: %s | |
Description: | |
*Source:* %s | |
*Alert Name:* %s | |
*State:* %s | |
*Description:* |
I suspect you already thought of this, and such formatting is not handled correctly in all comm platforms, correct?
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.
@pkosiec it becomes bold
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.
On Slack and probably Discord + Mattermost yes, but not sure about MS Teams 🤔 I know @mszostok knows a few caveats about MS Teams, that's why I asked 😄 But hopefully we can apply the bold 🤞
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.
So the problem is that Slack uses single *
where others uses double **
for bold statements :( only ` is common.
Thanks guys, I answered your comments, please take a look once again :) |
Description
Changes proposed in this pull request: