How much memory should the query service need? I am running it with 512MB and it seems to be dying due to OOM errors. Does it need to scale according to how much clickhouse data there is or maybe there is a memory leak? On version 10.2

Hi @Pranay, I asked this question in general and thought its correct here. I have installed signoz in our gke environment. We are pulling our metrics using prometheus ( and alerts with alertmanager). I would like to explore signoz as APM. I am following link: https://signoz.io/docs/userguide/send-metrics/#enable-a-prometheus-receiver.

I don't see it working when I changed my configmap "kubectl describe configmap my-release-signoz-otel-collector-metrics -n platform" as described in the link

prometheus:
    config:
      scrape_configs:
      - job_name: otel-collector
        scrape_interval: 30s
        static_configs:
        - targets:
          - my-release-signoz-otel-collector:8889
          - localhost:8080

I use promql to check the metrics, but do not see anything in UI. Am I missing something?

Do you have any case studies for migrating from Datadog to Signoz? I’m interested in migrating a Datadog setup which uses about 400K metrics/month , and around 300 synthetics. Datadog works but is pricy, so I’m interested in replacing Datadog to reduce costs. Signoz came up in my web searches

Is it possible to use a statsd client to send metrics to Signoz: https://github.com/cactus/go-statsd-client#example? The datadog Go client is basically a fork of this client

@Craig Rodrigues we would be happy to help you migrate from DataDog. We also extend some dashboarding support to get started quickly. Let us know when you plan to take it forward. Also, we launched log management this week making signoz a single tool for all 3 pillars of observability

Hi team i am using tempo with otel collector with grpc ingestion and i am getting my tempo data in otlp format and it's encrypted, how can i decrypt the data to normal otel format?

I have attached the full error log file.

@주현태 can you share what you see on running this. https://signoz.io/docs/install/troubleshooting/

Hi

In the open telemetry collector

I am not getting k8s cluster name

k8s_container_cpu_limit{container_id="9d6a59b984b2e196b214accbfe3789c68aa04e925f99ccb32ae4feee7bf14eb9",container_image_name="fluent/fluent-bit",container_image_tag="1.9.1",k8s_cluster_name="",k8s_container_name="fluent-bit",k8s_namespace_name="*********",k8s_node_name="ip---49-147.ap-south-1.compute.internal",k8s_pod_name="fluent-bit-db2wp",k8s_pod_uid="67acfe9f-3a72-47b7-9f0a-4f763b68509e",opencensus_resourcetype="container"}

k8s_cluster_name us empty

Is there any k8s env variable that we can set

in the demon set

?

in this query

container_memory_usage{k8s_namespace_name!="kube-system"}

I wanted one AND operator here

with k8s_cluster_name="my-k8s"

like

Has anyone compared Victoria Metrics to SigNoz?

SigNoz is not supported on windows as of now.

👋 Hello, team!

Hi all, I am new to Signoz. Am facing an issue with sending traces to it from python code. Signoz

v0.10.2

was deployed on a GKE Autopilot cluster. I have added an Ingress each for the frontend (443 -> 3313) and for the collector (80 -> 4318) to access the frontend and the collector over the internet. To see if I can send traces, I used this code

<https://gist.github.com/dfrankow/f91aefd683ece8e696c26e183d696c29>

and started it like so and did a POST and GET to it as shared in that gist -

❯ python3 -m venv simple_server
❯ source simple_server/bin/activate
❯ python -V
Python 3.9.13
❯ pip install opentelemetry-distro
❯ pip install opentelemetry-exporter-otlp
❯ wget <https://gist.githubusercontent.com/dfrankow/f91aefd683ece8e696c26e183d696c29/raw/016714b21cb2172b43611aabe03e53249027bd84/simple_server.py>
❯ OTEL_RESOURCE_ATTRIBUTES=service.name=test_apm OTEL_EXPORTER_OTLP_ENDPOINT="http://<sub.domain.here>" opentelemetry-instrument --traces_exporter otlp_proto_http python3 simple_server.py 7000 127.0.0.1

The traces do not get sent and the logs seem to suggest that I necessarily need to open the GRPC port even though I am specifying

otlp_proto_http

above. Please suggest if I am missing something.

I’ve migrated a fair chunk of services to SigNoz in our test environment and have

929234

time series at the moment. The query service needed to have its memory increased to 3GB for the container to not crash due to OOM. Our PROD setup is much more extensive and has more traffic so will this need dozens of GB to operate the backend service? Is there anything I am doing wrong, I know there are optimizations coming but seems tough to handle this linearly increasing memory in terms of operations.