-
Notifications
You must be signed in to change notification settings - Fork 89
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
Guide for libp2p node monitoring #158
Comments
The rust-libp2p metrics module with an example as well as a Grafana dashboard can be found here: https://github.com/libp2p/rust-libp2p/tree/master/misc/metrics |
@mxinden : are you suggesting our new docs page should link to https://github.com/libp2p/rust-libp2p/tree/master/misc/metrics ? I think it's great that it shows what an example dashboard can look like by linking to https://kademlia-exporter.max-inden.de/d/Pfr0Fj6Mk/rust-libp2p . Other questions/observations though:
|
Yes. It links to the dashboard and the examples directory.
That is my intuition, given that there is an
I am fine with it, though I am not sure how much help the docs are.
It is a convention to have an |
This is being handled in #160 |
Parts related to resource mgmt are addressed in https://docs.libp2p.io/reference/dos-mitigation/#monitoring-your-application We have a metrics effort in go-libp2p started, we can include this as a part of that. Therefore closing in favor of libp2p/go-libp2p#1356 |
Done Criteria
There is a easily discoverable way for a libp2p node operator to find the monitoring options available to them for the libp2p implementation they are using (e.g., new docs section/page at https://docs.libp2p.io/monitoring).
Why Important
libp2p implementations have various ways to view node health. This information is usually buried within language-specific docs, which can be harder to discover.
Notes
This page is expected to be minimal, mostly providing links to the relevant documentation for specific implementations for things like "how to enable Granafa dashboards".
There should likely be some linking from the docs generated from #153 as well.
The text was updated successfully, but these errors were encountered: