Skip to content
This repository was archived by the owner on Dec 20, 2024. It is now read-only.

Commit 8c6feee

Browse files
committed
add docs about other exporters
Signed-off-by: yeya24 <[email protected]>
1 parent d200985 commit 8c6feee

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/user_guide/monitoring.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,4 +131,10 @@ requestCounter.WithLabelValues("200").Inc()
131131

132132
This function will auto-register metrics to Prometheus default registry and you can get `dragonfly_supernode_http_requests_total{code,handler,method}` in /metrics endpoint. Here we also add prefix `dragonfly` to metrics name by default. If you want to learn more about how to use these metrics after getting them, please check [prometheus/client_golang](https://github.com/prometheus/client_golang).
133133

134-
As for naming of metric and label, it is better to follow the best practice. We suggest you to check this [metric and label naming](https://prometheus.io/docs/practices/naming/) guide for more detailed information.
134+
As for naming of metric and label, it is better to follow the best practice. We suggest you to check this [metric and label naming](https://prometheus.io/docs/practices/naming/) guide for more detailed information.
135+
136+
### Integrating with other exporters
137+
138+
In order to monitor the over-all status of Dragonfly components, you may need to use other exporters. Prometheus itself has a huge ecosystem, including all kinds of exporters with different utilities. You can check [exporters](https://prometheus.io/docs/instrumenting/exporters/) for more information.
139+
140+
If you want to monitor the io status and network traffic of supernodes, we recommend you to use [node_exporter](https://github.com/prometheus/node_exporter).

0 commit comments

Comments
 (0)