Repository navigation
docs: Describe how the containerdebug logs are collected - #975
Merged
Merged
Conversation
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
15 tasks done
NickLarsenNZ
reviewed
Nov 4, 2026
NickLarsenNZ
left a comment
Member
There was a problem hiding this comment.
I think a few small tweaks might be needed.
NickLarsenNZ
approved these changes
Nov 10, 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.
Description
The
Outputsection of the containerdebug page said that the collected information goes to the shared Stackable log dir for pickup by the Vector agent, without saying how that is enabled. It has in fact not happened since containerdebug 0.2.0, which no longer reads the environment variable that the operators were setting.This splits the section into pod logs, aggregated log files and state file, and documents the
FILE_LOG_DIRECTORY,FILE_LOG_ROTATION_PERIODandFILE_LOG_MAX_FILESvariables which the operators set instead. It also explains that the events carry the container namecontainerdebugalthough no container of that name exists, which path an override has to keep, and that the file log level is independent of the log configuration of the product container. The link to containerdebug now points at the crate in operator-rs, where the tool lives.Part of stackabletech/issues#909
Docs
Checklist
Author
Reviewer
Acceptance