Proposed Feature: NO_COLOR console or logfile output #878
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.
Trunk Recorder extensively uses ANSI color codes in logging statements to make the console output easier to read, but users should be able to disable them if desired.
Additionally, this behavior can create issues when combined with the
logFile
option, as the raw escape sequences may make the output difficult to parse or ingest (example below).Proposed is a
logColor
setting to selectively disable color output to logfiles and/or the console.logFile
.NO_COLOR
environment variable. If the environment variable is set (and not NULL), it will disable color output to both the console and logfiles without needing to alter the config.json.logColor
is used in the config.json, that value will override the presence of theNO_COLOR
env var. Per no-color.org recommendations, this is the desired behavior.Attached below is an example of the default setting, showing the simultaneous output of the console and logfiles. The color codes have been automatically removed from the logfiles without the use of additional tools or commands.