-
Notifications
You must be signed in to change notification settings - Fork 189
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
Fixed logging format #1450
Fixed logging format #1450
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
@humphd Is it safe to assume we have should have an almost same amount of docs in I'm thinking a doc should be created in the |
@c3ho sorry, I don't follow what you're asking. Also, do you want to merge this? |
@humphd sorry I'm holding off on merging this because I'm testing the options part. It seems to not like What I wanted to ask was for example we have the following when you navigate to http://localhost:9200/_cat/indices?v: with the original PR, we should have a new index called For quick reference this is after a few minutes of running: I would expect the |
Yeah, that sounds odd to me (that it's so low). What do you see in logs when you get those 8? |
|
Nevermind, I got ~7k hits on logs just now. |
It might be caching results and not flushing them to the db until some threshold is reached. |
I think that's the case with the |
@humphd I put another ternary to check |
Issue This PR Addresses
Fixes #1448
Type of Change
Description
Now when logging to console, the log messages will look pretty again.
Could someone also test the pino-elastic logging as well for this and make sure it is also working? I tested it, but it was inconclusive for me.
Steps to test fix:
.env
file setLOG_LEVEL
toinfo
docker-compose up redis elasticsearch
npm start
Check info messages in terminal tab. They should look pretty now (just like before)
To regression test:
.env
file setLOG_LEVEL
toinfo
and setLOG_ELASTIC
to 1docker-compose up redis elasticsearch
npm start
, there should be no logging appearing in terminal tab anymore as they're directed to elasticsearch nowhttp://localhost:9200/_cat/indices?v
You should see two rows and under theindexes
column there should be 2 indexeslogs
andposts
LOG_ELASTIC
to blank again in your.env
file after testing.Checklist