-
Notifications
You must be signed in to change notification settings - Fork 151
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
How can we use pino-pretty with non-development defaults? #397
Comments
I believe that PR shows a change to the documentation that would indicate how to reformat the time. |
Yes. |
Configuration files are supported: Lines 23 to 32 in 849f0fc
|
Do you have an example of a configuration file? Could you please show me what I should put in there to get the hostname back, so that the output looks like the output of pino-pretty, v8? |
I believe all of the source code is available for you to review. |
For those of you who don't want to look through the source, it seems that putting a file
It would be nice if there was a way to get this file to be used regardless of the current directory. But I guess each of us is expected to read through the source code to find that out. |
You are welcome to submit pull requests to improve documentation and add desired features. |
This PR, #366, changed the default options for pino-pretty so that
pino-pretty -t
no longer
SYS:standard
option (timestamp with year, month, day, time in UTC)How can I get these back? Is there an easy way (environment variable, config file, command line option) to get pino-pretty working again for non-development systems?
We use pino for logs in our kubernetes environment. When people create issues, I always tell them to paste the relevant logs using
pino-pretty -t
. That used to record the hostname (which micro-service made the log) and the time independent of wherever in the world the person is. But I noticed that recently, that key information is lost.pino-pretty --include hostname
shows me the hostname but it excludes other properties. So it is less than useful.The text was updated successfully, but these errors were encountered: