Improved Kafka and RabbitMQ Functionality #353
Merged
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
nikostoulas
requested review from
jgerbe,
klesgidis,
kzacharakis,
nikosd23 and
stavros-wb
as code owners
nikostoulas
force-pushed
the
kafka_propagated_logs
branch
from
09e5731 to
d1a78b4
Compare
manoskouvarakis
approved these changes
Dec 1, 2023
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.
Description
This pull request includes several updates aimed at enhancing the functionality of Kafka and RabbitMQ. The changes include the deprecation of a Kafka function, propagation of headers in Kafka messages, updates to the examples configuration, and modifications to the logTracer and rabbitmq initializer functions.
Changes
kafka send messagein favor ofkafka.producer.sendlogTracerfunction to return an empty string instead of undefinedrabbitmq initializerto returnoriginalTryHandlecall