Enable pino logger #851
Merged
Enable pino logger #851
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Westlad approved these changes Aug 5, 2022
I've added a DNM because I'll do a couple of tests before merging. |
…htfall_3 into david/logger-pino
Sign up for free to join this conversation on . Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Fixes #846
Use pino logger so that its easier to export logs to data dog monitoring services
This is the expected log output for production environments, in JSON format:
{"level":"info","time": "2022-08-08T20:25:08.112Z","msg":"Received request to /vk"}For the non-production envs the logs continue with the same format, with a slightly difference, the timestamp:
[2022-08-09 08:52:35.298] WARN: Attempted to replay existing transaction. This is expected while syncing