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

["Susan Hinrichs (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Susan Hinrichs reassigned TS-3072:
----------------------------------

    Assignee: Susan Hinrichs

> 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: sometime
>
>         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)