[
https://issues.apache.org/jira/browse/HTRACE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334097#comment-14334097
]
Colin Patrick McCabe commented on HTRACE-113:
---------------------------------------------
I ran across this when doing some testing. When there's no output, it's nice
to be able to turn up the log4j to find out why.
I realize that the code in {{SamplerBuilder}} which throws an exception and
catches it, just to log a stack trace, is a little awkward-looking. But it
turns out to be by far the best way to get a stack trace out of log4j. All the
other ways involved a lot more tricky code and dealing with stack frame objects.
> Add more log4j messages to htrace SamplerBuilder, SpanReceiverBuilder, etc.
> ---------------------------------------------------------------------------
>
> Key: HTRACE-113
> URL: https://issues.apache.org/jira/browse/HTRACE-113
> Project: HTrace
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Attachments: HTRACE-113.001.patch
>
>
> We should add more log4j messages at DEBUG or TRACE level to htrace
> SamplerBuilder, SpanReceiverBuilder, etc. This will make it easier to
> determine which samplers and span receivers are being used by the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
