Alerting: Display alert's 'Created' time in local time instead of UTC #54414
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: Michael Musenbrock <michael.musenbrock@gmail.com>
VikaCep
approved these changes
Sep 5, 2022
peterholmberg
approved these changes
Sep 5, 2022
|
Thanks for your contribution @mmusenbr 🎉 |
mmusenbr
deleted the
bugfix/unified_alerting_alert_created_at_timezone
branch
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.
This change displays the 'Created' time of an firing alert in the local browser time instead of UTC. This helps the user to better correlate the displayed information (firing for and the local time) shown in the new alerting rule view (/alerting/list) and in the the alert details (/alerting/grafana//view).
Fixes #54413