Hi team. We met this error when try to query a longer time 1 day logs. Not sure what’s the best way to solve it

{
  "status": "error",
  "data": {},
  "errorType": "bad_data",
  "error": "encountered multiple errors: error in query-A: context deadline exceeded"
}

Another separate question, I have multiple namespaces in the same production cluster that have duplicate sets of our stack in them (app A, app B, etc.) I would like to have them not combine their telemetry on the Services page of signoz when I use the auto instrumentation sidecar. Is there a way to separate the apps out by namespace on this page? Or maybe prepend the namespace name to the service name?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

can't see this "integrations" tab on the sidebar in "self-host" version .. any reason ?

I am setting signoz on EKS I am on clickhouse version:

24.1.2.5

schema migrator image

<http://docker.io/signoz/signoz-schema-migrator:0.102.8|docker.io/signoz/signoz-schema-migrator:0.102.8>

gives me the error as

clickhouse migrate failed to run, error: Dirty database version 16. Fix and force version.

is it necessary for me to have Database version

16

?

I am trying to send data from my cluster via otel agent to signoz otel collector on grpc I am seeing error in my source. My source is a default grpc otlp exporter

info	exporterhelper/queued_retry.go:423	Exporting failed. Will retry the request after interval.	{"kind": "exporter", "data_type": "logs", "name": "otlp", "error": "rpc error: code = Unavailable desc = upstream connect error or disconnect/reset before headers. reset reason: connection termination", "interval": "32.243501486s"}

and signoz Otel collector (default grpc otlp receiver ) is throwing error as:

info	zapgrpc/zapgrpc.go:178	[transport] [server-transport 0xc000ad0b60] Closing: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"POST /opentelemetry.prot\""	{"grpc_log": true}

Has anyone else faced this error?

This message was deleted.