-
## Is your feature request related to a problem? Please describe.
Currently only Winston is supported for enriching logs via the @newrelic/winston-enricher module, but we are using Pino for logging. …
-
Review the codebase and determine the correct logMessage level dependent on whether the message should appear only in development or in Staging / Production level logs.
Current logMessage levels are:…
-
I'm facing an issue after updating pino from "pino": "^4.16.1" to "pino": "^5.8.0"
```
Error: EPIPE: broken pipe, write
Emitted 'error' event at:
at SonicBoom.release (/app/node_modules/soni…
-
Any ideas why im getting req twice in logged json?
```{
"level": 30,
"time": 1573488495601,
"pid": 6012,
"hostname": "nodejs",
"req": {
"id": "1573488495579:nodejs:6012:k2umf1vz:10000"…
-
### Prerequisites
- [X] I have written a descriptive issue title
- [X] I have searched existing issues to ensure the bug has not already been reported
### Fastify version
3.28.0
### Plu…
-
When using the bunyan wrapper for logging from a Google Cloud Function, there doesn't appear to be a way to tell when the logs have been flushed to Stack Driver. If you don't give the logger time to f…
-
**Is your feature request related to a problem?**
I get colorization characters in my logs:
```
[2022-02-21 10:49:43] http --- [33m200[39m, req: 'GET https://artifactory.walkmernd.com/artifac…
osher updated
2 years ago
-
I'd like to recreate the `debug` value proposition in a pino compatible way
debug is a different use case (dev more than prod) - but I've also seen teams using debug for prod logging - I'm thinking…
-
Maybe I'm missing something, but I don't seem to be able to log all levels (or part of levels) to the same transport.
My Pino configuration looks like this:
```js
const transport = pino.transpo…
-
Like SonicBoom, it would be helpful if the pino/file transport provided a `mkdir` option to instruct the transport whether to ensure the directory of the destination file exists before attempting to o…