[root@myhostname deploy]# ./install.sh 👋 Thank you for trying out SigNoz! Detecting your OS ... 👉 Two ways to go forward 1) ClickHouse as database (default) 2) Kafka + Druid setup to handle scale (recommended for production use) ⚙️ Enter your preference (1/2):1 ✅ You have chosen: clickhouse setup Starting Docker ... ./install.sh: line 225: [: too many arguments :large_yellow_circle: Pulling the latest container images for SigNoz. To run as sudo it may ask for system password sudo: docker-compose: command not found 🔴 The containers didn't seem to start correctly. Please run the following command to check containers that may have errored out: sudo docker-compose -f docker/clickhouse-setup/docker-compose.yaml ps -a or reach us on SigNoz for support https://join.slack.com/t/signoz-community/shared_invite/zt-lrjknbbp-J_mI13rlw8pGF4EWBnorJA ++++++++++++++++++++++++++++++++++++++++ 📨 Please share your email to receive support with the installation Email: mymailid@gmail.com We will reach out to you at the email provided shortly, Exiting for now. Bye! 👋

:large_yellow_circle: Pulling the latest container images for SigNoz. To run as it may ask for system password Pulling clickhouse ... error Pulling query-service ... error Pulling frontend ... error Pulling otel-collector ... error Pulling hotrod ... error Pulling load-hotrod ... error ERROR: for clickhouse Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving ERROR: for query-service Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving ERROR: for hotrod Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving ERROR: for frontend Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving ERROR: for otel-collector Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving ERROR: for load-hotrod Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.73.90.2:53: server misbehaving 🔴 The containers didn't seem to start correctly. Please run the following command to check containers that may have errored out: docker-compose -f docker/clickhouse-setup/docker-compose.yaml ps -a or reach us on SigNoz for support https://join.slack.com/t/signoz-community/shared_invite/zt-lrjknbbp-J_mI13rlw8pGF4EWBnorJA ++++++++++++++++++++++++++++++++++++++++

@User https://github.com/SigNoz/signoz-k8s-helm-operator - May be you can check this out - as per our discussion in the community call

hey @User @User welcome to SigNoz community 🙂 Would love to know what go you interested in SigNoz

Hey folks 👋 Looking for a full stack/backend founding engineer to join our team at SigNoz. You will be part of the first few hires in our team and will have the opportunity to own a significant part of the product. This is an opportunity to work on core developer infra open source product - and would love to chat with folks who are excited by this If you know any dev friend who would be interested in this, please connect us or ask him/her reach out to me on pranay@signoz.io

Hi Team, can anyone say about how to integrate signoz in existing dockerfile for passing application data as an agent to ui of signoz or how is the flow looking to test it out

hey @User @User @User @User Welcome 👋

would love to know what got you interested in SigNoz

Hi 👋, I was wondering does SigNoz uses query engine apart from Prometheus, https://github.com/SigNoz/signoz/blob/main/pkg/query-service/app/clickhouseReader/reader.go#L47 for the clickhouse db?

and one more thing that how to run the application as after running with the OTEL_. command which is given in the documentation simply hides the console and data logged to it

I mean Node.js app

can you tell me how I can set these variables from inside the application

Hi everyone, I would like share my recent work. Created a FastAPI sample app with SigNoz integration. https://github.com/sureshdsk/sample-fastapi-app

It's meant for going to X-Ray, but it has an OTLP exporter. It seemed to be to be a good way to get additional insights into your AWS resources in SigNoz, like seeing your SQS messages on the AWS side in your traces

but not able to get Java code level metrics at function level

the total time is not adding up from the trace

Is there somewhere that we can see the near term roadmap? I looked in Discussions, but didn't find one

@User I am observing the data available in Signoz not available frequently, sometimes it auto recovers and sometimes its a complete loss

can anyone help me create an api so that I can get information about the errors in the applications connected to SigNoz

Hi there! I going thru docs (https://signoz.io/docs/), trying to understand SigNoz features for a simple hello-world app. any pointers ? thanks!

Has anyone used the AWS X-Ray Python SDK to get distributed traces that go across SQS/SNS in SigNoz?

is signoz a replacement for prometheus, grafana and jaeger?

Hi there ! Got into SigNoz after looking for an open source complete stack o11y platform... and really glad to see it... After playing around a bit (tried running the flask demo app), I was wondering if there is any intent to add some more (pretty basic in my opinion) OTEL_RESOURCES_ATTRIBUTES into account in the UI... I imagine how good would it be to be able to filter interesting services by their namespace for example (service.namespace in otel's semantic conventions), or maybe the version of a service - in order to be able to correlate bad deployments to some monitored signal... (service.version) Does anyone know about a reason not to add / intent to add a usage of these attributes ?

@User interesting idea. Do you mean only being able to see services based on these filters or also filter traces based on these attributes?

Hey there, I'm the main developer behind https://plausible.io. I'm kinda shopping around for a monitoring tool to set up for our infrastructure (Elixir apps, ClickhouseDB, probably adding Redpanda). Signoz looks really neat, I will probably play around with it soon. I hope the rest of the ecosystem catches up and starts supporting OpenTelemetry better.

@User Currently, we are more focused on "after the deployment" use case - where you need to monitor how your deployed apps are doing. But you are right, shouldn't be very difficult to get into the during development use case. Curious, what are the main use cases fo you use Sentry currently for?

Right we have errors and exception data...but the complete request with headers is not there with opentelemetry libs but should be easily extendible