Trouble Setting Trace Retention Days in SigNoz
TLDR Jose faced issues with trace retention settings. vishal-signoz advised connecting to SQLite DB and clearing TTL status table to update the retention setting.
Jose
Sun, 26 Mar 2023 16:02:45 UTCIs there a way to force this? Or Delete all data and restart?
Jose
Sun, 26 Mar 2023 20:08:08 UTCI'm running signoz on an ec2 instance (t3a.2xlarge)
vishal-signoz
Mon, 27 Mar 2023 04:21:04 UTCWhich SigNoz version are you using Jose? In latest version there are some improvements on retention.
Jose
Mon, 27 Mar 2023 11:27:11 UTC0.17.0, the latest one. I've even block all incoming traffic so as not to have new traces and process the remaining one....still kept in that loop
vishal-signoz
Wed, 29 Mar 2023 05:02:45 UTCYou can connect to SQLite DB and clear TTL status table to allow updating retention setting. If you are using docker follow below steps: Connect to query-service ```docker exec -it query-service sh``` Run the following: ```# install sqlite apk update apk add sqlite # open sqlite with signoz.db sqlite3 /var/lib/signoz/signoz.db # (sqlite shell) check existing ttl status select * from ttl_status; # delete all rows of ttl_status DELETE FROM ttl_status;```
SigNoz Community
Indexed 1060 threads
Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI
View in App
Jose
Sun, 26 Mar 2023 16:02:21 UTCHi everyone, I'm struggling withe setting the trace retention days. I've changed it to 5 days, but several days have passed and the setting never persisted. I've tried recreating the docker container, restarting, etc. But still the issue: