Skip to content

Commit

Permalink
Update docs/source/upgrade/upgrade-guide-from-monitoring-4.x-to-monit…
Browse files Browse the repository at this point in the history
…oring-4.y.rst

Co-authored-by: Tzach Livyatan <[email protected]>
(cherry picked from commit f57c81c)
  • Loading branch information
amnonh committed Jan 3, 2024
1 parent 48f21e9 commit ad3404a
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -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 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.
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.

.. caution::

Expand Down

0 comments on commit ad3404a

Please sign in to comment.