Collect prototype feedback

[cfl0ws]

Introduction

We're feeling excited to release this Validator Monitoring and Alerting tool prototype to the community.

Chainflow would like to express our gratitude to our development partner Vitwit. We partnered with them a few months ago and have been working together with @anilcse and his team since then to develop and release this.

Thanks also to @mnugumanova from Ztake and @EdouardLvdl from POS Bakerz for providing preliminary feedback.

The Tool - Monitoring

You'll see that the tool is comprised of three Grafana dashboards.

1 - Summary

This view provides a quick-look at overall validator and system health.

2 - Validator Monitoring Metrics

This view provides a comprehensive look at validator details and performance. It also includes proposal information.

3 - System Monitoring Metrics

This view provides a comprehensive look at system performance metrics.

You can view the dashboard here -

http://134.209.142.233:3000/

uid: user3

pwd: user3

Note: The dashboard is currently monitoring a single validator-sentry pair on the current Cosmos testnet.

#8

The Tool - Alerting

The tool is configured to send selected, user-configurable alerts to a Telegram bot. You can see the bot in action here. You can find a list of the alerts here.

Bonus! Validator alerting bot...

We also released a bonus Validator Voting bot. You can use it to confirm your validator is voting and receive an alert if you validator stops voting. Find find the code and deployment instructions here.

Your Feedback

We're building this tool for the Cosmos community. Your feedback is essential in making this tool as useful to you as possible.

Please provide constructive feedback in the comments of this issue by 0000 UTC 2 April 2020 👇

#8

If you don't know where to start, pointing out one or two things you -

1 - Find beneficial

2 - Feel could be added or improved

...is a great place to start.

We can also discuss the tool in the Chainflow Telegram Group.

Next Steps

1 - Collect community feedback until 0000 UTC 4 April

2 - Triage, clarify and implement feedback

3 - Release prototype instructions and open source the code