[8.x](backport #40775) chore: add debug histograms for s3 object size and events per processed s3 object #40819
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.
Proposed commit message
Fixes #40306 by adding
s3_events_per_object
&s3_object_size_in_bytes
histograms. These histograms provide valuable insights on the size of S3 objects filebeat processed and the number of events produced by each S3 object.Consider below screenshot,
s3_events_per_object
tracks events (logs) per object with max, min and counts3_object_size_in_bytes
tracks object size with max and min and countChecklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
s3_object_size_in_bytes
&s3_events_per_object
histogramsRelated issues
This is an automatic backport of pull request chore: add debug histograms for s3 object size and events per processed s3 object #40775 done by Mergify.