Lots of obsolete logging when perfoming health checks

[spring-cloud]

Lots of obsolete logging when perfoming health checks

[elnur]

I'm at 1.2.0.RELEASE and still seeing all this excessive logging.

[mbogoevici]

Hi @wblancqu,

thanks for reporting this. We'll get this for our next point release. Until we get to it, as per the usual, we encourage users to contribute with any improvements they see fit :).

[ltalhouarne]

@wblancqu,

We are using the same strategy for health checking our applications.

However, I don't believe the KafkaConsumer API allows for passing the aforementioned boolean that the AbstractConfig utilizes.

In the meantime, we've decided to change the logging level for the ConsumerConfig as well as the ProducerConfig to ERROR. We lose the initial logging on boot up but our logs don't get clustered for each health check.

logging.level.org.apache.kafka.clients.consumer.ConsumerConfig=ERROR      
logging.level.org.apache.kafka.clients.producer.ProducerConfig=ERROR

[blancqua]

Hi @ltalhouarne,

Thanks for your reply. We did indeed the same trick:

log4j2.yml:

Configuration:
packages: "org.whatever"
Appenders:
Console:
name: console
target: SYSTEM_OUT
ThresholdFilter:
level: debug
onMatch: ALLOW
PatternLayout:
pattern: '%d [%p] [%t] %c{1.} %m%n'
Loggers:
# Avoid superfluous logging due to health checks
Logger:
- name: org.apache.kafka
additivity: false
level: warn
AppenderRef:
- ref: console
- name: kafka
additivity: false
level: warn
AppenderRef:
- ref: console
- name: org.springframework.cloud.config.client
additivity: false
level: warn
AppenderRef:
- ref: console
Root:
level: info
AppenderRef:
- ref: console

[laur89]

If you still want the ConsumerConfig to how up in logs upon startup, you could decrease log level just after kafka binder is started: https://gist.github.com/laur89/bef122a936996d83554353e0601916ae