docs: add log collection guide for VM installs - #758
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
aking13
approved these changes
Aug 25, 2026
ak684
approved these changes
Aug 25, 2026
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.
Summary of changes
Nothing in the docs tells an operator how to get logs off a VM install. The troubleshooting guide covers one-off diagnostics, so anyone who wants OHE logs flowing continuously into their own observability platform has to work out where the files live on the VM themselves.
This adds a short page under VM Install with the log locations and the steps to point an agent at them.
The page recommends a host-level log agent. It needs no kubernetes access, and a single file glob covers every service on the VM. That glob matches only the active files, so rotated logs don't get re-ingested.
I verified the paths, the permissions, and the
tailcommand in the last step against a running VM install.