SigNoz Helm Installation and Connection Issue
TLDR Ibrahim experienced connection issues with SigNoz Helm on their Kubernetes cluster and needs help. Prashant suggested checking logs of SigNoz OtelCollector and ClickHouse pods.
Prashant
Wed, 21 Jun 2023 20:04:15 UTC> 2023-06-20T10:33:17.385Z info fileconsumer/file.go:196 Started watching file {“kind”: “receiver”, “name”: “filelog/k8s”, “data_type”: “logs”, “component”: “fileconsumer”, “path”: “/var/log/pods/ This is not an issue but just info
Prashant
Wed, 21 Jun 2023 20:05:24 UTC> I had one “connection aborted issue” in the agent pods, then it started logging the following This message appears in the start during installation. is this coming even afterwards? If yes, do check logs of SigNoz OtelCollector and ClickHouse pods.
SigNoz Community
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in App
Ibrahim
Tue, 20 Jun 2023 10:37:52 UTCHello Everyone I recently installed SigNoz Helm on my kubernetes cluster. I had one “connection aborted issue” in the agent pods, then it started logging the following 2023-06-20T10:33:17.385Z info fileconsumer/file.go:196 Started watching file {“kind”: “receiver”, “name”: “filelog/k8s”, “data_type”: “logs”, “component”: “fileconsumer”, “path”: “/var/log/pods/ I still see nothing in SigNoz frontend, even when I query clickhouse from another tool it shows 0 results. Is there any kube post-installation documentation? (The values yaml file is the default one)