GH-2505: Use Correct Brokers for Cluster Id #2514
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
Resolves spring-projects#2505 When observation is enabled, we use the context's `KafkaAdmin`, if present, to determine the cluster id. The context's admin may be configured with different bootstrap servers than the producer/consumer (e.g. in Spring Cloud Stream). When looking up the cluster id for observation, use the appropriate bootstrap servers for the component.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves #2505
When observation is enabled, we use the context's
KafkaAdmin, if present, to determine the cluster id.The context's admin may be configured with different bootstrap servers than the producer/consumer (e.g. in Spring Cloud Stream).
When looking up the cluster id for observation, use the appropriate bootstrap servers for the component.