Scylla University Live | Nov 9 (AMERICAS), Nov 10 (EMEA and APAC) Free Virtual Training Event
Learn More

The command


You are not reading the most recent version of this documentation. Go to the latest version of Scylla Monitoring Stack Documentation.

As Scylla-Monitoring is container-based, the simplest way to configure and start the Scylla Monitoring Stack 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 Scylla Monitoring Stack. Because the Scylla Monitoring Stack 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.


-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 override it to another file.prometheus

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