-
Notifications
You must be signed in to change notification settings - Fork 41
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
No data in dashboard #3
Comments
Hey! There some errors in |
If you are using ssh, make sure run the command with nohup. Also make sure the mtail binary file has right permission to execute. It requires 3.0.0 rc45 version. |
You can check your farmer host 9090 port first. It should show the Prometheus portal and you should be able to query the data like total_plots |
Also, you can check http://ptometheus_ip:9090/metrics and find your chia services |
I have pretty much the same issue, probably some kind of configuration is missing. Second thing is the run_mtail.sh script: In addition, I see mtail needs to look at ~/.chia/mainnet/log/farmer_summary.log but this file does not exists. In that way I have the grafana dashboard partially working: I have total plots, challenges per harvester, etc but missing earned xch, expected xch, netspace, etc So I think we need to change something on the config.yaml of chia to generate ~/.chia/mainnet/log/farmer_summary.log |
This helped a lot. For anyone else, you need to change paths in EVERY script in the repository AND change the user in watch-farmer.service too! |
I have the same problem did you managed to fix it? |
Hi, Did you fix the missing data like earned xch, expected xch, netspace, etc |
Followed instructions for installation.
Am running harvester and full node / dashboard on same host to test.
I used SCREEN to keep run_mtail.sh in the background.
Have imported JSON but all the graphs show "No data".
Apologies - first time with Grafana / Prometheus.
Suspect mtail is not running. Have reviewed run_mtail.sh and I note that when I try to execute at the prompt ./mtail I receive a "command not found" response.
The text was updated successfully, but these errors were encountered: