You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(kafkajs): include kafka_cluster_id in DSM backlog offset tracking (#7569)
* fix(kafkajs): include kafka_cluster_id in DSM backlog offset tracking
DSM checkpoints correctly included kafka_cluster_id in edge tags, but
the backlog/offset tracking (which feeds lag metrics like
data_streams.kafka.lag_messages and data_streams.kafka.lag_seconds) did
not. This caused cross-cluster offset mixing when the same topic exists
on multiple Kafka clusters, producing wildly incorrect lag values.
Thread clusterId through to setOffset calls for both producer and
consumer commit paths so that backlog entries are scoped per cluster.
DSMON-1226
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test(kafkajs): add comments explaining clusterIdAvailable version guard
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test(kafkajs): remove irrelevant comment from getDsmPathwayHash
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(kafkajs): add comment explaining resolvedClusterId safety
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
0 commit comments