[
https://issues.apache.org/jira/browse/TS-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036092#comment-15036092
]
ASF GitHub Bot commented on TS-3072:
------------------------------------
Github user SolidWallOfCode commented on the pull request:
https://github.com/apache/trafficserver/pull/350#issuecomment-161358854
Uri - it is not the case that header_rewrite can support the required use
case. There is no hook that is sufficiently early to enable pre-SSL accept
debugging and therefore no plugin can actually enable it that early. I
understand your point and in general agree with it, but the fact remains it is
not possible to do it with the current set of hooks. If you want to propose
adding a hook to make it possible (which would have to be immediately after the
TCP handshake) that would be good. That is outside the scope of this PR.
> 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)
