OpenBankProject / OpenBankProject/OBP-API
Excessive DEBUG logging by Kafka consumer
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
When using the Kafka connector OBP_CONNECTOR = "kafka_vSept2018"
I'm seeing a constant stream of debugging logs like this
06:10:37.788 [Thread-12] DEBUG org.apache.kafka.clients.consumer.internals.Fetcher - [Consumer clientId=consumer-1, groupId=obp-api-north.side.consumer] Added READ_UNCOMMITTED fetch request for partition to.obp.api.0.caseclass.OutboundGetAccounts-0 at offset 0 to node kafka-0.kafka.obp-example.svc.cluster.local:9092 (id: 1001 rack: null)
I tried and unable to turn the logs off by setting
OBP_LOGGER_LOGLEVEL = "INFO"
OBP_AKKA_CONNECTOR_LOGLEVEL = "INFO"
How do I silence the Kafka DEBUG logs?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Kafka connector configuration for OBP_CONNECTOR="kafka_vSept2018" and the OBP_LOGGER_LOGLEVEL and OBP_AKKA_CONNECTOR_LOGLEVEL settings. Reproduce the consumer's DEBUG output and verify that the Kafka client messages are silenced while INFO-level logging remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, scala
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100