-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add requestId and sessionId to logs #532
Comments
@eleanorreem can I try my hands on this ? |
Thank you @chinmaym07 you have been assigned this issue! Support Chayn's mission? ⭐ Please star this repo to help us find more contributors like you! |
Hi @chinmaym07 are you still working at this? If not I would like to pick up the issue :) As I see the logging.interceptor already logs the user id of the request as well as the IP, what exactly would the request-ID be? About logging the origin IP of the request, I'm not sure if this could be a privacy issue or what do you think about this?:) Also I there is already a session and session-user but as far as I understand those have different meanings than web sessions, here is a solution for sessions which could the already existing Firebase, maybe this would be a solution! |
Thank you @leoseg you have been assigned this issue! Support Chayn's mission? ⭐ Please star this repo to help us find more contributors like you! |
@leoseg thanks for this! And good catch on the privacy issue. We are planning to remove IP addresses from our logs as we don't need that information, thank you for the reminder. I am going to prioritise that today. I think we would want to log the requestId separate from the userId as the userId can make multiple requests at the same ID. A quick google brought me to this suggestion but alternative methods would be valid. Thanks for your help so far! |
Hi @eleanorreem I created a first pull request here, to hear your thoughts about my implementation idea for logging the request id and session id. I have some problems with my local setup in the moment so until now I only ran the unit tests but I'm on it and let you hear when I did manually test everything. |
…RequestAndSessionLogs-chaynHQ#532 # Conflicts: # yarn.lock
Overview
We currently don't log request IDs or session IDs in our logs. These would be hugely helpful with debugging. Every time we call logger.log or logger.error, the output should be decorated with both requestIds and sessionIds. We are currently refactoring/ improving our logs so any suggestions for improving are welcome.
Action Items
Resources/Instructions
The text was updated successfully, but these errors were encountered: