Repository navigation
[Reporting] Instantiate a logger top level, and use it throughout the job - #43636
Conversation
389b336 to
b470782
Compare
There was a problem hiding this comment.
In order to get control over how things get logged from within the Chromium driver, I decided it's best to NOT pass the logger to the HeadlessChromiumDriver constructor. Logging happens via the caller's logger object that gets passed to each method of the driver.
There was a problem hiding this comment.
Note: removed a redundant tag
There was a problem hiding this comment.
This was causing a redundant tag
c5bf563 to
07c2287
Compare
💚 Build Succeeded |
|
Pinging @elastic/kibana-stack-services |
There was a problem hiding this comment.
Not exactly related to this PR, but this really should have been logged previously.
There was a problem hiding this comment.
It turns out better to not have a logger tied to the instance. Instead, calling code passes in a logger to all the driver methods.
07c2287 to
ee58673
Compare
💔 Build Failed |
…e-typescript-executeJob-ii
💚 Build Succeeded |
|
Code LGTM! Nice cleanup |
…e-typescript-executeJob-ii
💚 Build Succeeded |
Summary
This PR creates
jobLoggerobjects and shares them throughout the job creation flow and job execution flow. This really helps with job execution, because the jobLogger is now tagged with thejobID, which is now logged with every call to the logger. Having the jobID visible for each log line heavily improves logging experiences in Reporting.Release Note: Improved the logging for Reporting to include the ID of the current job with every log line. Also, several logging events in Reporting have been raised from
debugtoinfolevel.(The last sentence refers to other changes prior to this PR.)