I seem to be getting error 500 when i call this signoz_latency_bucket metrics. after updating to latest version, this works fine on my previous version and i did a clean install I imported the dashboard from github Here is image from dashboard old and new version

Hey folks, Did anybody face such an issue. I run signoz in the swarm mode under wsl. And it seems like all domain names are wrongly resolved:

2024-11-07 13:52:54 SigNoz version   : v0.56.0
2024-11-07 13:52:54 Commit SHA-1     : b70d50f
2024-11-07 13:52:54 Commit timestamp : 2024-10-10T10:10:41Z
2024-11-07 13:52:54 Branch           : HEAD
2024-11-07 13:52:54 Go version       : go1.22.7
2024-11-07 13:52:54 
2024-11-07 13:52:54 For SigNoz Official Documentation,  visit <https://signoz.io/docs/>
2024-11-07 13:52:54 For SigNoz Community Slack,         visit <http://signoz.io/slack/>
2024-11-07 13:52:54 For archive of discussions about SigNoz,       visit <https://knowledgebase.signoz.io/>
2024-11-07 13:52:54 
2024-11-07 13:52:54 Check SigNoz Github repo for license details.
2024-11-07 13:52:54 Copyright 2024 SigNoz
2024-11-07 13:52:54 
2024-11-07 13:52:54 {"level":"WARN","timestamp":"2024-11-07T13:52:54.926Z","caller":"query-service/main.go:152","msg":"No JWT secret key is specified."}
2024-11-07 13:52:54 {"level":"INFO","timestamp":"2024-11-07T13:52:54.928Z","caller":"query-service/main.go:160","msg":"Migration successful"}
2024-11-07 13:52:55 {"level":"INFO","timestamp":"2024-11-07T13:52:55.108Z","caller":"license/manager.go:126","msg":"No active license found, defaulting to basic plan"}
2024-11-07 13:52:55 {"level":"INFO","timestamp":"2024-11-07T13:52:55.109Z","caller":"app/server.go:149","msg":"Using ClickHouse as datastore ..."}
2024-11-07 13:52:55 {"level":"INFO","timestamp":"2024-11-07T13:52:55.109Z","caller":"clickhouseReader/options.go:108","msg":"Connecting to Clickhouse","at":"clickhouse:9000","MaxIdleConns":50,"MaxOpenConns":100,"DialTimeout":5000}
2024-11-07 13:52:58 {"level":"FATAL","timestamp":"2024-11-07T13:52:58.585Z","caller":"clickhouseReader/reader.go:170","msg":"failed to initialize ClickHouse","error":"error connecting to primary db: dial tcp: lookup clickhouse on 127.0.0.11:53: no such host","stacktrace":"<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.NewReader|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.NewReader>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:170\ngo.signoz.io/signoz/ee/query-service/app/db.NewDataConnector\n\t/home/runner/work/signoz/signoz/ee/query-service/app/db/reader.go:30\ngo.signoz.io/signoz/ee/query-service/app.NewServer\n\t/home/runner/work/signoz/signoz/ee/query-service/app/server.go:150\nmain.main\n\t/home/runner/work/signoz/signoz/ee/query-service/main.go:163\nruntime.main\n\t/home/runner/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.22.7.linux-amd64/src/runtime/proc.go:271"}

What's even more confusing is that if I connect to the running containers, it can resolve domains correctly:

# from otel-collector
/ # telnet clickhouse 9000
Connected to clickhouse

Hi Clickhouse cpu consumption is high with the below error logs

Hi, I ran into issues setting metrics total retention period in v0.46 and tried now on v0.47 as well. I did see some logs in the query service

signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"INFO","timestamp":"2024-06-06T13:05:18.162Z","caller":"app/server.go:388","msg":"/api/v1/settings/ttl\ttimeTaken:42.476559ms","timeTaken":42,"path":"/api/v1/settings/ttl"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"ERROR","timestamp":"2024-06-06T13:05:18.171Z","caller":"clickhouseReader/reader.go:2406","msg":"error while setting ttl.","error":"code: 47, message: There was an error on [chi-signoz-with-clickhouse-cluster-0-0:9000]: Code: 47. DB::Exception: Missing columns: 'timestamp_ms' while processing query: 'toDateTime(toUInt32(timestamp_ms / 1000), 'UTC') + toIntervalSecond(604800)', required columns: 'timestamp_ms' 'timestamp_ms'. (UNKNOWN_IDENTIFIER) (version 24.1.2.5 (official build))","stacktrace":"<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:2406"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"ERROR","timestamp":"2024-06-06T13:05:18.238Z","caller":"clickhouseReader/reader.go:2406","msg":"error while setting ttl.","error":"code: 47, message: There was an error on [chi-signoz-with-clickhouse-cluster-0-0:9000]: Code: 47. DB::Exception: Missing columns: 'timestamp_ms' while processing query: 'toDateTime(toUInt32(timestamp_ms / 1000), 'UTC') + toIntervalSecond(604800)', required columns: 'timestamp_ms' 'timestamp_ms'. (UNKNOWN_IDENTIFIER) (version 24.1.2.5 (official build))","stacktrace":"<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:2406"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"ERROR","timestamp":"2024-06-06T13:05:18.250Z","caller":"clickhouseReader/reader.go:2406","msg":"error while setting ttl.","error":"code: 47, message: There was an error on [chi-signoz-with-clickhouse-cluster-0-0:9000]: Code: 47. DB::Exception: Missing columns: 'timestamp_ms' while processing query: 'toDateTime(toUInt32(timestamp_ms / 1000), 'UTC') + toIntervalSecond(604800)', required columns: 'timestamp_ms' 'timestamp_ms'. (UNKNOWN_IDENTIFIER) (version 24.1.2.5 (official build))","stacktrace":"<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:2406"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"ERROR","timestamp":"2024-06-06T13:05:18.264Z","caller":"clickhouseReader/reader.go:2406","msg":"error while setting ttl.","error":"code: 47, message: There was an error on [chi-signoz-with-clickhouse-cluster-0-0:9000]: Code: 47. DB::Exception: Missing columns: 'timestamp_ms' while processing query: 'toDateTime(toUInt32(timestamp_ms / 1000), 'UTC') + toIntervalSecond(604800)', required columns: 'timestamp_ms' 'timestamp_ms'. (UNKNOWN_IDENTIFIER) (version 24.1.2.5 (official build))","stacktrace":"<http://go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2|go.signoz.io/signoz/pkg/query-service/app/clickhouseReader.(*ClickHouseReader).SetTTL.func2>\n\t/home/runner/work/signoz/signoz/pkg/query-service/app/clickhouseReader/reader.go:2406"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"INFO","timestamp":"2024-06-06T13:05:19.224Z","caller":"clickhouseReader/reader.go:2499","msg":"checkTTLStatusItem query","query":"SELECT id, status, ttl, cold_storage_ttl FROM ttl_status WHERE table_name = ? ORDER BY created_at DESC","tableName":"signoz_metrics.samples_v4"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"INFO","timestamp":"2024-06-06T13:05:19.228Z","caller":"clickhouseReader/reader.go:2499","msg":"checkTTLStatusItem query","query":"SELECT id, status, ttl, cold_storage_ttl FROM ttl_status WHERE table_name = ? ORDER BY created_at DESC","tableName":"signoz_metrics.samples_v4"}
signoz-with-clickhouse-query-service-0 signoz-with-clickhouse-query-service {"level":"INFO","timestamp":"2024-06-06T13:05:19.229Z","caller":"clickhouseReader/reader.go:2591","msg":"Parsing TTL from: ","queryResp":"MergeTree PARTITION BY toDate(unix_milli / 1000) ORDER BY (env, temporality, metric_name, fingerprint, unix_milli) TTL toDateTime(unix_milli / 1000) + toIntervalSecond(2592000) SETTINGS ttl_only_drop_parts = 1, index_granularity = 8192"}

is this a known issue?

👋 Hello, team! I'm using signoz local and try to trace the DB call metrics (Mongo DB) , but I'm unable to do so. Can anyone help me to figure it out ?

How to get nested spans for a request?

const trace = signozTracer.startSpan(functionName);
const span = trace.addEvent('mongo-getbyid');

I tried the above approach, but I am getting

mongo-getbyid

in events section, instead of in spans below main span. Any advice to manually instrument database performance traces so that I can see it in a request span as well as separately in mongo group for example.

Hi, I'am installing Signoz helm chart via ArgoCD, whenever I

sync

it always shows

out of sync

with these changes. Any idea why this is coming? I'am using the chart version: 0.38.0

This message was deleted.

This message was deleted.

This message was deleted.