-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
refactor(rcmgr): use default libp2p rcmgr metrics #9947
Conversation
Not sure why sharness is failing. Has something to do with Prometheus metrics. I don't have a sharness setup locally, so I won't be able to debug this. I'd also argue (again) that it doesn't make sense to have any test that asserts what metrics downstream libraries are exposing. |
Triage note: @Jorropo will take a look |
3ba1080
to
cd25750
Compare
61c83f0
to
887c036
Compare
we no longer expect those extra ones
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a nice cleanup.
The sharness was failing because we have early warning when exposed metrics change, and this PR introduced diff:
-libp2p_rcmgr_memory_allocations_allowed_total
-libp2p_rcmgr_memory_allocations_blocked_total
-libp2p_rcmgr_peer_blocked_total
-libp2p_rcmgr_peers_allowed_total
Rebased, updated tests and added changelog entry informing people about removal, and that Kubo switched to upstream ones.
Once CI is green, will ship in 0.33.
Removes the bespoke rcmgr metrics with the default libp2p metrics. This allows us to use the libp2p-maintained dashboard on all of our Grafana instances.
It would be great if this could be merged for the v0.21 release. There've been quite a few instances recently where libp2p dashboards have helped us pinpoint a problem. Not having rcmgr metrics has made debugging more complicated than necessary.