[
https://issues.apache.org/jira/browse/TS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198837#comment-13198837
]
Leif Hedstrom commented on TS-1079:
-----------------------------------
Cool, I'll take a look at TS-1102 today (unless someone else beats me to it :).
As for the API / remap: One possibility is to look at the APIs we added to
support overriding records.config settings per transaction. It's a bit hacky,
but works fairly well. The only caveat here is that it only works in places in
the code where you have access to the HttpSM's "State". So that might be a
problem for this?
If necessary, we could add another @ option to remap.config, but we tried to
avoid that as much as possible with the new per-transaction records.config
features (in fact, we removed 3 @ options after adding this feature).
> Add an API function to turn debugging on for specific transactions/sessions
> ---------------------------------------------------------------------------
>
> Key: TS-1079
> URL: https://issues.apache.org/jira/browse/TS-1079
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core, HTTP
> Reporter: Uri Shachar
> Priority: Minor
> Attachments: debug_specific.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> When attempting to troubleshoot issues on a production ATS system, it
> is often impossible/difficult to turn on any of the 'high-volume' debug tags
> like http due to the performance impact.
>
> This enhancement allows a plugin to set a debug flag for a specific txn/ssn,
> and replaces some of the internal Debug calls with a new function that checks
> if the flag is turned on, and outputs the debug line regardless of the tag if
> it is (The diags enable/disable flag is still taken into account).
> The API will also have TSDebugSpecific in order to allow plugins to use the
> same functionality.
> In addition, we might consider adding an internal config file (remap-like) to
> allow turning this flag on without plugin intervention.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
