Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Monitoring: Make it easy to find which incoming requests triggered logged errors #638

Open
adrienjoly opened this issue Jul 29, 2023 · 0 comments
Open

Monitoring: Make it easy to find which incoming requests triggered logged errors #638

adrienjoly opened this issue Jul 29, 2023 · 0 comments
Labels
help wanted production

Comments

@adrienjoly
Copy link
Member

Cf https://github.com/goldbergyoni/nodebestpractices#-514-assign-a-transaction-id-to-each-log-statement

E.g. by using a standard logging library (e.g. Winston) and/or AsyncLocalStorage
adrienjoly added a commit that referenced this issue Aug 23, 2023
@adrienjoly
fix(api): return 404 status codes on "not found" pages (#674)
f4c8867 
contributes to #638.
@adrienjoly adrienjoly mentioned this issue Aug 23, 2023
Merged
adrienjoly added a commit that referenced this issue Aug 23, 2023
@adrienjoly
fix(logs): log errors thru stderr, with stack trace
e3671c7 
contributes to #638.
@adrienjoly adrienjoly mentioned this issue Aug 23, 2023
Merged
adrienjoly added a commit that referenced this issue Aug 23, 2023
@adrienjoly
fix(logs): log errors thru stderr, with stack trace (#675)
dbf3c96 
contributes to #638.
@adrienjoly adrienjoly changed the title Make it easy to find which incoming requests triggered logged errors Monitoring: Make it easy to find which incoming requests triggered logged errors Sep 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted production
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adrienjoly