Hi everyone, Yesterday, I changed the log retentio...
# general
k
Hi everyone, Yesterday, I changed the log retention period, but it gave me an error. After that, CPU usage became very high, and no logs were coming in. The connection to
<http://xxx.xx.xx.xx:4318/v1/traces>
timed out. After restarting Docker and killing some processes, logs started coming in again. How can I identify the root cause and resolve this issue without restarting Docker? Also, how can I check if this issue has occurred before? For my action: I killed a process in ClickHouse, and after that, it started working again. How can I set the log retention period? My current maximum log retention period is six months. There are already some logs in SigNoz. How can I extend the retention period? Please support me. Thanks!
a
@Khuslen what error did you get while changing log retention? i faced similar CPU issue when my log data and metrics started to increase, i had to increase CPU and memory(clickhouse needs it during start time) also consider moving logs to secondary storage like S3 and only keep recent logs in disk to change retention period follow https://signoz.io/docs/userguide/retention-period/