-
Notifications
You must be signed in to change notification settings - Fork 40
Prometheus exporter for IPFS API #129
Comments
too big? |
While factoring out go-libp2p it became clear that the current integration isn't waterproof, i.e. go-libp2p would be depending on the prometheus client code. I didn't wanna justify this kind of bloat right at the birth of libp2p, and @whyrusleeping was happy enough to rip it out. |
Between no metrics and bloat we should be choosing bloat right now. gx should make it not a problem to depend on this. gx should only be downloading source code, so it should be pretty light. (and yes Go binaries are bloated in general) |
We should be adding more metrics, not removing them. I'm happy with whatever, but we shouldn't have a long interruption in metrics-- which is likely to happen if we don't make this an atomic swap (i.e. have something to replace it before removing it) |
We have the proper IpfsCollector in go-ipfs now, which so far collects
|
We're about to rip prometheus out of go-ipfs, and need something to poll the API for this info.
Examples:
ipfs swarm peers | wc -l
:5001/debug/pprof
The text was updated successfully, but these errors were encountered: