[
https://issues.apache.org/jira/browse/KAFKA-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129389#comment-16129389
]
CJ Woolard commented on KAFKA-5740:
-----------------------------------
For deployments in Mesos, where you typically have a scheduled health check
assigned to your Kafka Connect distributed worker instances, you end up with
quite a few HTTP log lines in the Kafka Connect logs. This can sometimes make
it difficult to inspect the output of the Kafka Connect tasks themselves
(without additional tooling). As this ticket describes it might be helpful to
separate out the HTTP logs from the 'normal' Kafka Connect logs in order to
ease debugging scenarios.
> 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: 0.11.0.0
> 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
(v6.4.14#64029)
