This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
generated from ipfs/ipfs-repository-template
-
Notifications
You must be signed in to change notification settings - Fork 20
Expose the same metrics as Kubo #8
Milestone
Comments
@gmasgras is that all you need for drop-in replacement? Is there a place we can find all necessary metrics, to double-check we did not miss anything? |
for caboose preference for using Prometheus metrics directly versus opencensus? |
Here is a list of metrics we're currently using for our dashboards and alerts
|
Of these, only
are relevant |
Thanks! Hm.. it looks like we don't use existing metrics for directory listings, nor blocks, cars, and miss metrics for newly added types like JSON/CBOR/IPNS. We'll clean this up in ipfs/boxo#154 and then document all metrics exposed by |
Last one landed in #18 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Kubo Gateway exposes a bunch of metrics on RPC port: http://127.0.0.1:5001/debug/metrics/prometheus
bifrost-gateway should do the same
Details
We already have the some code extracted from Kubo:
https://github.com/ipfs/go-libipfs/blob/302b2799386dea7afb72ba0b4c32a5c427215d06/gateway/handler.go#L220-L262
We need to also move things from
MetricsCollectionOption
:https://github.com/ipfs/kubo/blob/14649aa8ba8d7612ce9e35bba776fe7e7498b343/core/corehttp/metrics.go#L79
While at it, we should fill the gaps mentioned in ipfs/boxo#154
The text was updated successfully, but these errors were encountered: