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

Keyper synch monitor #552

Open
ylembachar opened this issue Nov 25, 2024 · 0 comments · May be fixed by #559
Open

Keyper synch monitor #552

ylembachar opened this issue Nov 25, 2024 · 0 comments · May be fixed by #559

Comments

@ylembachar
Copy link

ylembachar commented Nov 25, 2024

Create a mechanism that:

  • monitors the keyper for the latest synchronized block number in the transaction event table every 30s
  • verifies if the block number has progressed since the last check. If not, the service triggers an error to restart the container
@ylembachar ylembachar linked a pull request Nov 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant