External ClickHouse Server Installation Issue
TLDR Syed faced a connection error with an external ClickHouse server. Srikanth and Ankit suggested changing the cluster name to 'cluster'. The issue was resolved after updating the name.
Apr 07, 2023 (8 months ago)
Syed
02:13 AMkubectl logs -f my-release-signoz-otel-collector-54bf55dbb9-ckqmz
Defaulted container "my-release-signoz-otel-collector" out of: my-release-signoz-otel-collector, my-release-signoz-otel-collector-init (init)
2023-04-07T02:08:48.916Z info service/telemetry.go:111 Setting up own telemetry...
2023-04-07T02:08:48.916Z info service/telemetry.go:141 Serving Prometheus metrics {"address": "0.0.0.0:8888", "level": "Basic"}
2023-04-07T02:08:48.916Z info components/components.go:30 Stability level of component is undefined {"kind": "exporter", "data_type": "traces", "name": "clickhousetraces", "stability": "Undefined"}
Error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": error connecting to primary db: code: 170, message: Requested cluster 'cluster' not found
2023/04/07 02:08:48 application run finished with error: cannot build pipelines: failed to create "clickhousetraces" exporter, in pipeline "traces": error connecting to primary db: code: 170, message: Requested cluster 'cluster' not found
My override file:
global:
storageClass: gp2
cloud: aws
clickhouse:
enabled: false
cloud: other
externalClickhouse:
host: 54.75.80.150
cluster: events
user: xxxxxx
password: xxxxxxxxxxxxxxx
secure: false
verify: false
httpPort: 8123
tcpPort: 9000
allowedNetworkIps:
- "0.0.0.0/0"
I really appreciate your kind response.
Srikanth
02:17 AMcluster
Syed
02:18 AMSrikanth
02:18 AMcluster
. Create one if it doesn’t exist.Syed
02:18 AM Environment:
CLICKHOUSE_HOST: 54.75.70.130
CLICKHOUSE_PORT: 9000
CLICKHOUSE_HTTP_PORT: 8123
CLICKHOUSE_CLUSTER: events
CLICKHOUSE_DATABASE: signoz_metrics
CLICKHOUSE_TRACE_DATABASE: signoz_traces
CLICKHOUSE_USER: admin
CLICKHOUSE_PASSWORD: 2kkkkkkkb9
CLICKHOUSE_SECURE: false
CLICKHOUSE_VERIFY: false
K8S_NODE_NAME: (v1:spec.nodeName)
K8S_POD_IP: (v1:status.podIP)
K8S_POD_NAME: my-release-signoz-otel-collector-54bf55dbb9-ckqmz (v1:metadata.name)
K8S_POD_UID: (v1:metadata.uid)
K8S_NAMESPACE: platform (v1:metadata.namespace)
K8S_CLUSTER_NAME:
SIGNOZ_COMPONENT: otel-collector
OTEL_RESOURCE_ATTRIBUTES: host.name=$(K8S_NODE_NAME),signoz.component=$(SIGNOZ_COMPONENT),k8s.cluster.name=$(K8S_CLUSTER_NAME),k8s.pod.uid=$(K8S_POD_UID),k8s.pod.ip=$(K8S_POD_IP)
LOW_CARDINAL_EXCEPTION_GROUPING: false
Syed
02:19 AMSyed
02:19 AMSyed
02:28 AMAnkit
04:00 AMcluster
Syed
07:45 AMSyed
08:07 AMSigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Issues Running SigNoz on Azure AKS with External ClickHouse DB
Nicolai faced an error while trying to run SigNoz with an external ClickHouse database on Azure AKS. Prashant suggested additional steps and the need for detailed documentation for using SigNoz with an external ClickHouse database.
Error with ClickHouse Cluster Name in SigNoz-Otel-Collector
Shreyash encountered an error related to hardcoded ClickHouse cluster name. Romil suggested renaming the cluster to "cluster" to fix the issue.
Issues with SigNoz Setup and Data Persistence in AKS
Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.
SigNoz Deployment Issue with External ClickHouse and PVC
Ragulraj faced issues with deploying SigNoz v0.18.1 through kubernetes due to otel-collector not connecting to the correct ClickHouse cluster. After discussing with Srikanth, Syed and Prashant, he decided to try again with SigNoz helm charts, but faced issues with PVC remaining pending.
Issues with Multicluster Functionality in a Clickhouse Setup
Hoang has trouble implementing multi-cluster functionality in a Clickhouse setup as the collector does not read `CLICKHOUSE_CLUSTER`. Shivanshu suggests using `cluster` for the cluster name, while Prashant refers to the relevant documentation.