Revert "[Fleet] Improve validation for dynamic Kafka topics" #219415
Merged
Conversation
This file contains hidden or 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
This reverts commit 5903c7a.
kpollich
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
kpollich
added
release_note:skip
nchaulet
approved these changes
Apr 28, 2025
|
Correct this feature was only ever in 9.1.0. |
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Async chunks
Page load bundle
cc @kpollich |
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
May 29, 2025
…#219415) Reverts elastic#212422 We don't want to surface this Beats-specific syntax for dynamic topics because it greatly harms our ability to migrate users to OTel. The recommended way to handle complex multi-field interpolations for topic names is to use an `add_field` Beats processor to add the desired topic name as a distinct field, and then use that field for the dynamic topic name in the Fleet-managed Kafka output. I'll be filing a docs issue to get this in our public docs as well.
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.
Reverts #212422
We don't want to surface this Beats-specific syntax for dynamic topics because it greatly harms our ability to migrate users to OTel.
The recommended way to handle complex multi-field interpolations for topic names is to use an
add_fieldBeats processor to add the desired topic name as a distinct field, and then use that field for the dynamic topic name in the Fleet-managed Kafka output. I'll be filing a docs issue to get this in our public docs as well.