You are not reading the most current version of the documentation. If you want up-to-date information, please have a look at 3.7 .

The command

Scylla Monitoring Stack is container-based, the simplest way to configure and start the monitoring is with the command.

The script is a small utility that sets the dashboards and starts the containers with the appropriate configuration.

General Options

-h Help, Print the help, and exit.

–version print the current Scylla-Monitoring stack version, and exit.

-l local. Use the host network. This is important when one of the containers need access to an application that runs on the host. For example, when Scylla Manager runs on the localhost next to the monitoring. Because the monitoring applications run inside containers by default their local IP address ( is the container local IP address. You cannot use port mapping when using the -l flag

-A bind-to-ip-address Bind the listening-address to an explicit IP address.

-D encapsulate docker param Allows passing additional parameters to all the docker containers.

–auto-restart When set, Docker will automatically restart all the services inside the containers in case of a failure.

Alert Manager

alertmanager handles the alerts and takes the following parameters:

-m alertmanager-port Override the default Alertmanager port, this is done using port mapping, note that port mapping does not work when using the host network.

-r alert-manager-config By default, the Alertmanager takes its configuration from rule_config.yml in the prometheus directory. The -r flag overrides it to another file.prometheus

-C alertmanager-commands Allows adding an arbitrary command line to the alertmanager container starting command.