[jira] [Commented] (TS-3072) Debug logging for a single connection in production traffic.

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on TS-3072:
------------------------------------

GitHub user shinrich opened a pull request:

    https://github.com/apache/trafficserver/pull/350

    TS-3072: Debug logging for single connection.

    Proposed changes to enable per-client-ip specification for debug messages.  A version of this code has been running in our production for the past month.  We are able to capture debug messages from the start of the TCP connection.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shinrich/trafficserver ts-3072

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/350.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #350
    
----

----


> Debug logging for a single connection in production traffic.
> ------------------------------------------------------------
>
>                 Key: TS-3072
>                 URL: https://issues.apache.org/jira/browse/TS-3072
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core, Logging
>    Affects Versions: 5.0.1
>            Reporter: Sudheer Vinukonda
>            Assignee: Susan Hinrichs
>              Labels: Yahoo
>             Fix For: 6.1.0
>
>         Attachments: ts-3072.diff
>
>
> Presently, when there's a production issue (e.g. TS-3049, TS-2983 etc), it is really hard to isolate/debug with the high traffic. Turning on debug logs in traffic is unfortunately not an option due to performance impacts. Even if you took a performance hit and turned on the logs, it is just as hard to separate out the logs for a single connection/transaction among the millions of the logs output in a short period of time.
> I think it would be good if there's a way to turn on debug logs in a controlled manner in production environment. One simple option is to support a config setting for example, with a client-ip, which when set, would turn on debug logs for any connection made by just that one client. If needed, instead of one client-ip, we may allow configuring up to 'n' (say, 5) client-ips. 
> If there are other ideas, please comment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)