update tslog json transport to spit out proper json
sanitize log message in some places
add additional secret mask regex values
Due to numerous limitations with both pino (doesn't work with next.js) and winston (doesn't support log traces, difficult formatting, having to do new Error() to display error stack), we are sticking with tslog, but have made changes to the JSON transport to allow better parsing in splunk.
Readiness Checklist
Author/Contributor
[ ] If documentation is needed for this change, has that been included in this pull request
[X] run npm run lint and fix any linting issues that have been introduced
[X] run npm run test and run tests
[ ] If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz
Reviewer
[x] Label as either bug, documentation, enhancement, infrastructure, maintenance, or breaking
Pull Request
Proposed Changes
Due to numerous limitations with both pino (doesn't work with next.js) and winston (doesn't support log traces, difficult formatting, having to do
new Error()to display error stack), we are sticking with tslog, but have made changes to the JSON transport to allow better parsing in splunk.Readiness Checklist
Author/Contributor
npm run lintand fix any linting issues that have been introducednpm run testand run tests@jeffrey-luszczReviewer
bug,documentation,enhancement,infrastructure,maintenance, orbreaking