Me again with an

otel-collector

issue. I keep seeing this intermittent error in the collector logs

2024-09-10T22:31:30.706Z	error	tcp/input.go:156	Scanner error	{"kind": "receiver", "name": "tcplog/docker", "data_type": "logs", "operator_id": "tcp_input", "operator_type": "tcp_input", "error": "bufio.Scanner: token too long"}
<http://github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1|github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1>
	/home/runner/go/pkg/mod/github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/input/tcp/input.go:156

2024-09-10T22:31:31.721Z	error	tcp/input.go:156	Scanner error	{"kind": "receiver", "name": "tcplog/docker", "data_type": "logs", "operator_id": "tcp_input", "operator_type": "tcp_input", "error": "bufio.Scanner: token too long"}
<http://github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1|github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1>
	/home/runner/go/pkg/mod/github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/input/tcp/input.go:156

This causes

logspout

to crash and restart

2024-09-10T22:31:30.706Z	error	tcp/input.go:156	Scanner error	{"kind": "receiver", "name": "tcplog/docker", "data_type": "logs", "operator_id": "tcp_input", "operator_type": "tcp_input", "error": "bufio.Scanner: token too long"}
<http://github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1|github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1>
	/home/runner/go/pkg/mod/github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/input/tcp/input.go:156
2024-09-10T22:31:31.721Z	error	tcp/input.go:156	Scanner error	{"kind": "receiver", "name": "tcplog/docker", "data_type": "logs", "operator_id": "tcp_input", "operator_type": "tcp_input", "error": "bufio.Scanner: token too long"}
<http://github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1|github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/tcp.(*Input).goHandleMessages.func1>
	/home/runner/go/pkg/mod/github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/input/tcp/input.go:156

Is this a known issue?

After recent upgrade to latest version of signoz, some things are not working properly, getting CORS issue. not able to edit alerts

Hello, Team, As per this, zookeeper is not necessary for single node clickhouse and I do not think there's an option to not use a zookeeper in the SigNoz/ClickHouse helm chart. Any help on how to disable it and whether we even should (to save on memory) ?

Is there any way of exporting user-settings, dashboards etc, and then importing it to a different signoz ? Because its stored in a sqlite db, so its in a PVC in kubernetes. So if you recreate cluster, its kinda difficult to have it persist to the next kubernetes cluster (AWS EKS)

Hello, I need help. I'm trying to boot up query-service on signoz-docker environment in WSL. However I got error message like belows. Any ideas?

{"level":"\u001b[31mFATAL\u001b[0m","timestamp":"2024-05-09T18:20:58.696+0900","caller":"query-service/main.go:95","msg":"Failed to create server{error 26 0  Storage type:  is not supported in query service}","stacktrace":"main.main\n\t/root/signoz/pkg/query-service/main.go:95\nruntime.main\n\t/snap/go/10585/src/runtime/proc.go:271"}
exit status 1

root@hjchoi-samsung:~/signoz/pkg/query-service# CGO_ENABLED=1 go run main.go # github.com/mattn/go-sqlite3 sqlite3-binding.c: In function ‘sqlite3SelectNew’: sqlite3-binding.c12804910: warning: function may return address of local variable [-Wreturn-local-addr] 128049 | return pNew; | ^~~~ sqlite3-binding.c12800910: note: declared here 128009 | Select standin; | ^~~~~~~ SigNoz version : -- Commit SHA-1 : -- Commit timestamp : -- Branch : -- Go version : go1.22.2 For SigNoz Official Documentation, visit https://signoz.io/docs For SigNoz Community Slack, visit http://signoz.io/slack For discussions about SigNoz, visit https://community.signoz.io Check SigNoz Github repo for license details. Copyright 2022 SigNoz {"level":"\u001b[33mWARN\u001b[0m","timestamp":"2024-05-09T182048.691+0900","caller":"query-service/main.go:88","msg":"No JWT secret key is specified."} {"level":"\u001b[31mFATAL\u001b[0m","timestamp":"2024-05-09T182058.696+0900","caller":"query-service/main.go:95","msg":"Failed to create server{error 26 0 Storage type: is not supported in query service}","stacktrace":"main.main\n\t/root/signoz/pkg/query-service/main.go95\nruntime.main\n\t/snap/go/10585/src/runtime/proc.go271"} exit status 1

Hey folks @ SigNoz - I understand SigNoz doesn't run on Graviton nodes atm, but are there any plans to make it work on

arm64

? I have a feeling I might be breaking the bank soon, running Clickhouse on

c6i

nodes 😄

Hello Team! I am trying to send application logs from log file to signoz I can see docker logs but not the logs which I wanted to see from the file I am attaching the config file to the thread

This message was deleted.

This message was deleted.

This message was deleted.