Update config to reflect degrade_on_partial
#6640
Open
+70
−0
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.
elastic/beats#42160 added the ability to mark metricset as degraded when partial metrics are encountered. As per this discussion, it didn't really make sense to document this behaviour on beats repo, as this option is only usable while running elastic-agent.
Until now, we weren't marking metricsets as degraded due to various hidden bugs encountered and CI failures on agent.
The plan is to enable this in agent integration test cases in elastic-agent. Once we're confident enough, we will enable this feature by default in beats and eventually, remove the flag.
This PR updates the reference file with the necessary information about the config.
Simultaneously, I've opened a PR to update system integration to reflect the changes on UI.