This PR introduces different kind of logger. Right now the API has one logger and its the default one provided by restify and uses pino under the hode.
Motivation and Context
This hat a motivational background in debugging purposes and support requests. Right now it is only possible to see some basic information in requests coming in and sometimes it is quite hard to identify the issue.
The introduced debugLogger extends the log message by including the request body. It should only be used in support cases.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Chore (update dependencies or documentation)
Checklist:
[x] My code has been linted using yarn run lint.
[x] My code does not break the tests (yarn run test)
[ ] My change requires a change to the documentation.
Description
This PR introduces different kind of logger. Right now the API has one logger and its the default one provided by
restifyand usespinounder the hode.Motivation and Context
This hat a motivational background in debugging purposes and support requests. Right now it is only possible to see some basic information in requests coming in and sometimes it is quite hard to identify the issue. The introduced
debugLoggerextends the log message by including the requestbody. It should only be used in support cases.Types of changes
Checklist:
yarn run lint.yarn run test)