Currently it's set to 20Gb and I see no straightforward way of changing that

@Prashant Shahi Any documentation available for Query Builder?

If I wants to convert PromQL query to Query Builder

exm

sum(rate(container_cpu_utilization{k8s_namespace_name!="kube-system"}[5m])) by (k8s_container_name,k8s_pod_name)

how can I write same in Query Builder

if any doc is there

it would help me

Hi, I would like to defiine

Alert channels

and

Alerts

in the config file which would be commited to git repo. I see there are

alertmanager.yml

and

alerts.yml

files for it, but not sure where should I mount those files so UI could automatically get notifications from them. Could anyone explain it, please?

Hello I am facing this issue whenever I want to see metric detail traces.

ts=2022-08-31T10:22:39.399416813Z caller=log.go:168 level=info msg="Completed loading of configuration file" filename=/root/config/prometheus.yml
2022-08-31T10:22:48.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 57.388µs
2022-08-31T10:22:48.913Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 91.352µs
2022-08-31T10:22:58.911Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 28.994µs
2022-08-31T10:22:58.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 29.987µs
2022-08-31T10:23:08.911Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 34.044µs
2022-08-31T10:23:08.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 68.438µs
2022-08-31T10:23:18.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 32.411µs
2022-08-31T10:23:18.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 165.58µs
2022-08-31T10:23:28.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 52.459µs
2022-08-31T10:23:28.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 60.634µs
2022-08-31T10:23:38.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 40.206µs
2022-08-31T10:23:38.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 15.829µs
2022-08-31T10:23:48.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 16.001µs
2022-08-31T10:23:48.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 33.143µs
2022-08-31T10:23:58.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 32.522µs
2022-08-31T10:23:58.913Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 35.286µs
2022-08-31T10:24:08.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 56.676µs
2022-08-31T10:24:08.913Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 19.336µs
2022-08-31T10:24:18.915Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 31.96µs
2022-08-31T10:24:18.916Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 13.445µs
2022-08-31T10:24:28.912Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 31.679µs
2022-08-31T10:24:28.913Z	INFO	app/server.go:189	/api/v1/version	timeTaken: 34.184µs

Readiness probe failed: Get "http://10.42.8.128:8080/api/v1/version": dial tcp 10.42.8.1288080 connect: connection refused also unable to fetch data from api/v1/services response:

{
  "data": null,
  "total": 0,
  "limit": 0,
  "offset": 0,
  "errors": [
    {
      "code": 500,
      "msg": "Error in processing sql query"
    }
  ]
}

I reinstalled in k8s multiple times. Updated repo and install again got same issue. Increases memory and cpu in yaml. Problem is still occurring.

@Prashant Shahi @Pranay Is there any way to configure SMTP service ?

I did not find in values.yaml

any place holder for it

So that when we invite any member, he will get invitation link automatically via email

I did not find it any where

@sudhanshu dev it is not supported yet.. https://github.com/SigNoz/signoz/issues/1540. We might look into prioritising this in a month

Thank you

Hey, I am unable to send metrics to the

otlp:
        protocols:
          grpc:
            endpoint: 0.0.0.0:4317

from outside the kubernetes cluster. I am using contour as an ingress. I also tried using httpproxy of contour. Neither of those worked for me.

Hi all, I am new to signoz. Does the clickHouse storage engine support distributed clusters?

Is there documentation for the SigNoz high availability deployment solution?

Hi everyone, I just discovered SigNoz. I'm trying to deploy it via Kubernetes by following the tutorial with Helm. Some pods are crashing because of an unsuccessful DB access : Logs from the pod my-release-signoz-otel-collector-ddb76f957-kxjp9 :

time="2022-09-01T12:49:09Z" level=info msg="Executing:\nCREATE DATABASE IF NOT EXISTS signoz_metrics\n" component=clickhouse
Error: cannot build pipelines: failed to create "clickhouselogsexporter" exporter, in pipeline "logs": cannot configure clickhouse logs exporter: code: 516, message: admin: Authentication failed: password is incorrect or there is no user with such name

Hello Team, Is there any way through which the my-release-signoz-otel-collector-pod ip will automatically gets updated under k8s deployment file, when my-release-signoz-otel-collector-pod gets restarted with any reason. I am using below key value parameter in my deployment files to capture signoz information. OTEL_EXPORTER_OTLP_ENDPOINT: <my-release-signoz-otel-collector-pod-ip>:4317 OTEL_RESOURCE_ATTRIBUTES: service.name=dispatcher-service

While running your application did you add

OTEL_LOGS_EXPORTER=otlp

env variable as described here https://signoz.io/docs/userguide/collecting_application_logs_otel_sdk_java/

@nitya-signoz After upgrading to latest SIgnoz version

kubectl get pods -n platform NAME READY STATUS RESTARTS AGE signoz-release-alertmanager-0 1/1 Running 0 5d23h signoz-release-clickhouse-operator-7648754fdf-pxtkz 2/2 Running 0 20m signoz-release-frontend-5d8d4bcf96-xcjhr 1/1 Running 0 5d23h signoz-release-frontend-76d7ff5895-kwpbx 0/1 Init:0/1 0 20m signoz-release-otel-collector-kbnvr 0/1 Init:0/1 0 20m signoz-release-otel-collector-metrics-57f4977457-xfh7h 0/1 Init:0/1 0 20m signoz-release-otel-collector-metrics-7df59bc9cd-hf4kq 1/1 Running 0 5d23h signoz-release-otel-collector-v97nc 0/1 Init:0/1 0 2m55s signoz-release-query-service-0 0/1 Init:0/1 0 20m signoz-release-zookeeper-0 1/1 Running 0 5d23h

most of the pods in init stage

any idea?

earlier I was getting below error

kubectl logs -f signoz-release-otel-collector-xfjbx -n platform Defaulted container "signoz-release-otel-collector" out of: signoz-release-otel-collector, signoz-release-otel-collector-init (init) 2022-09-05T065416.741Z info service/telemetry.go:103 Setting up own telemetry... 2022-09-05T065416.741Z info service/telemetry.go:138 Serving Prometheus metrics {"address": "0.0.0.0:8888", "level": "basic"} Error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": error connecting to primary db: dial tcp: lookup signoz-release-clickhouse on 172.20.0.1053 no such host 2022/09/05 065416 application run finished with error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": error connecting to primary db: dial tcp: lookup signoz-release-clickhouse on 172.20.0.1053 no such host