This repository has been archived by the owner on Jun 28, 2023. It is now read-only.
config.sample.yaml: alertmanager: update example (text|html)_template #368
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
Signed-off-by: Tom Herbers <mail@tomherbers.de>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I've updated the
(text|html)_templatewithin in the sample config file and made the following changes:info: it's blue and probably quite common (hoewer other's might usenonebut that should be a easy fix for them)FIRING -prefix: With limited space in Pop-ups i think the first few characters are too important as to waste them with kinda redundant information.[RESOLVED]and everthing else should be enough to distinguish between a firing alert and a resolved one.Since it's only an example config i don't really see an issue with changing it. As long as others agree that my version is better. ;)