From af93c83f51c7f3659924763f2e4a7807eb08fa16 Mon Sep 17 00:00:00 2001 From: Amnon Heiman Date: Wed, 3 Jan 2024 13:21:46 +0200 Subject: [PATCH] upgrade-guide-from-monitoring-4.x-to-monitoring-4.y: fix typo (cherry picked from commit 061265adb43f906a7441ed4cc7eb9dc7253bcb26) --- .../upgrade-guide-from-monitoring-4.x-to-monitoring-4.y.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/upgrade/upgrade-guide-from-monitoring-4.x-to-monitoring-4.y.rst b/docs/source/upgrade/upgrade-guide-from-monitoring-4.x-to-monitoring-4.y.rst index 59fd4f9a1b..95cec1d4ef 100644 --- a/docs/source/upgrade/upgrade-guide-from-monitoring-4.x-to-monitoring-4.y.rst +++ b/docs/source/upgrade/upgrade-guide-from-monitoring-4.x-to-monitoring-4.y.rst @@ -40,7 +40,7 @@ ScyllaDB-monitoring reads from ScyllaDB itself, from node_exporter for OS-relate Almost always, those targets use their default ports, and all share the same IP. If you use the default port number, we recommend using the target file without ports and letting ScyllaDB monitoring add the default port number. -If the ScyllaDB Mmanager agent and node_exporter are running next to ScyllaDB on the same host (the default installation), use one target file for scylla_server, and the ScyllaDB monitoring will use that file with the correct ports for each target. +If the ScyllaDB Manager agent and node_exporter are running next to ScyllaDB on the same host (the default installation), use one target file for scylla_server, and the ScyllaDB monitoring will use that file with the correct ports for each target. .. caution::