Update elastic-agent-logging.md with right calculation details for disk sizing #4483
+1
−1
Conversation
This file contains 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
The calculation of the amount of disk had a small mistake on line 70. Changed: ``` 210Mb (20Mb x 7 + 10Mb x 7 = 210Mb) ```
|
This pull request does not have a backport label. Could you fix it @e-parth-pathak? 🙏
NOTE: |
lucabelluccini
added
backport-v8.6.0
|
belimawr
approved these changes
Mar 26, 2024
AndersonQ
approved these changes
Mar 27, 2024
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.
While researching for a case I noticed that there might have been a typo mistake here where the calculation of the default disk size required for the Elastic Agent's log files was explained.
What does this PR do?
Why is it important?
Right calculation of the defaults would be necessary to set the right expectations.