-
Notifications
You must be signed in to change notification settings - Fork 74
Reduce Kafka per event logging to debug and include Kafka offset #3285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR reduces per-event Kafka logging to debug level and enriches spans with the Kafka offset for better traceability.
- Lower per-message logs to
debug
and includemessaging.kafka.offset
- Add
#[instrument]
todispatch_kafka_event
andtopic_partition_queue_consumption_loop
- Simplify consumer task logging by removing
info_span
and using structureddebug!
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
crates/ingress-kafka/src/dispatcher.rs | Updated import, added #[instrument(level = "debug", …)] to include offset |
crates/ingress-kafka/src/consumer_task.rs | Switched from info_span to debug! , added instrumentation on loop, trimmed fields |
…ontroller This PR changes how the ClusterController learns about alive/dead nodes. Now it uses the restate_core::cluster_state::ClusterState to update the ObservedClusterState which is used by the LogsController and the Scheduler. As part of this commit, we hide the implementation details of the ObservedClusterState to allow for easier evolutions of it. Moreover, it simplifies the error handling of the LogsController by panicking if the loglet params cannot be parsed because it is a situation from which the Restate server cannot recover until the metadata gets fixed.
This commit improves a little bit the logging we do when consuming from Kafka. It reduces the per event log level to debug and includes the Kafka offset in spans/events for easier correlation what is being read.
e30634f
to
397ab7d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only question/ask for this review is if this changes how the trace looks on user tracing jaeger, if you verified it or idk.
I didn't verify it. Will do so and post a screenshot of the traces. |
This commit improves a little bit the logging we do when consuming from Kafka. It reduces the per event log level to debug and includes the Kafka offset in spans/events for easier correlation what is being read.