-
-
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
Collecting Process Metrics #1418
Comments
As goals, i think we should try for something:
I have one proposal with two possible implementation approaches. The idea is to make one module that has metrics stored at particular paths, so things like From an interfaces standpoint, the idea i have would be to make one (So, instead of having a package implement its own collection and expose functions to get the metrics, the package is given a metrics object (global or passed in), that they write their metrics to.) IIRC, https://github.com/ipfs/go-ipfs/pull/1163/files does some namespacing of metrics. |
Some of the metrics bitswap-ml may need: ipfs-inactive/bitswap-ml#1 |
I had some plans to write a 'bs-top' that would be a process monitor for bitswap. It would essentially register for notifications from bitswap, and be notified of what each worker is doing as soon as it starts doing it. That way, we could have a nice interface that shows live information about what bitswap is doing. Although, that may be tangental to the metrics we're discussing here. |
@whyrusleeping sweet! i want it to. we should make these "dashboards" for different subsystems (dht, bitswap, repo, api, gateway, etc) (top is a dashboard) |
|
maybe we want to discuss a general strategy for dashboards somewhere? We could either do them through notifications, which might be obnoxious, or we could do it through our new eventlogs API. and just have bitswap emit eventlogs for the dashboard |
We're getting to the point where we want to collect a large swath of metrics. This is for use cases like:
So far, some metrics work includes #457 and #1163. Interested people include: @whyrusleeping @lgierth @rht @Heems @jbenet
We should use this issue to track:
The text was updated successfully, but these errors were encountered: