Conversation
ValeraS
approved these changes
Jul 7, 2023
This was referenced Jul 11, 2025
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
2 participants
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.
Why might you want to configure statoscope?
Firstly, to change the
statsOptionsthat are being collected. The more you collect — the bigger the stats.json becomes.Also, you might want to use it to disable the creation of html reports — those also spend substantial amount of cpu time, especially if you use report compression, and those might not be needed for you in case you have
statoscope compare-based CI pipelineAlso, you might be using brotli instead of gzip — that is also overridable thorough config