-
Cannot support stream for pretty-pino
I am using Node v20.3.0
"pino": "^8.15.0",
"pino-pretty": "^10.2.0",
"next": "13.4.5",
This is my logger.ts
import pino from 'pino';
import pretty f…
-
### What happened?
I've been debugging for days why tracing does not work as expected.
I've realized that some auto instrumentations are never actually applied.
After a lot of digging, I've l…
gajus updated
2 months ago
-
### Link to the code that reproduces this issue
https://github.com/jdoe802/pino-pretty-mongo-minimal
### To Reproduce
have been working on this for a few weeks now. I was getting errors like …
-
# Problem Solved By The Feature
we use pino for logger with different level. It will be nice to pass in logger
# Solution
create a callback for logger in isr Config.
I will try to make a P…
-
In case of multiple log arguments
```
debug("Redis options", options);
```
native debug.js produces
```
package:server Redis options {
host: 'redis.dev.aaa.io',
port: '6379',
passwo…
-
When pino-pretty is used together with elastic formatting the logging level has `log.level` key in the log object. I found no way to make pino-pretty work correctly with this level key.
In version …
-
The "global" `level` setting isn't taken into account when `transport.targets` parameter is provided - each target has its own level that defaults to `info` ([as mentioned here](https://github.com/pin…
-
Hi, anyway to store console logs to file?
I use npm run start > botxxx.log
But with that no live console logs.
-
Is it possible to change the logging level of a multistream element at runtime?
Consider the _multistream_ example ...
```var fs = require('fs')
var pino = require('pino')
var pretty = require('pi…
-
## Overview
In https://github.com/hyperlane-xyz/issues/issues/918 the monorepo's logging was overhauled to replace Debug with Pino.
A few alternative libs were considered but Pino was chosen. It t…