Cherry-pick #18723 to 7.x: Avoid watching monitor logs #18761
Merged
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.
Cherry-pick of PR #18723 to 7.x branch. Original message:
What does this PR do?
This PR differentiates beat for its purpose (normal/monitoring) and avoids monitoring output of monitoring beats.
It does it checking special tags passed in descriptor if tag is present it redirect logs to {original_path}_monitor file/socket so it is not picked up by monitor
Why is it important?
to lower CPU consumption and avoid publishing monitoring logs about monitored logs
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.