[
https://issues.apache.org/jira/browse/TS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192465#comment-13192465
]
Leif Hedstrom commented on TS-1079:
-----------------------------------
The patch looks good to me. And yes, I agree, we require gcc (or compatible) >
4.1 I think (to simplify atomic support). I'm fine with cleanup (getting rid of
old crud is good).
I'm assuming the next step is for you to change some (select) Debug()
invocations in the core? How do you plan to decide which ones are useful or not?
> 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
