[Bug]: default metadata is not added on log message of profiler
See original GitHub issue🔎 Search Terms
metadata profiler
The problem
When logging a message with the profiler, the default meta data of the logger instance is not added to the log message.
It is calling this.logger.write()
directly, and it should have the added default metadata as well.
I worked around it by adding the defaultMeta myself:
profiler.done({ message: "Finished complete request", ...logger.defaultMeta });
What version of Winston presents the issue?
v3.8.1
What version of Node are you using?
v16.16.0
If this worked in a previous version of Winston, which was it?
No response
Minimum Working Example
No response
Additional information
No response
Issue Analytics
- State:
- Created a year ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Profiler Troubleshooting - Datadog Docs
Missing profiles in the profile search page · Reduce overhead from default setup · Increase profiler information granularity · Enabling the allocation profiler....
Read more >Continuous profiler errors - Unity Forum
I've been getting this message lately, it stops my profiler recording. Unpressing record and pressing it ... Complete() missing somewhere.
Read more >Troubleshooting - Profiler - Google Cloud
To access the Profiler API settings for your project, do the following: Click Go to Profiler API settings. In the toolbar, select your...
Read more >Node.js: Winston: Can I add default meta data to all log ...
I'm using Winston in Node.js for logging. I know I can add metadata individually to each log message but is there a way...
Read more >Changes - Google Git
profiler : Add log messages for slow path in start. Fix start to allow retry until success. firestore: Add admin client. containeranalysis: Add...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@maverick1872 FYI
You can treat 3.7.1 as that RC, but a failing one as described in #2103…