[8.14](backport #39873) Add Offset to libbeat/reader.Message
#39992
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
libbeat: add Offset to libbeat/reader.Message
This commit introduces the Offset property to libbeat/reader.Message, which stores the total number of bytes read and discarded before generating the message. The Offset field allows inputs to accurately determine how much data has been read up to the message, calculated as Message.Bytes + Message.Offset.
With this new Offset field, the filestream input correctly updates its state to account for data read but discarded by the include_message parser.
Checklist
[ ] I have made corresponding changes to the documentation-~~ [ ] I have made corresponding change to the default configuration files~~
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
None
How to test this PR locally
Follow the instructions on #39653
Related issues
include_message
do not correctly track the offset of a file #39653This is an automatic backport of pull request #39873 done by [Mergify](https://mergify.com).