cfl0ws / chainflow

Results 16 comments of cfl0ws / chainflow

No additional feedback has been received, so I'm considering this done for now.

Removed the security section from the MVP, based on feedback from @greg-szabo and pending further discussion.

Thanks @jackzampolin for your feedback in the doc and via Telegram. In addition to the comment you suggested in the doc, I'll add your Telegram feedback here for reference -...

@anilCSE I added your suggestions. Please check rows 58-61 to see if they convey what you had in mind. I'm debating whether these will be in the MVP or added...

@novy4 Are you referring to all unclaimed/unwithdrawn rewards, as described [here](https://docs.cosmos.network/master/modules/distribution/04_messages.html#msgwithdrawdelegationrewardsall)?

@liangping Can you please clarify specifically what data you mean? Are you referring to the connections among sentries and validators, to confirm they're communicating with each other?

@jackzampolin are there any specific metrics you feel would be beneficial related to this? https://docs.cosmos.network/master/modules/distribution/04_messages.html#msgwithdrawdelegationrewardsall I'm going to add these to the MVP Plus sheet for now. My thinking is...

I've shortlisted the tools to - - Icinga - Prometheus - Zabbix Next step will be to map each to the requirements docs to identify the best fit or fits,...

After doing some additional research, it seems like a combination of Prometheus and Icinga is the way to go. If this combination falls short, I'll look at Zabbix again.

It turns out that Icinga was unnecessary, as we were able to customize Grafana/Prometheus to send the alerts we needed to send, using a custom-built alerting module, which will be...