-
Notifications
You must be signed in to change notification settings - Fork 666
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
Delivery report from events channel does not have timestamp and headers #425
Comments
I also set metadata in headers and would like to know the delivery result from headers. @edenhill |
@silencev Sorry, timestamps and headers are not available in the delivery report. You can pass a user object of your choice with each produced message which you can retrieve in the delivery report, you can use that to measure latency, et.al. In librdkafka there's a |
@edenhill Can you explain what do you mean by "user object" ? Are you referring to |
@nandak522 and @jasimsulaiman This is an old issue, but I added the producer latency into this PR. Unless there's a better method of getting the ProducerLatency that can circumvent this. |
Description
Delivery report of message from events channel, when using channel producer does not have timestamp or headers. This behavior is same for successfully delivered, as well as on timeout on failure to deliver to kafka.
Not having headers makes it very hard to identify which message failed.
How to reproduce
Send message with timestamp:
Checklist
Please provide the following information:
LibraryVersion()
): confluent-kafka-go:v1.3.0, librdkafka-1.3.0-r0ConfigMap{...}
kafka.ConfigMap{"bootstrap.servers": serverIp, "broker.version.fallback": "2.1.1", "message.timeout.ms": "1000", "api.version.request": true}
alpine:3.11
"debug": ".."
as necessary)code:
log:
2020/02/02 14:58:46 mes t: 0001-01-01 00:00:00 +0000 UTC
The text was updated successfully, but these errors were encountered: