[ 
https://issues.apache.org/jira/browse/KAFKA-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822823#comment-16822823
 ] 

ASF GitHub Bot commented on KAFKA-8271:
---------------------------------------

mjsax commented on pull request #6614: KAFKA-8271: Changed(De)Serializer should 
forward call to configure()
URL: https://github.com/apache/kafka/pull/6614
 
 
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Trogdor - Log Jetty requests at DEBUG level
> -------------------------------------------
>
>                 Key: KAFKA-8271
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8271
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Stanislav Kozlovski
>            Priority: Minor
>
> When running Trogdor, as with any system, is it important to keep track of 
> the logs it produces.
> Trogdor agents can log useful information at the INFO level, depending on the 
> worker being ran on them. The problem is that when you enable INFO level logs 
> for the Agent, Jetty logs all the requests sent to the Agent at INFO.
> This results in a lot of useless logs like
> {code:java}
> [21/Apr/2019:11:46:52 +0000] "GET /agent/status HTTP/1.1" 200 1171 2{code}
> This can obscure the useful logs, especially when inspecting logs from a 
> decent-sized Trogdor cluster. It would be great if we could set these logs at 
> DEBUG level



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to