found the issue

statefulset-controller create Pod chi-signoz-release-clickhouse-cluster-0-0-0 in StatefulSet chi-signoz-release-clickhouse-cluster-0-0 failed error: pods "chi-signoz-release-clickhouse-cluster-0-0-0" is forbidden: error looking up service account platform/clickhouse-instance: serviceaccount "clickhouse-instance" not found

but I have the SA

signoz-release-alertmanager 1 18d signoz-release-clickhouse-instance 1 29m signoz-release-clickhouse-operator 1 29m signoz-release-frontend 1 18d signoz-release-otel-collector 1 18d signoz-release-otel-collector-metrics 1 18d signoz-release-query-service 1 18d

but with diff name

it should use signoz-release-clickhouse-instance

this SA

Hi Team, We are trying to deploy signoz on an EKS cluster on AWS. We followed the steps mentioned here - https://signoz.io/docs/install/kubernetes/aws/ But otel-collector, otel-collector-metrics and query-service containers are stuck in CrashLoopBackOff state And we are getting below errors - ERROR clickhouseReader/reader.go:113 failed to initialize ClickHouse: error connecting to primary db: code: 516, message: admin: Authentication failed: password is incorrect or there is no user with such name Can anyone please help, if this is a version issue, and provide version numbers to use?

I think this is related to new version

bcz in earlier version it picked the service account

@Prashant Shahi Do we need to pass any parameter for it

@sudhanshu dev I see the issue you reported occurs only when cold storage is enabled. will make a quick release with the fixes.

Ok

Will it take time or soon u will fix it?

Also, can we have a better color distribution please. After a certain count, everything goes to red

hi team we use k6 for performance benchmarking and result integration is done using a prometheus “remote write” endpoint. How do we achieve the same using open telemetry prometheus receiver as it does not support remote write and read? any workaround strategy ?

Hello 🙂

How can i clean logs / traces history in signoz ?

Hello Guys, We have deployed signoz on our environment with k8s and in signoz we have integrated many services from QA and DEV environment and bcoz of which we can see many traces and application api hits are coming to signoz dashbaord. So can anyone help me how much data it can save (like any GB sizes) As i have used k8s to deploy sigonz and my application is also running on k8s. I can see below listed pvc. [ec2-user@ip- ~]$ kubectl get pvc -n platform NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE data-my-release-zookeeper-0 Bound pvc-4308e74a-3348-4f30-9728-b57e936cdfab 8Gi RWO gp2 21d data-volumeclaim-template-chi-signoz-cluster-0-0-0 Bound pvc-65d9c2d4-bf60-415b-b4bc-badb01b5e97c 20Gi RWO gp2 21d signoz-db-my-release-signoz-query-service-0 Bound pvc-a6018216-f84d-4313-8073-3f4ae6047167 1Gi RWO gp2 21d storage-my-release-signoz-alertmanager-0 Bound pvc-76e05df3-d508-4075-a1c9-c94770c3edaf 1Gi RWO gp2 21d [ec2-user@ip- ~]$

Hi Team, Is there any way to remove defaults sample apps from application section?

Is there any way to read s3 cold storage data?

As I can see data is not in readable format

@Prashant Shahi @Ankit Nayan @Pranay

Hey @sudhanshu dev 👋 any reason for viewing the raw data in S3?

We are running with default configuration.

I hope you are running signoz outside the resource limits of the application. Let's say, signoz in 1 cluster and your applications in another cluster so that signoz does not limit the resource needs of the application.

Question: can we query SigNoz to get metrics about a service that is running? • Docker container, running python program, instrumented with OpenTelemetry • program sends/creates a "heartbeat" that includes the version of the program and the latest measurement of how long it took to execute the main loop • many instances of this docker container running on different machines/cloud deployments We want to know, in a separate a process, not using SigNoz dashboard in browser: 1. How many docker containers are running our program 2. What the mean/median amount of time the main loop is requiring

Can we do this? Where do I find documentation?

Hello Team, I was plannning to do signoz version upgrade from 0.10.2 to 0.11.0, can anyone help me with the upgrade script and also i need my metrics data and logs to be there after the upgrade operation. Also when i install signoz 0.10.2 at that time otel-collector was install as deployment, but in the latest version i can see otel-collector is of kind deamonset, i want otel-collector as deployment only in the new version of signoz 0.11.0