Discussing SigNoz Start Up Times
TLDR Kareem questioned long SigNoz start up times. Yash rV, Chitransh, and Davide confirmed it as normal.
Powered by Struct AI
5
3mo
Solved
Aug 09, 2023 (4 months ago)
Kareem
Kareem
06:58 PMI am just starting to use SigNoz. I am using the self-hosted version which I installed using clickhouse-setup/docker-compose. That was smooth. However, there were two long start up times. clickhouse took about 30 seconds. And the query-service took another 30 seconds. Is this expected? Thank you. I am running in a recent version of Ubuntu.
✔ Network clickhouse-setup_default Created 0.0s
✔ Container zookeeper-1 Sta... 1.2s
✔ Container hotrod Started 1.3s
✔ Container load-hotrod Sta... 1.0s
✔ Container clickhouse Heal... 32.1s
✔ Container clickhouse-setup-otel-collector-1 Started 32.9s
✔ Container clickhouse-setup-otel-collector-metrics-1 Started 32.7s
✔ Container query-service H... 63.1s
✔ Container clickhouse-setup-alertmanager-1 Started 63.4s
✔ Container frontend Starte... 63.8s
Yash rV
Yash rV
09:27 PMYes, I think It's fine if you are running SigNoz on your machine.
Aug 10, 2023 (3 months ago)
Kareem
Kareem
05:26 AMty
Chitransh
Chitransh
05:38 AMYes. I can confirm the same while using darwin.
Davide
Davide
09:12 AMyes, because of dependencies between services, i guess.
SigNoz Community
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
Indexed 1023 threads (61% resolved)
Similar Threads
Troubleshooting SigNoz Local Setup on M1 Mac
Sindhu had issues with their local SigNoz installation using Docker on an M1 Mac. Srikanth helped diagnose the problem. It was resolved by manually starting the ClickHouse container and then starting SigNoz via Docker Compose in the terminal.
14
8mo
Solved
Troubleshooting SigNoz Setup Issue
onfla_11 and Caio experience difficulty setting up SigNoz due to clickhouse container errors. Alfredo suggests checking TCP ports.
3
1mo
SigNoz Install Script Errors
Nishant encountered errors with the install.sh script. Prashant suggested using `bash install.sh` or `./install.sh` instead of `sh`.
7
7mo
Solved