Document log aggregation via Loki #161
Merged
+115
−0
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 a page in the docs describing the installation and setup of Loki, a log aggregation system made by Grafana Labs. It has nice integration with Grafana and allows viewing realtime logs in the Explore menu and configuring "Logs" visualizations in Dashboard panels.
Motivation and Context
Log visibility can often be cumbersome, especially on multi-node systems. This allows log aggregation across nodes in a centralized location and provides an easy viewing alternative to running
docker logs -f <container>
on each container you want to view the logs for.How Has This Been Tested?
I have tested the configuration example in an isolated VM. I'm waiting to setup on the Yale system for our cooldown to be completed (tomorrow), since this requires remaking each container you want to forward logs.
Types of changes
Checklist:
develop
branch.