Hello all 😁 I'm having some trouble setting up logspout on a different host. Following: https://signoz.io/docs/userguide/collect_docker_logs/ I have 2 servers, one is running signoz (Machine A) and the other (Machine B) is running my services in docker containers and which I want to mount logspout. Settings: (Machine A) docker-compose.yaml (snippet of otel-collector)

otel-collector:
    ports:
      # - "1777:1777"     # pprof extension
      - "4317:4317" # OTLP gRPC receiver
      - "4318:4318" # OTLP HTTP receiver
      - "2255:2255" # <------ Port opened for logspout comm

(Machine B)

docker run --net=host --rm --name="logspout" \
     --volume=/var/run/docker.sock:/var/run/docker.sock \
     gliderlabs/logspout \
     syslog+tcp://<machine_a_ip>:2255

---------------------- When starting logspout on (Machine B) de container fails with the output:

2025/02/05 14:27:32 !! dial tcp <machine_a_ip>:2255: connect: connection refused

Running netcat inside (Machine B):

nc -zv <machine_a_ip> 2255

nc: connect to <machine_a_ip> port 2255 (tcp) failed: Connection refused

Ok, expected, since logspout is already failing... Running netcat inside (Machine A)

nc -zv 0.0.0.0 2255

Connection to 0.0.0.0 2255 port [tcp/*] succeeded!

So from this I can understand that I have some problem with port 2255 on (Machine A), but: Running tcpdump on Machine A (that is running signoz) while starting logspout from the Machine B:

sudo tcpdump -i any port 2255

I get:

14:47:52.799030 eth0  In  IP static.****.your-server.34632 > static.<machine_a_ip>.2255: Flags [S], seq 2710839612, win 64240, options [mss 1460,sackOK,TS val 533319106 ecr 0,nop,wscale 7], length 0
14:47:52.799194 br-e99af481de3a Out IP static.your-server.34632 > 172.18.0.4.2255: Flags [S], seq 2710839612, win 64240, options [mss 1460,sackOK,TS val 533319106 ecr 0,nop,wscale 7], length 0
14:47:52.799207 veth62369ab Out IP static.your-server.34632 > 172.18.0.4.2255: Flags [S], seq 2710839612, win 64240, options [mss 1460,sackOK,TS val 533319106 ecr 0,nop,wscale 7], length 0
14:47:52.799254 veth62369ab P   IP 172.18.0.4.2255 > static.****.your-server.34632: Flags [R.], seq 0, ack 2710839613, win 0, length 0
14:47:52.799254 br-e99af481de3a In  IP 172.18.0.4.2255 > static.****.your-server.34632: Flags [R.], seq 0, ack 1, win 0, length 0
14:47:52.799279 eth0  Out IP static.<machine_a_ip>.2255 > static.****.your-server.34632: Flags [R.], seq 0, ack 2710839613, win 0, length 0

So the tcp is reaching Machine B but not being accepted on the container. Can someone tell me what am I missing? Thank for the help in advance 😁

Hello, I have a problem with SMTP for alertmanager. I have a certificate error : ts=2025-01-08T121302.432Z caller=api.go:814 level=error component=api version=v1 msg="API error: failed to send test message to channel (test-test mail)" err="server_error: send STARTTLS command: tls: failed to verify certificate: x509: certificate is valid for ubuntu.adret.retloc, not *******" I see the issue on GitHub but I don't know how to solveit. Can anyone help me please ? Thanks

Hello team, i hope you are alright, i need your support on this. I'm unable to filter logs based on service.name, i'm getting error

Aw snap :/ Something went wrong. Please try again or contact support.

By looking at the clickhouse logs, i can see 4 errors, all with same issue :

Code: 47. DB::Exception: Missing columns: 'resource_string_service$$name' while processing query

I'm using Signoz 0.54.0 deployed with chart 0.52.0. Full stack error in thread. Thank you in advance

Hi team, I saw the new version 0.55 include the log migration is released and I have read the migration guide. But before I have confidence to upgrade it. Can someone help explain more details about what’s the log change that breaks the previous log table and how does the migration work to make sure we are smoothly upgrade to new way to avoid us loose any existing logs.

I installed Signoz to a k8s cluster, configured it to receive logs, and setup two otel collectors to send data. Logs are being received, but the default logs filter 'K8S Cluster Name' is blank. In the otel collector/k8s-infra config, I set global.clusterName and clusterName, but that value does not get set as an attribute on the logs, and the 'K8S Cluster Name' filter doesn't work. How do I set cluster name?

When you follow the steps, you'd see there are many things where you can contribute, docs, frontend, backend, create an issue, and pick it up if you're interested in solving it. Since we are seeing many developers interested in contributing, and soon we'll start triaging them. For now, pick anything you like, and ask questions in the channel someone from SigNoz community will be happy to help you!

Hello, I'm running into an issue with exported labels. I have a kind cluster with a few services exposing metrics on a prometheus /metrics endpoint. I want SigNoz to run in this cluster, discover these services, and scrape from the metrics endpoints. With the following value overrides, I can see the correct metrics and services in SigNoz:

otelCollectorMetrics:

ports:

prometheus:

enabled: true

containerPort: 9464

servicePort: 9464

protocol: TCP

config:

receivers:

prometheus:

config:

scrape_configs:

- job_name: kubernetes-services

kubernetes_sd_configs:

- role: service

exporters:

prometheus:

endpoint: 0.0.0.0:9464

service:

pipelines:

metrics:

exporters: [clickhousemetricswrite]

I also want the OpenTelemetry Collector to expose a Prometheus endpoint. But as soon as I add "prometheus" to the list of exporters, I see recursively added labels with an "exported" prefix. For example, "exported_exported_job", "exported_exported_exported_job", "exported_exported_exported_exported_job", etc. Am I configuring the prometheus exporter incorrectly?

This message was deleted.

Hey folks - continuing from a previous thread I posted(https://community-chat.signoz.io/t/16364993/nginx-metrics-are-missing#4f844108-d7ee-4a37-970f-9e0744867093). I've ensured the Signoz annotations are added to my Nginx Ingress

Pods

, but the

k8s-infra

chart doesn't seem to scrape these; the

controller-

labels are missing from my self-hosted SigNoz cluster. Everything else seems to work fine. Would def appreciate any pointers!

This message was deleted.