Skip to content

Commit 8edb5a1

Browse files
Lower kafka_consumer highwater offset warning to debug (#23388)
* Lower highwater offset warning to debug in kafka_consumer The warning fires routinely during leader failover, which is a transient condition handled by the subsequent check run. Lowering to debug avoids noisy agent logs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Rename changelog fragment to match PR number Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 5264ac2 commit 8edb5a1

2 files changed

Lines changed: 2 additions & 1 deletion

File tree

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Lower log level from WARN to DEBUG for the message emitted when a consumer group has offsets for a partition but no stored highwater offset (typically during leader failover).

kafka_consumer/datadog_checks/kafka_consumer/kafka_consumer.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -325,7 +325,7 @@ def report_consumer_offsets_and_lag(
325325
reported_contexts += 1
326326

327327
if (topic, partition) not in highwater_offsets:
328-
self.log.warning(
328+
self.log.debug(
329329
"Consumer group: %s has offsets for topic: %s partition: %s, "
330330
"but no stored highwater offset (likely the partition is in the middle of leader failover) "
331331
"so cannot calculate consumer lag.",

0 commit comments

Comments
 (0)