For a test, I needed to deploy a Signoz test instance, so I did so using the helm chart. Currently, SignozTest is receiving no Records, everything is empty. However, I took notice that the clickhouse volume still rapidly ingested data every minute. This rate has been slowing down with every passing minute, but has yet to fully stop. What is it storing and could I further disable it? My concern is with the fact this data may not have an easily configurable TTL same way the observability records do.

@Srikanth Chekuri system tables? How can we look more into this?

This is less likely about system tables. We collect the logs and metrics from the cluster automatically when you install through the helm chart.

Currently, SignozTest is receiving no Records, everything is empty.

Did you also check if there are no logs and metrics?

What is it storing and could I further disable it?

Please exec into clickhouse and share the output of this

SELECT
    database,
    table,
    formatReadableSize(sum(data_compressed_bytes) AS size) AS compressed,
    formatReadableSize(sum(data_uncompressed_bytes) AS usize) AS uncompressed,
    round(usize / size, 2) AS compr_rate,
    sum(rows) AS rows,
    count() AS part_count
FROM system.parts
WHERE (active = 1) AND (database LIKE '%') AND (table LIKE '%')
GROUP BY
    database,
    table
ORDER BY size DESC;