You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please explain your change in detail.
Add and "status" or "health" endpoint that provide fast results of the state of the node, like for example if is catching up or not, if stake or not, etc.
In this particular case I accept any kind of suggestion or advice, I was thinking to add status information that is not sensitive from tendermint layer that help a node runner or an automation tool to see/check if a node is running well.
Please provide a justification for your change.
There is no way currently to check the health of the node.
There is no way using pocket rpc to see if the node is catching up, but is if you know and use tendermint rpc, but people should be able to only point and use pocket node for anything around their nodes.
Timeline
After any discussion and ideas of what information this could expose safety, should be a trivial task of 1 day or 2.
The text was updated successfully, but these errors were encountered:
Please explain your change in detail.
Add and "status" or "health" endpoint that provide fast results of the state of the node, like for example if is catching up or not, if stake or not, etc.
In this particular case I accept any kind of suggestion or advice, I was thinking to add status information that is not sensitive from tendermint layer that help a node runner or an automation tool to see/check if a node is running well.
Please provide a justification for your change.
There is no way currently to check the health of the node.
There is no way using pocket rpc to see if the node is catching up, but is if you know and use tendermint rpc, but people should be able to only point and use pocket node for anything around their nodes.
Timeline
After any discussion and ideas of what information this could expose safety, should be a trivial task of 1 day or 2.
The text was updated successfully, but these errors were encountered: