-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable logging in ES client #2862
Conversation
Signed-off-by: albertteoh <[email protected]>
cc @dekimsey |
Codecov Report
@@ Coverage Diff @@
## master #2862 +/- ##
==========================================
- Coverage 95.98% 95.95% -0.03%
==========================================
Files 223 223
Lines 9679 9685 +6
==========================================
+ Hits 9290 9293 +3
- Misses 322 325 +3
Partials 67 67
Continue to review full report at Codecov.
|
pkg/es/config/config.go
Outdated
case logger.Core().Enabled(zap.DebugLevel): | ||
l = zapgrpc.NewLogger(logger, zapgrpc.WithDebug()) | ||
options = append(options, elastic.SetTraceLog(l)) | ||
case logger.Core().Enabled(zap.InfoLevel): |
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 am not sure this is a good idea. Our default log level is info, so we're going to be adding a log line for every span written in the collector.
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.
Okay, fair point about the collector. The motivation for this PR was to log ES queries so I think just showing the tracelog when debug
logging is enabled is enough, and the rest, including info level in jaeger, should default to ErrorLevel
logging in ES client.
It also brings up the question of whether the debug logs for collector would be too much as it would log the entire span's content which can be very large. The only log line the collector writes when log-level=debug
is:
{"level":"debug","ts":1615007007.183977,"caller":"app/span_processor.go:149","msg":"Span written to the storage by the collector","trace-id":"4a9afb787bbb4f3f","span-id":"4a9afb787bbb4f3f"}
which I can see a use case for when debugging ingestion. With ES queries in the logging mix, it may be hard to see the above logs without grepping. As such, maybe we need to isolate this feature to jaeger-query and not jaeger-collector, though I'm not sure how easy this would be?
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.
You're probably better positioned to answer this since you're running this setup in prod.
Another option instead of piggy-backing on the main log level is to add just an --es.
flag for log level, then people can go nuts if they want to, all the way to full payload.
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.
Actually, we don't use jaeger-collector with ES as the backing store; although I do like your suggestion of having a separate flag (I propose --es.log-level
), which I'll aim to do in the coming day or so.
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.
@yurishkuro I've added the --es.log-level
(and --es-archive.log-level
) flag and tested it together with --log-level
in different combinations of values. Both the --es
and non---es
flags are decoupled, working independently of one another.
Signed-off-by: albertteoh <[email protected]>
Signed-off-by: albertteoh <[email protected]>
814c257
to
62cdf8b
Compare
Signed-off-by: albertteoh [email protected]
Which problem is this PR solving?
Short description of the changes
Testing
Manually tested with the following combination of flags on jaeger-collector:
ES_LOG_LEVEL=debug
only: logs ES queries as expectedES_LOG_LEVEL=debug LOG_LEVEL=debug
: logs both ES queries and usual collector debug logs as expectedES_LOG_LEVEL=debug LOG_LEVEL=error
: logs ES queries as expectedManually tested with the following combination of flags on jaeger-query:
ES_LOG_LEVEL=debug
only: only logs primary ES client queries.ES_LOG_LEVEL=debug ES_ARCHIVE_LOG_LEVEL=debug
: logs both primary ES client as well as archive ES client queries.Example logs: jaeger-query
With
ES_LOG_LEVEL=debug
:With
ES_LOG_LEVEL=info
:Example logs: jaeger-collector
With
ES_LOG_LEVEL=debug
:With
ES_LOG_LEVEL=info
: