From c9af8bfa332b5bb20593083280ed5d5c5e72bd90 Mon Sep 17 00:00:00 2001 From: franck-dailymotion Date: Wed, 16 Oct 2024 09:17:08 +0200 Subject: [PATCH] docs: Metrics are available on different port on kubernetes --- docs/managing-dragonfly/monitoring.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/managing-dragonfly/monitoring.md b/docs/managing-dragonfly/monitoring.md index b4cebecd..7e5b7740 100644 --- a/docs/managing-dragonfly/monitoring.md +++ b/docs/managing-dragonfly/monitoring.md @@ -7,3 +7,14 @@ sidebar_position: 5 By default, Dragonfly allows HTTP access via its main TCP port (i.e, `6379`) and it exposes Prometheus compatible metrics on `:6379/metrics`. Check out this complete example of setting up a [Grafana Monitoring Stack with Dragonfly](https://github.com/dragonflydb/dragonfly/tree/main/tools/local/monitoring). + +** :warning: ** + +If you're using kubernetes, Metrics are also available on admin port `9999`. You may encounter this error with port `6379`: + +``` +* Request completely sent off +* Received HTTP/0.9 when not allowed +* Closing connection +curl: (1) Received HTTP/0.9 when not allowed +```