-
Notifications
You must be signed in to change notification settings - Fork 3
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
Host metrics - mac #16
Comments
On it! |
Making good progress here: sigp/lighthouse#1848 I'll come back to it tomorrow morning to finish it off. |
I've added this feature here: sigp/lighthouse#1848. @daniel-flex I have sent you a binary privately. The output looks like this: "cpu_status": {
"status": "ok",
"message": "CPU below 85%",
"gauge_pct": 0.12
},
"memory_status": {
"status": "ok",
"message": "1 GB available memory",
"gauge_pct": 40.7
},
"eth1_status": {
"status": "error",
"message": "Eth1 sync is disabled, use the --eth1 CLI flag to enable. Eth1 is only required for validators.",
"gauge_pct": 0
},
"p2p_status": {
"status": "warn",
"message": "Low peer count (3).",
"gauge_pct": 5.45
},
"database_status": {
"status": "ok",
"message": "/home has sufficient capacity.",
"gauge_pct": 64.53
} |
@paulhauner have connected this up the the frontend in commit #32ab08d. It's currently coming from the BN api: /lighthouse/health (I was previously getting it from the VC api). Most of the data is available, but I think this endpoint could be updated slightly, like adding the beacon node health/status info, plus potentially merging/combining some of the fields (as I'm currently doing it on the frontend right now). Can discuss further if you want - I have some ideas about it. Also, polling timeout can be controlled via an env variable to give the user more control - if the lighthouse client is local then polling could be faster, and if remote then slower, for example. Defaults to 5000ms. |
Need host metrics for mac - currently unavailable.
https://lighthouse-book.sigmaprime.io/api-vc-endpoints.html#get-lighthousehealth
The text was updated successfully, but these errors were encountered: