Ewen Cheslack-Postava commented on KAFKA-5740:

Isn't this something that can be handled via log4j configs to separate the two 
types of log traffic? Is this about defaults or some other issue that can't be 
handled via log4j?

I'd make a strong *no* vote to removing the HTTP logs from the default Connect 
logs. They provide way too useful information when debugging issues. Just the 
HTTP status info often reveals something important (whether bad input 
triggering something in the 4xx range or something broken in Connect triggering 
the 5xx range).

> Use separate file for HTTP logs
> -------------------------------
>                 Key: KAFKA-5740
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5740
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions:
>            Reporter: Randall Hauch
>            Priority: Critical
>              Labels: monitoring, usability
> Currently the HTTP logs are interspersed in the normal output. However, 
> client usage/requests should be logged to a separate file.
> Question: should the HTTP logs be *removed* from the normal Connect logs?

This message was sent by Atlassian JIRA

Reply via email to