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

Implement health monitoring #11

Open
TimDaub opened this issue Nov 4, 2019 · 2 comments
Open

Implement health monitoring #11

TimDaub opened this issue Nov 4, 2019 · 2 comments

Comments

@TimDaub
Copy link
Collaborator

TimDaub commented Nov 4, 2019

Scope

  • It's really important for the challenge-services to be running reliably as otherwise invalid operations could pass on the LeapDAO Plasma chain

Deliverables

  • Create a service that monitors the health of the event-scanner service by e.g. periodically checking:
    • if event-scanner returns a valid response through a HTTP API
    • if event-scanner is at the latest height of the configured Ethereum chain
    • if event-scanner has stored some new events in its queue
    • etc.
  • In cases where the health of event-scanner can be considered damaged, the health monitor should send a message to its operators (e.g. through Slack) to notify them about the issue

Notes

  • In the future, it might make sense to implement a restart or self-healing mechanism for event-scanner. Given that various things could go wrong, however, I currently believe this would be premature and difficult to do reliably. So human intervention at this point is more reliable.

Gain for the Project

  • Improved uptime for event-scanner

Roles

bounty gardener: @TimDaub / 10%
bounty worker: name / 75%
bounty reviewer: name / 15%

@TimDaub TimDaub added the bounty label Nov 4, 2019
@TimDaub TimDaub self-assigned this Nov 4, 2019
@troggy
Copy link
Member

troggy commented Nov 4, 2019

can these be built in the challenge service itself? Otherwise these checks can be made as a an extra checks in https://github.com/leapdao/leap-peeper

@johannbarbie
Copy link
Member

no feedback to question

@troggy troggy reopened this Dec 4, 2019
@troggy troggy removed the bounty label Dec 4, 2019
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

No branches or pull requests

3 participants