Pinned issues
Issues
- 3
v9 release doesn't list breaking changes
#1952 opened - 2
- 2
Import error when using worker with pkg
#1948 opened - 1
pino assign takes only http context
#1944 opened - 3
Transport is not being waited for in lambda
#1938 opened - 2
Using pino with nextjs
#1936 opened - 3
[Question] Same logger for both node and browser
#1935 opened - 3
Docs: Pino Logging with Grafana Promtail/Loki
#1932 opened - 10
`pino.transport.pipeline` may have lost logs
#1927 opened - 6
Verifying logs from unit tests (again!)
#1926 opened - 7
Accessing log level label from transport
#1925 opened - 3
Applying regex to redact keys or value
#1924 opened - 2
- 1
Bundling to `ESM` using `vite`
#1919 opened - 3
- 3
- 1
- 2
consider using toad-cache
#1914 opened - 1
create a function to capture full log object
#1912 opened - 1
transport options - either confusing variable names or I'm just still learning (free to admit it)
#1911 opened - 6
- 2
transport for file does not work in middleware.
#1909 opened - 5
Request: mixed sync/async transports
#1907 opened - 2
Simple log file rotation
#1906 opened - 1
- 6
Logs written out of order
#1903 opened - 2
pino/file logs do not get populated to docker container via mounted volume until the app closes
#1902 opened - 10
Question: CPU usage overhead vs console.log
#1899 opened - 1
- 4
- 3
Question: Are transports browser compatible?
#1893 opened - 1
- 8
- 3
Question: Is dynamic log redaction possible?
#1890 opened - 4
- 2
- 5
It will be cool to configure level per context, it's available in other languages and libraries
#1886 opened - 7
Error: overwritten\n at writeSync
#1885 opened - 5
Pino streams do not honor logger level debug
#1884 opened - 5
Allow custom levels comparison
#1880 opened - 6
Create a logfmt transport
#1879 opened - 3
- 3
- 1
- 5
- 3
- 9
TS2344 & TS2339 errors on building with v8.17
#1864 opened - 2
- 1
- 1