Document how timestamps set in Kafka messages affect retention #30025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter.
rdner
added
docs
backport-v8.0.0
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
botelastic
bot
added
needs_team
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
cmacknz
reviewed
Jan 26, 2022
cmacknz
approved these changes
Jan 26, 2022
Co-authored-by: Craig MacKenzie <[email protected]>
mergify bot
pushed a commit
that referenced
this pull request
Jan 26, 2022
Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter. (cherry picked from commit a473d94)
mergify bot
pushed a commit
that referenced
this pull request
Jan 26, 2022
Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter. (cherry picked from commit a473d94)
mergify bot
pushed a commit
that referenced
this pull request
Jan 26, 2022
Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter. (cherry picked from commit a473d94)
rdner
added a commit
that referenced
this pull request
Jan 26, 2022
… (#30037) Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter. (cherry picked from commit a473d94) Co-authored-by: Denis Rechkunov <[email protected]>
rdner
added a commit
that referenced
this pull request
Jan 26, 2022
… (#30036) Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter. (cherry picked from commit a473d94) Co-authored-by: Denis Rechkunov <[email protected]>
rdner
added a commit
that referenced
this pull request
Jan 26, 2022
… (#30035) Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter. (cherry picked from commit a473d94) Co-authored-by: Denis Rechkunov <[email protected]>
yashtewari
pushed a commit
to build-security/beats
that referenced
this pull request
Jan 30, 2022
…ic#30025) Some customers find the default behavior when using Kafka outputs unexpected.There are 2 possible options: 1. Message timestamp to be assigned on event creation (in beats), when the actual event was emitted and then propagated to Kafka 2. Message timestamp to be assigned when Kafka actually receives the message Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's worth to document how to switch between the 2 options in Kafka configuration using the `log.message.timestamp.type` parameter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Adds an important note to the Kafka output documentation.
Why is it important?
Some customers find the default behavior when using Kafka outputs
unexpected.There are 2 possible options:
message
Since beats always set the message timestamp for Kafka version 0.10.0.0+ it's
worth to document how to switch between the 2 options in Kafka
configuration using the
log.message.timestamp.typeparameter.