Docker Standalone
Prerequisite
- Self-Hosted SigNoz installed
Once you have successfully installed SigNoz on Docker Standalone, the following sections provide an overview of the activities that are required to successfully operate SigNoz.
Stop/Start SigNoz Cluster
To stop SigNoz cluster:
docker compose -f docker/clickhouse-setup/docker-compose.yaml stop
To start/resume SigNoz cluster:
docker compose -f docker/clickhouse-setup/docker-compose.yaml up -d
The stopped SigNoz cluster should resume and mount to the existing docker volumes.
Upgrade SigNoz Cluster
Use the commands below to sync to the latest release.
Checkout to
main
branch:git checkout main
Pull the
latest
changes from the SigNoz GitHub repository:git pull origin main
Go to
deploy
folder and run theinstall.sh
script:cd deploy && ./install.sh
In case you wish to upgrade the SigNoz cluster to a specific version, let's say v0.6.2
, follow the steps below:
Checkout to the v0.6.2 tag:
git checkout v0.6.2
Go to
deploy
folder and run theinstall.sh
script:cd deploy && ./install.sh
- Be careful with breaking changes across versions!
- There might be misconfiguration caused by version mismatch.
Uninstall SigNoz Cluster
Enter the following command to uninstall SigNoz:
docker compose -f docker/clickhouse-setup/docker-compose.yaml down -v
Running SigNoz without Sample Application
By default, docker-compose.yaml
includes a sample application setup. To run SigNoz without the sample application, instead of using docker-compose.yaml
, use docker-compose-minimal.yaml
in all previously mentioned commands.
For example,
docker compose -f docker/clickhouse-setup/docker-compose-minimal.yaml up -d
If you still see the HotROD services on the dashboard, wait for a few minutes, and the changes will be reflected.