Patched changelog for PR 4579 #4671
Conversation
pchila
added
Team:Elastic-Agent-Control-Plane
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
|
|
||
| # Long description; in case the summary is not enough to describe the change | ||
| # this field accommodate a description without length limits. | ||
| # NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. | ||
| #description: | ||
| description: Removing beat state metricsets reduces the document count of indices metrics-elastic_agent.*-* by 50%, saving around 13% disk space |
There was a problem hiding this comment.
Isn't the number of metrics produced dependent on the number of components running under agent? i.e. something like x document per beat per interval? so the % savings depends on the number of deployed integrations/managed beats?
We need to document which integrations we used to obtain this number and that that the savings depend on the number of inputs. More inputs = more monitoring data being written, so the total savings should be greater in terms of absolute numbers (MB) in that case.
There was a problem hiding this comment.
The numbers I got are obtained using only the system integration... Those should be replicated n times for any other component that belongs in the supported component list
The % gain should stay roughly the same though if an install is running the same integrations before and after upgrading to a version that includes this change
There was a problem hiding this comment.
Makes sense we drop the same amount of documents from every Beat
|
@pchila Can we merge this? :-) |
(cherry picked from commit 7ad2f59)
What does this PR do?
This PR patches changelog fragment for already merged PR #4579 specifying the savings coming from removal of beat state metricset
Why is it important?
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testHow to test this PR locally
Related issues
Questions to ask yourself