-
When using `Pino.stdSerializers.errWithCause` in the browser the "cause" property of errors are not, in fact, serialized.
Video demonstrating the behavior.
https://www.loom.com/share/916e9677c5094…
-
Hi
I am using pino logger for nestjs, and add to each log a correlation id.
The problem is when the entry point is not via request, the correlation id is missing, and therefore I don't have any trac…
-
Hello, how to pretty output the logs? I'm trying pino-pretty, but that isnt working.
`nx run api:start | pino-pretty \"[{severity}] {message}\"`
```
[[object Object]]:
severity: "INFO"
re…
-
### Description
The JWT is always logged in internal microservice comms - this is a risk if Kibana is hacked or if a server engineer is corrupt
https://nkhilv.medium.com/how-to-redact-sensitive-info…
-
## Improve and Standardize Error Handling and Logging Strategy
### Description
While we already use pino for logging in our SDK, our error handling approach is inconsistent across the codebase. We…
-
```js
const pino = require('pino')
const logger = pino({
transport: {
target: 'pino-pretty',
options: {
colorize: true,
sync: true
}
}
}, pino.destination({sync:t…
-
From the back of , I took a look at pino and found we should be able to drop it in with a few tweaks.
## Things I looked at
### `defaultMeta`
We use this to enrich all log entries emitted by …
-
-
Was just testing this briefly and I notice that the scripts does not automatically close on completion, meaning there's probably some event handler or something that is left hanging, which is differen…
sp00x updated
3 weeks ago
-
For some reason getting the below error, works fine in development but not when built.
```bash
⨯ Error: unable to determine transport target for "@baselime/pino-transport"
at fixTarget (/var/ta…