grafana: add Loki logs section with lifecycle and logging events #12279
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: Simon Deziel <simon.deziel@canonical.com>
tomponline
approved these changes
Sep 20, 2023
@simondeziel please can you open an issue for that. |
This was referenced Sep 21, 2023
Closed
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.
Here's what it looks like
The Loki logs section is static as there is currently no way to know which LXD server generated the associated logs. I think we are missing the equivalent of a Prometheus "instance" label. I also think we'll want to enrich the
lifecycleevents eventually to havenameandprojectlabels. Those are for another day/PR however.@tomponline if/when that gets merged, I'll deal with updating the copy on Grafana's site.