https://signoz.io
Join Slack
Hello all, signoz is amazing tool! We are mowing all our grafana workloads to signoz. I ran into a ...
# support
t
Hello all, signoz is amazing tool! We are mowing all our grafana workloads to signoz. I ran into a small issue though. I have configured S3 for cold storage. Based on documentation I think there is supposed to be a setting when to move data to cold storage:
Copy code
You can also set the duration after which the data will be moved to cold storage (S3/GCS) for traces, metrics and logs. This can be only set if Cold Storage (S3/GCS) is enabled from the backend.
However, I don't see such selection. S3 is configured correctly, I can see tests files are created in the bucket when clickhouse starts. Signoz version 0.92.1 ClickHouse version 25.5.6-alpine Thanks for any advice
k
Data is sent to S3 after it becomes older than the retention period. Logs for example is set to 181 days. Which means logs won't start going to S3 until 182 days after you start using Signoz for logs. Before then, all logs will remain in Signoz Clickhouse DB only.
t
That is interesting. Based on description my expectation was that there would be a setting like "move to s3 after 7 days, delete after 60". I can test this by setting retention for metrics to 1 hour
k
Hmm, now that you mention it, I do recall seeing more boxes on the retention page the last time I looked at it. So I may have steered you wrong in my previous message sorry. I'd need to take another look tomorrow when I'm back at work.
t
I created new fresh copy of signoz with s3 config added imidiatelly. it now has s3 option
so looks like cold storage needs to be enabled on first install 🤔
Ok looks like I found the root cause, there is probably a bug in signoz. The steps that I went trough: 1. I was trying to use EKS pod identity to grant access to S3 2. The default version of clickhouse used in signoz helm chart is 
24.1.2-alpine
which seems to not support this EKS pod identity credentials 3. I updated clickhouse to 
25.5.6-alpine
as described here 4. S3 permissions now were ok but signoz UI does not show 
Move to S3
option. 5. I dowgraded clickhouse back to 
24.1.2-alpine
and used AWS accessKey and secretAccess instead of pod identity role Now UI has an option to enable "Move to S3" and moving itself seems fine
5 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by