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 verbosity of the logs #124

Closed
P1sar opened this issue Mar 6, 2023 · 0 comments · Fixed by #136
Closed

Improve verbosity of the logs #124

P1sar opened this issue Mar 6, 2023 · 0 comments · Fixed by #136

Comments

@P1sar
Copy link
Contributor

P1sar commented Mar 6, 2023

It is pretty difficult to debug some of the occasions when relayer is running, next improvements are suggestions to improve general verbosity of some Relayer actions

Implementation details

1.[Info] On startup Relayer should log all SYG_DOM_N evs values. (Except private key, please in this log convert private key to corresponding address)
2. [Info] Processing any events logs should appear not every iteration call but every 5 minutes with the range of all parsed during that time blocks and amount of found events. Although when event found all the logs should remain the same
3. [Info] Print Network Topology on startup and after Refresh
4. [Info] Print Topology URL on startup and on key Refresh
5. [Info] When Relayer is not part of part of MPC group (situation when Relayer have been deployed by partners, but it is still have not being added to Topology map hence does not have any peers) it should notify about this every 5 minutes.

Testing details

Acceptance Criteria

[] Logs have been added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants