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
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: