[
https://issues.apache.org/jira/browse/TS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137626#comment-14137626
]
Sudheer Vinukonda edited comment on TS-3072 at 2/23/15 5:54 PM:
----------------------------------------------------------------
Thanks, [~jpe...@apache.org] -
Yes, I am using the same framework as that of TSHttpTxnDebugGet()/Set(), except
that I'm making it a little bit more easier to use (for e.g. adding a setting
for the user to specify any arbitrary client/ip using traffic_line rather than
having to write/code a plugin etc) and also extend the logging support beyond
http (for e.g. NetVC, Spdy, FetchSM etc). Currently, we have it only in
HttpSM/HttpTransact.
was (Author: sudheerv):
Thanks, [~jpe...@apache.org]] -
Yes, I am using the same framework as that of TSHttpTxnDebugGet()/Set(), except
that I'm making it a little bit more easier to use (for e.g. adding a setting
for the user to specify any arbitrary client/ip using traffic_line rather than
having to write/code a plugin etc) and also extend the logging support beyond
http (for e.g. NetVC, Spdy, FetchSM etc). Currently, we have it only in
HttpSM/HttpTransact.
> 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: 5.3.0
>
>
> 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)
