[
https://issues.apache.org/jira/browse/TS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248161#comment-13248161
]
Leif Hedstrom commented on TS-1079:
-----------------------------------
If I understand the original design correctly, the idea was that
DebugSpecific() would work just like the old Debug() when not being "specific".
But when enabled e.g. in a transaction or session, it would override the
"global" defaults. So when the flag is true, it will always print the debug
info, but when false it depends on whatever the global diags flag is.
The public TSDebugSpecific() API follows the same pattern as the core version I
assume. Meaning, a plugin can now call TSDebugSpecific() in a way that it uses
the global diagnostics settings when false, but forcing the Debug() when true.
This seems generally useful to me.
> 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
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 3.1.4
>
> Attachments: debug_specific.patch, debug_specific_2.patch,
> debug_specific_3.patch, debug_specific_4.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
