SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

SigNoz Community

Hi, just installed standalone version on docker/ubuntu. After reboot containers are down. I could change `compose...yaml` to `restart:always`  but then I will have conflict with new updated version on git and git pull will be shout on me. How to do it without dangling with files from git?

It is a known issue that some of the containers go down when the machine reboots (expected or unexpected).

You could create your own `custom-main` branch and sync upstream `main` whenever desired.

Or make sure that instruction to bring up SigNoz cluster is added to your machine startup script.

Thanks for the response. Can I ask why `restart` setting in docker-compose is not set as `always` ? :slightly_smiling_face:

<@U02NBMHMJ9L> <@U02SS3ZAMKQ> The ability for Signoz to come back online properly after system reboot is key for production system. If AWS were to reboot our EC2 instance running Signoz for any reason (e.g. faulty hardware), we might not know Signoz was not running until we tried to access Signoz, potentially losing many hours of metrics/logs. We would appreciate if Signoz team could look into this for an upcoming release to enhance reliability.