[jira] [Updated] (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 updated TS-3072:
-------------------------------
    Attachment: ts-3072.diff

Re-activating the discussion.  We recently deployed what [~sudheerv] suggested in production while tracking yet another tedious user-specific crash.  

I've attached the patch in ts-3072.diff.  It is a surprisingly small code change.  We changed how debug.enabled is interpreted to minimize the performance impact if one is not using the debug.client_ip feature.  The client-ip value is only tested if debug.enabled is set to 2.  Regular full debugging happens with debug.enabled set to 1.  Nothing is checked if debug.enabled is set to 0.

It was incredibly useful while tracking down our most recent fire.  We didn't have to anticipate the need for a plugin.  We were able to change the client_ip setting without restarting ATS.  

[~amc] has ideas for generalizing this technique to "taint" VC's for other more detailed tracking/debugging/monitoring.

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