This message was deleted.

do you want to add. your own clickhouse @Dave Lahn?

We have set up a standalone ClickHouse.

Got it. This might be helpful - https://signoz.io/docs/operate/clickhouse/connect-to-clickhouse/

We aren't used K8s. We are setting this up in ECS/Fargate, so we are bringing up all of the individual elements.

It seems the SigNoz otel-collector must have a cluster called “cluster” in ClickHouse

Yes

I have already shared @Srikanth Chekuri - https://signoz.io/docs/operate/clickhouse/connect-to-clickhouse/

@Pranay This isn't the correct doc. This is just how to connect to ClickHouse.

Ok, will let Srikanth get back

In your docker-compose example, you have something like this:

<?xml version="1.0"?>
<clickhouse>
    <remote_servers>
        <cluster>
            <shard>
                <replica>
                    <host>localhost</host>
                    <port>9000</port>
                </replica>
            </shard>
        </cluster>
    </remote_servers>
</clickhouse>

ZK that comes with SigNoz installation is not required if you want to use external ClickHouse. It’s main purpose is to provide coordination system for distributed ClickHouse. But if you want to use SigNoz there should be cluster called

cluster

so you may already have zk or clickhouse keeper on your ClickHouse server.

So I must have ZK or Keeper to back my ClickHouse.

Yes, the distributed ClickHouse setup requires zookeeper or clickhouse-keeper.

Ok. And since you require "cluster", I have to have a distributed ClickHouse, even though I only have 1 ClickHouse.

Let me share the docs for it.

Unfortunately, there is no written documentation around this. You can disable the ClickHouse and setup the appropriate values for externalClickHouse. And use the override-values to apply the custom config.

The easy solution for this was to enable the ClickHouse Keeper configuration within ClickHouse.

Nice, were you able to make this work for your setup? @Dave Lahn