-
Notifications
You must be signed in to change notification settings - Fork 232
Conversation
Codecov Report
@@ Coverage Diff @@
## master #531 +/- ##
============================================
- Coverage 88.42% 88.36% -0.06%
Complexity 505 505
============================================
Files 66 66
Lines 1883 1883
Branches 239 239
============================================
- Hits 1665 1664 -1
- Misses 142 143 +1
Partials 76 76
Continue to review full report at Codecov.
|
I'm of the opinion that bootstrap can be verbose because it allows for easy checks on what the actual configuration of the tracer is on production, etc. |
They are printed only once, but when tracing is a "small" part of a bigger ecosystem, it might not be desirable to have them. I'm quite sure I left the first message at INFO because of local tests ( The second is too verbose to be useful "all the time", which is why I think it should be suppressed. They are indeed useful when debugging why something is wrong, though. |
I just added another commit with some changes to the Here's how it looks like before this PR:
And here's how it looks after:
|
private final boolean expandExceptionLogs; | ||
private final JaegerObjectFactory objectFactory; | ||
|
||
@ToString.Exclude private final PropagationRegistry registry; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like more adding @ToString.Exclude
directly on top of the excluded field without creating a new block for excluded fields. And keep the field at the original place
private final boolean zipkinSharedRpcSpan
@ToString.Exclude
private final ScopeManager scopeManager;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a matter of taste, I guess. I'll keep it like that, unless other reviewers prefer to have the annotation in a different line.
The reason I prefer it this way is that it makes it easy to spot what is and what is not in the toString. More importantly, it makes future decisions more conscious about whether or not the field should be included in the toString, instead of just "copy and paste".
@@ -83,7 +83,7 @@ public static Sender resolve(Configuration.SenderConfiguration senderConfigurati | |||
} | |||
|
|||
if (null != sender) { | |||
log.info(String.format("Using sender %s", sender)); | |||
log.debug(String.format("Using sender %s", sender)); | |||
return sender; | |||
} else { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not directly related to this PR, but to improve clarity of error reporting, just wondering if we should add reporting of these specific scenarios:
- multiple factories but JAEGER_SENDER_FACTORY not specified to select
- multiple factories found, but JAEGER_SENDER_FACTORY value not found in the list
- no sender factories found
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created #532
@vprithvi, could you please re-review this one? If this change is acceptable, I'll merge and do a new release, so that I can consume it on WildFly. |
@jpkrohling LGTM! I like the approach of applying the exclude annotations on the specific fields. Lot less fragile. |
5eb42c9
to
34666c7
Compare
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
34666c7
to
6548879
Compare
Signed-off-by: Juraci Paixão Kröhling [email protected]
Which problem is this PR solving?
Short description of the changes
debug
frominfo
level. Users who wish to see those messages can set log4j to displaydebug
messages forio.jaegertracing
classes.#toString()