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.

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

Improve Request Node Logging #1391

Closed
4 tasks done
MantisClone opened this issue Apr 17, 2024 · 0 comments · Fixed by #1463
Closed
4 tasks done

Improve Request Node Logging #1391

MantisClone opened this issue Apr 17, 2024 · 0 comments · Fixed by #1463
Assignees

Comments

@MantisClone
Copy link
Member

MantisClone commented Apr 17, 2024

Problem

The Request Node logs are difficult to read and analyze.

  • information is split across separate logs so it's hard to correlate the logs

Proposed Solution

  • Every endpoint on the gateway should log the incoming request and the outgoing response.
  • Label all data - Logs should be clear about whether they're logging Channel ID, Request transaction ID, on-chain transaction ID.
  • If possible and easy, Whenever we log the request transaction ID, we should also log the on-chain transaction ID and the IPFS CID
  • Whenever the Request Node times out we should log it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

2 participants