-
Notifications
You must be signed in to change notification settings - Fork 28
Failed to get TCP info getsockopt: not implemented #106
Comments
I noticed this seems to be a windows only issue, but this issue gives us a bit of concern. |
Closed by #93 which is in https://github.com/libp2p/go-tcp-transport/releases/tag/v0.2.8. As for the more general "how do I disable metrics" question I'll defer to @marten-seemann and if you'd like you can open a new issue. However, IIRC in this particular case the only way to trigger this error message on Windows is if you explicitly called the prometheus metrics collection. |
Metrics collection can currently not be disabled, as for all other libp2p / IPFS systems. So far, I haven't seen any benchmark that showed a significant performance impact of metrics collection in our stack (but I can be convinced otherwise by data). |
After updating prysm to a recent version of libp2p, many users are reporting this log. It seems to have something to do with metrics and it is a cause for concern.
It seems to be coming from this line: https://github.com/libp2p/go-tcp-transport/blob/v0.2.4/metrics.go#L135
How can we disable this metrics collection?
What is this log about?
Tracking in Prysm here: prysmaticlabs/prysm#9733
The text was updated successfully, but these errors were encountered: