ui: Markdown timestamp support #3558
Merged
Conversation
This file contains hidden or 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
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.
Description:
This PR adds support for timestamps in the markdown renderer.
It adds support for ISO-formatted timestamps, with or without sub-second precision, as well as UNIX date-formatted timestamps (like those used for heartbeat timeouts).
2006-01-02T15:04:05.999999999Z2006-01-02T15:04:05.99999999907:002006-01-02T15:04:05ZMon Jan 2 15:04:05 MST 2006Timestamps will be underlined and always converted to the users local timezone and can be clicked to copy the ISO-formatted string for use in filters, SQL queries, other systems, etc..
Which issue(s) this PR fixes:
Closes #2834
Screenshots:
Describe any introduced user-facing changes:
Timestamps in any markdown document, including alert details, will be automatically detected and converted to local time.
Describe any introduced API changes:
N/A