@Prashant Shahi let me know once you are available to sort out the deployment issue with latest helm chart

@Umang Bhalla you can use this promQL query for p75 in custom dashboard

histogram_quantile(0.75, sum(rate(signoz_latency_bucket{service_name="workflow-service", span_kind="SPAN_KIND_SERVER"}[5m])) by (le))

👋 What's the default user/pass for the docker standalone setup?

After upgrading from 0.9 to 0.10, I noticed that the query-service crashes with an OOM error, though this isn't directly related to the upgrade itself, I think it's more just because the query-service was restarted. There's a large memory growth on load, to around 2.9GB RSS, which appears to be a fetch/cache of trace information from the DB:

[pid 754622] read(12, "espace\":\"svc-uat\",\"kubernetes_pod_name\":\"graphql-be-9f6b79d49-9tb4n\",\"le\":\"1\",\"pod_template_hash\":\"9f6b79d49\",\"reporter\":\"destination\",\"request_protocol\":\"http\",\"response_code\":\"200\",\"re"..., 1048576) = 32768

[pid 754622] read(12, "source_workload_namespace\":\"istio-system\"}\377\f{\"__name__\":\"istio_response_bytes_bucket\",\"app\":\"istio-ingressgateway\",\"chart\":\"gateways\",\"connection_security_policy\":\"unknown\",\"controller_revisio"..., 1048576) = 32768

[pid 754622] read(12, "ion_service\":\"claimform-gen.svc-prod.svc.cluster.local\",\"destination_service_name\":\"claimform-gen\",\"destination_service_namespace\":\"svc-prod\",\"destination_version\":\"v1\",\"destination_"..., 1048576) = 32768

What is the query-service fetching from the DB and caching in memory during the initialisation phase? I'm trying to figure out what memory sizing I really need to use for the query-service and whether that's going to grow significantly if I push more data into Clickhouse.

Hi everyone, 1- for microservices application, does Application here refer to one service ? or does it refer to a cluster which contain multiple services like in instana ? 2- is it possible to have a section for all called endpoints for all services as sometimes we receive questions from our dev team regarding certain endpoints and then we need to know which microservices these endpoints belongs to ?

In terms of deploying the SigNoz containers which ones can not be scaled? I assume the frontend and query-service can be scaled to N replicas while the alertmanager can only have 1 instance?

Hi Team, How do I disable self signup option? right now in the login screen it allows to create user for anyone. I want to create the user from Admin login only.

Hi Team, I instrumented one Spring Boot application to to SigNoz, I can see trace and its details in SigNoz/Trace section. But service name is coming as "unknown_service:java" did I missed anything? Here is my java agent info -javaagent:/opt/signoz_apm_jar/opentelemetry-javaagent.jar -Dotel.metrics.exporter=none -Dotel.exporter.otlp.endpoint=http://10.10.2.9:4317 -Dotel.resource.attributes="service.name=javaapp"

Hello. I'm trying to run Signoz on Raspberry Pi 4B on Ubuntu 20.04 in docker (docker-compose), but two containers won't start (frontend and alertmanager).

CONTAINER ID   IMAGE                                        COMMAND                  CREATED         STATUS                          PORTS                                                                            NAMES
d5dc1809f74f   signoz/frontend:0.10.0                       "nginx -g 'daemon of…"   7 minutes ago   Restarting (1) 44 seconds ago                                                                                    frontend
61b81a776ded   signoz/alertmanager:0.23.0-0.1               "/bin/alertmanager -…"   7 minutes ago   Restarting (1) 47 seconds ago                                                                                    clickhouse-setup_alertmanager_1
279f2c81dcd5   signoz/query-service:0.10.0                  "./query-service -co…"   8 minutes ago   Up 8 minutes (healthy)          8080/tcp                                                                         query-service
d8304bed592e   signoz/otelcontribcol:0.45.1-1.1             "/otelcontribcol --c…"   8 minutes ago   Up 8 minutes                    0.0.0.0:4317-4318->4317-4318/tcp, :::4317-4318->4317-4318/tcp, 55679-55680/tcp   clickhouse-setup_otel-collector_1
cdef746f2201   signoz/otelcontribcol:0.45.1-1.1             "/otelcontribcol --c…"   8 minutes ago   Up 8 minutes                    4317/tcp, 55679-55680/tcp                                                        clickhouse-setup_otel-collector-metrics_1
a26416c81131   clickhouse/clickhouse-server:22.4.5-alpine   "/entrypoint.sh"         9 minutes ago   Up 8 minutes (healthy)          8123/tcp, 9000/tcp, 9009/tcp                                                     clickhouse-setup_clickhouse_1
e97a6050f4b9   jaegertracing/example-hotrod:1.30            "/go/bin/hotrod-linu…"   9 minutes ago   Up 8 minutes                    8080-8083/tcp                                                                    hotrod

Ports

3301

,

80

and

9093

are not occupied in the system. Can someone help me sort this out?

Hi @Ankit Nayan, is there any way to import alerts from yaml or some kind of configuration into signoz ?

Any documents or idea about signoz resources for kubernetes deployment

After deployment of signoz our kubernetes cluster resources utilisation increased

@Duncan Boag Does it restart with OOM or different reason? How much data gets ingested and what are the resource limits for the pod?

For this file here, what files are needed to run the query-service within docker? Do I need

alerts.yml

at all or can i omit the files altogether? From my understanding the query-service acts as the prometheus server and stores the alerts in the SQLite DB on the filesystem? Also I noticed

alertmanager.yml

seems to be unused, is this needed anywhere? Also does SigNoz support environment vars in this file as I want to be able to replace the clickhouse domain, user, password without exposing that in the file I mount into the container (

prometheus.yml

)

Hi does the signoz/otelcontribcol supports prometheusremotewrite exporter?

Hello, i have a couple of questions if anyone can help

getting this error in query service after upgrading to 0.10

2022-08-03T18:59:21.389Z	ERROR	clickhouseReader/reader.go:102	failed to initialize ClickHouse: error connecting to primary db: dial tcp 100.70.132.148:9000: connect: connection refused

Just noticed in my custom clickhouse cluster that the SigNoz tables are not created on every node, what is the recommended approach to get all the tables to align across all the Clickhouse nodes? I’m trying to get HA but have noticed most of the push is to run 1 instance of clickhouse atm. Does that scale well, is a cluster overkill?

I didn't find any Prometheus in signoz

R u using Prometheus?

Bcz all the dashboard written in promql

Could you please help me in that?

Or u just use promql as query language

hey @sudhanshu dev we primarily use PromQL as the query language You can also create dashboard with Query builder, which will create native clickhouse queries. We provided PromQL support because many users are famiiar with PromQL and sometimes have dashboards written in that

Thank you

Hello. I have some problems with tracing section in signoz, could u explain me what’s wrong. More in thread

Is it possible to instrument with JBOSS Server? Currently I had Tomcat version

Hi Team. I am trying to install 2 signoz app in the same k8s cluster. But, getting following error message.

Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "clickhouse-operator-signoz" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>" must equal "platform-qa": current value is "platform"

Can anyone suggest how to install 2 signoz in same k8s cluster but difference namespace. I am using AWS EKS 1.18.20

Seems the query service hardcodes the alertmanager URL to always be http://alertmanager:9093/api and not use what is supplied in the prometheus.yml file. Is this intended? Seems I need to use this other env var to get it to use the actual alertmanager URL?