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

Grafana Docker Dash Doesn't show Prysm Prater Metrics #26

Closed
alexpeterson91 opened this issue Dec 5, 2021 · 5 comments · Fixed by dappnode/DAppNodePackage-exporter#8
Assignees

Comments

@alexpeterson91
Copy link
Member

Describe the bug
The grafana docker dashboard doesn't appear to show Prysm Prater Beacon-chain and Validator. when running a mainnet prysm package at the same time. they appear to be combined into one service for each sub-service, both mainnet and prater beaconchain, and then both mainnet and prater validators.

To Reproduce
Install DMS, DAppNodeExporter, Prysm Prater, GoerliEth, geth light, and prysm.
let everything sync and go to the dms dashboard for docker and you will see what seems to be an outsize amount of resources dedicated to beacon-chain, and validator. shut off the prysm and youll se a huge drop in resource usage but not entirely. it continues to run at prater speed.

Expected behavior
I would expect to see a beacon chain metric, a prater beacon chain metric, a prysm validator metric, and a prysm prater validator metric

Screenshots
with both prater and mainnet running
Screen Shot 2021-12-05 at 4 53 07 AM
shut off mainnet prysm
Screen Shot 2021-12-05 at 4 57 17 AM
dashboard after shutting off prysm mainnet
Screen Shot 2021-12-05 at 4 56 47 AM

DAppNode version:
@mgarciate sees the same, and i see it on all 5 of my dappnodes

@alexpeterson91
Copy link
Member Author

@alexpeterson91
Copy link
Member Author

alexpeterson91 commented Dec 19, 2021

Grafana still shows only 1 beacon-chain application, and 1 validator application, for every instance of Prysm, combining them all, so if you have Prysm, Prysm Prater, and Gnosis Beacon Chain Prysm, they are all combined into one service for each sub service so on grafana you see just beacon chain, but its actually a combo of all prysm applications you have installed, testnets, gnosis, mainnet etc, need to make it show them as different its making troubleshooting impossible. Screenshot clearly showing how at least prater and mainnet are combined was in the first post of this issue. @mgarciate @eduadiez @tropicar dappnode/DAppNodePackage-prysm-prater#29 did not fix this or https://github.com/dappnode/DAppNodePackage-prysm-prater/issue/28 as it was supposed to.
The situation is now worse with the GBC prysm being a package on DAppNode, since it also combines

@mgarciate
Copy link

Grafana still shows only 1 beacon-chain application, and 1 validator application, for every instance of Prysm, combining them all, so if you have Prysm, Prysm Prater, and Gnosis Beacon Chain Prysm, they are all combined into one service for each sub service so on grafana you see just beacon chain, but its actually a combo of all prysm applications you have installed, testnets, gnosis, mainnet etc, need to make it show them as different its making troubleshooting impossible. Screenshot clearly showing how at least prater and mainnet are combined was in the first post of this issue. @mgarciate @eduadiez @tropicar dappnode/DAppNodePackage-prysm-prater#29 did not fix this or https://github.com/dappnode/DAppNodePackage-prysm-prater/issue/28 as it was supposed to.
The situation is now worse with the GBC prysm being a package on DAppNode, since it also combines

@alexpeterson91 @eduadiez @tropicar @dapplion I'm working on it. I'll create a PR today.

@mgarciate
Copy link

@alexpeterson91
Copy link
Member Author

@eduadiez @tropicar @alexpeterson91 Created PR dappnode/DAppNodePackage-exporter#8

Check new dashboard at https://github.com/mgarciate/DAppNodePackage-exporter/blob/fix/7_ungroup_usage_same_name_services/docker-grafana-dashboard.json

Works great for me this linked PR does fix this issue fully for me. On all machines.

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.

3 participants