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

Debug endpoint to check peering status #130

Closed
hacdias opened this issue Apr 24, 2024 · 3 comments
Closed

Debug endpoint to check peering status #130

hacdias opened this issue Apr 24, 2024 · 3 comments
Assignees

Comments

@hacdias
Copy link
Member

hacdias commented Apr 24, 2024

It would be advantageous if we have a debug endpoint where we can check the peering status. This can be especially useful if we're using seed-based automatic peering.

The only way of checking it now is using GOLOG_LOG_LEVEL="peering=debug" and checking the debug logs.

@gammazero gammazero self-assigned this Nov 25, 2024
@gammazero
Copy link
Contributor

In #194 a new management endpoint was added that shows the current peers:

  • http://$RAINBOW_CTL_LISTEN_ADDRESS/mgr/peers returns a list of currently connected peers

I am not sure if this is exactly what you are looking for, but if it is please close this issue.

@hacdias
Copy link
Member Author

hacdias commented Nov 26, 2024

I think this issue was created when we introduced peering in Rainbow. The idea was to have an endpoint where we could properly monitor whether the instances were getting automatically connected to their peers (#111). Whether or not the current endpoint is enough, that's not for me to say.

@gammazero
Copy link
Contributor

I think this is handled in #194, unless there is a further request. If endpoint needs to be exposed outside of localhost, then is up to operator.

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

No branches or pull requests

2 participants