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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grafana Dashboard #38
Comments
https://wiki.polkadot.network/docs/maintain-guides-how-to-monitor-your-node
Is there anything related to the CPU and memory usage in the Prometheus metrics exposed by Reef Node? This is what I can see in the
|
I think the main 2 metrics on server side are disk and RAM usage. I dont think this should be proxied through Reef, there is probably a better way to monitor global server health. On the Reef side of things, the thing to look for are any errors, equivocations or non-consensus in finality. |
@Netherdrake Do you think the proposed Dashboard covers all mentioned information? If so, I could close this issue. If not, then please let me know which metrics specifically you would like to see there [based on the Prometheus metrics in my previous comment]. |
I've decided to close this issue as there is no activity. Grafana dashboards which could be helpful are linked in the description. |
First of all, congratulations for successfully launching the Reef Chain mainnet! 馃殌
Mainnet is a network of the nodes and there are many people running their own nodes. In fact, maintenance of such a node is not so easy and requires substantial technical knowledge. Apart from the knowledge, it also requires constant monitoring and keeping the nodes up and running. In turn, to have monitoring in place, there must be in place a mechanism for gathering metrics (and alerting). Thankfully, Substrate already provides the Prometheus metrics out of the box.
Grafana is a software commonly used to visualize Prometheus metrics. I would like to propose creating a ready to use Grafana Dashboard which would use all exposed Prometheus metrics.
For a starter, I took the Polkadot one and modified it appropriately for what Reef Node exposes.
Here is my Reef Node Grafana Dashboard.
Note: it doesn't include the underlying machine resources utilization (CPU, memory, network), because Reef Node doesn't expose them in the Prometheus metrics.
What do you think? Would you change the proposed Grafana Dashboard in any way? Any suggestions?
The text was updated successfully, but these errors were encountered: