This message was deleted.

Hi SigNoz Team, I need a help to set up SMTP server details for email alert purpose, it would be great if anyone assist me to set up, i have tried all possibilities but didn't worked. I have selfhosted SigNoz on my ubuntu system through docker steps. Thanks, Ramana

Hi, just testing out Signoz integration with Vector. We use Vector for log shipping and currently I have Signoz self hosted on our K8s cluster. It looks like Vector has added opentelemetry sinks recently (https://vector.dev/docs/reference/configuration/sinks/opentelemetry/) and I'm trying to get this working but it doesn't appear to be successfully sending to Signoz, this is what I'm trying for my Vector sink. Any ideas?

service-signoz-sink:
  type: opentelemetry
  inputs: [ "service-transform" ]
  protocol:
    type: http
    uri: <http://signoz-otel-collector.signoz.svc.cluster.local:4318/v1/logs>
    method: post
    encoding:
      codec: json
    framing:
      method: newline_delimited
    headers:
      content-type: application/json
  healthcheck:
    enabled: true

Hi. We are playing around with external clickhouse setup (every other part of signoz runs on k8s), latest version of chart (0.56.2, signoz 0.58.2). When we use the default clickhouse user with empty password: externalClickhouse: host: 10.10.10.10 user: default password: "" everything works correctly, signoz deployment finishes, schema-migrator completes. But when we setup a password for the default user: user: default password: yyyy or password: "yyyy" or password: 'yyyy' schema migrator seems to complete part of migrations but then fails and goes into CrashLoopBack and timeouts with this error:

Error: failed to run squashed migrations: failed to run squashed migrations

code: 516, message: Received from 10.10.10.10:9000. DB::Exception: default: Authentication failed: password is incorrect, or there is no user with such name.

If we change the user, delete the deployment and helm install fresh - same situation, same error. We use the default clickhouse ports (8123, 9000) so we don't setup them in the yaml file. Connecting locally or externally to clickhouse instance on 10.10.10.10 with the default user or the other user and providing yyyy password - works without any issues. Any idea what we are doing incorrectly?

I am missing lot of logs from signoz, is there a way to find out why this is happening? I associate logs with traces, and even though traces are present, many times logs are not there. I am having k8s deployment, and sending logs from node.js application using pino-otel-transporter https://github.com/pinojs/pino-opentelemetry-transport

Hey Guys, I am trying to send alert🚨 notification over Email, I am getting some error of channel not being configured properly to send email for even a test alert. And I am not getting any mails even for an obvious conditions for alert.

Failed to send a test message to this channel, please confirm that the parameters are set correctly

This was the error message popped up when trying to set email channel and send a test mail Can you send me the procedure of setting mail based alerts, or does it require any prior SMTP configuration. Thanks and regards

This message was deleted.

How is it possible to take backup of alerts in Signoz? Using 0.37.

This message was deleted.

please has anyone exposed their otel-collector through nginx ingress before? i need help, here is my current settings

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
  name: signoz-otel-collector-grpc-ingress
  namespace: ops
  annotations:
    <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: nginx
    <http://nginx.ingress.kubernetes.io/grpc-backend|nginx.ingress.kubernetes.io/grpc-backend>: "true"
    <http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: "GRPCS"
    <http://nginx.ingress.kubernetes.io/proxy-buffer-size|nginx.ingress.kubernetes.io/proxy-buffer-size>: "128k"
    <http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: "true"
    <http://nginx.ingress.kubernetes.io/proxy-body-size|nginx.ingress.kubernetes.io/proxy-body-size>: "0"
    <http://nginx.ingress.kubernetes.io/proxy-connect-timeout|nginx.ingress.kubernetes.io/proxy-connect-timeout>: "300"
    <http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: "300"
    <http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: "300"
    <http://nginx.ingress.kubernetes.io/upstream-keepalive-timeout|nginx.ingress.kubernetes.io/upstream-keepalive-timeout>: "600"
    <http://nginx.ingress.kubernetes.io/upstream-keepalive-requests|nginx.ingress.kubernetes.io/upstream-keepalive-requests>: "100"
spec:
  rules:
  - host: <http://otelcollector.domain.com|otelcollector.domain.com>
    http:
      paths:
      - path: /
        pathType: ImplementationSpecific
        backend:
          service:
            name: signoz-otel-collector
            port:
              number: 4317
---
apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
  name: signoz-otel-collector-http-ingress
  namespace: ops
  annotations:
    ingressClassName: nginx
    <http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: HTTP
    <http://nginx.ingress.kubernetes.io/proxy-connect-timeout|nginx.ingress.kubernetes.io/proxy-connect-timeout>: "300"
    <http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: "300"
    <http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: "300"
spec:
  rules:
  - host: <http://otelcollector-http.domain.com|otelcollector-http.domain.com>
    http:
      paths:
      - path: /
        pathType: ImplementationSpecific
        backend:
          service:
            name: signoz-otel-collector
            port:
              number: 4318