Kafka source: add metrics to track connector performance #778
Assignees
Labels
enhancement
New feature or request
Comments
sravotto
added a commit
that referenced
this issue
Apr 16, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
sravotto
added a commit
that referenced
this issue
Apr 22, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
sravotto
added a commit
that referenced
this issue
Apr 22, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
sravotto
added a commit
that referenced
this issue
Apr 30, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
sravotto
added a commit
that referenced
this issue
Apr 30, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
sravotto
added a commit
that referenced
this issue
Apr 30, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
sravotto
added a commit
that referenced
this issue
Apr 30, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 30, 2024
This change improves the logic to find an adequate offset to start the event replay. We return the offset of the most recent resolved timestamp message that is stricly less than the minimum timestamp provided by the user. A new set of metrics have been added to track the total number of messages that have been replayed, and the number of messages read to find the resolved timestamp. A new mock client and consumer have been introduced to facilitate testing. Fixes #779, #778.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: