-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: allow tracking kafka produce and consume offsets #18
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.
Are we testing both cases of the upsert here? 🤔 Do we need to? :D
Co-authored-by: Matt Sutkowski <msutkowski@gmail.com>
Co-authored-by: Matt Sutkowski <msutkowski@gmail.com>
I am not testing both, and 🤷 maybe. I figured I would test this on a project before release |
@msutkowski Alright, looking at the code again, I assert the second upsert case at the end of the test. We should be good to merge. |
🤖 I have created a release *beep* *boop* --- ## [1.2.0](v1.1.2...v1.2.0) (2023-07-10) ### Features * allow tracking kafka produce and consume offsets ([#18](#18)) ([ebab69b](ebab69b)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This was the one remaining feature from the golang library that I haven't ported yet. Now it's done. It allows tracking Kafka offsets. Datadog uses this to detect lag and consumers that are offline and not reporting.
After every publish, we push the last offset to Datadog. After every consume, we push the last read offset to Datadog. It can then calculate the offset and alert us on issues.