-
Notifications
You must be signed in to change notification settings - Fork 853
Issues: pinojs/pino
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
pino transport - is it worth using a transport in another process for writing to stdout?
#2000
opened Jul 3, 2024 by
RichardWright
Forbid using default log levels when
useOnlyCustomLevels: true
#1998
opened Jul 1, 2024 by
chernodub
How should a Pino instance be identified in runtime?
#1984
opened Jun 3, 2024 by
gerardo-lima-moonfare
Logs missing in debugger console using node --inspect
help wanted
#1983
opened Jun 3, 2024 by
richterdennis
Promise catch directly calling error log results in "Cannot read properties of undefined" exception
#1962
opened May 1, 2024 by
flyweight
Inclusive language suggestion: rename default branch to "main" across Pino's repos
#1918
opened Mar 9, 2024 by
10xLaCroixDrinker
[question] How do I create dynamic customized logfile names?
#1917
opened Mar 8, 2024 by
JosuerBague
Filtering of the content using transformations in the pipeline for multiple transports
#1916
opened Mar 7, 2024 by
WoZ
transport options - either confusing variable names or I'm just still learning (free to admit it)
#1911
opened Feb 28, 2024 by
YeeP79
pino/file logs do not get populated to docker container via mounted volume until the app closes
#1902
opened Feb 9, 2024 by
mjarosie
Improve documentation on global logging level with multiple targets
#1895
opened Feb 5, 2024 by
mjarosie
Pino rejecting a valid json format in case of error passed as object.
#1875
opened Jan 5, 2024 by
jindalAnuj
Previous Next
ProTip!
Adding no:label will show everything without a label.