This message was deleted.

Can you can try out the changes suggested by this article https://theorangeone.net/posts/calming-down-clickhouse/

This is what I'm trying to do actually. According to your chart https://github.com/SigNoz/charts/blob/main/charts/signoz/values.yaml#L225-L230 :

profiles: {}

  # -- Default user profile configuration for Clickhouse. !!! Please DO NOT override this !!!
  defaultProfiles:
    default/allow_experimental_window_functions: "1"
    default/allow_nondeterministic_mutations: "1"

so I added the following to the list:

default/log_queries: "0"

and when I restart the pod, I don't see anywhere the changes, so it seems what is changed in the

values.yaml

are not properly applied maybe. I can see this file `/etc/clickhouse-server/users.d/chop-generated-profiles.xml`:

yandex>
    <profiles>
        <default>
            <allow_experimental_window_functions>1</allow_experimental_window_functions>
            <allow_nondeterministic_mutations>1</allow_nondeterministic_mutations>
        </default>
    </profiles>
</yandex>

and this `/etc/clickhouse-server/users.d/02-clickhouse-default-profile.xml`:

<yandex>
  <profiles>
    <default>
      <log_queries>1</log_queries>
      <connect_timeout_with_failover_ms>1000</connect_timeout_with_failover_ms>
      <distributed_aggregation_memory_efficient>1</distributed_aggregation_memory_efficient>
      <parallel_view_processing>1</parallel_view_processing>
    </default>
  </profiles>
</yandex>

without my settings of

log_queries=0

anywhere 😕

@Prashant Shahi can you help here?

Hello @Guillaume 👋 You can lower the log output of chi pods to

warning

by setting the following configuration in

override-values.yaml

:

clickhouse:
  clickhouseOperator:
    logger:
      level: warning

Followed by

helm upgrade

or

helm install

command.

Seems to be working this way, thanks!

That’s great 🎉