hi , is there a way or some configuration tag in c...
# support
s
hi , is there a way or some configuration tag in clickhouse-storage.xml to write a rule to move data on s3 based on time period eg : 1 month and empty the clickhouse tables so that it can ingest data periodically without any space issues .
v
You can set retention based on time period like move to s3 by following this doc: https://signoz.io/docs/userguide/retention-period/#configuring-cold-storage---amazon-s3
Even in s3 the performance drop is around 30% so you can access s3 data like normal data (with some performance drop)
s
thanks vishal for the response , so you are saying , suppose if i retain after 7 days data into s3 by configuring then , after that clickhouse will automatically query old data from s3 , actually i also had that doubt that if i need to write some code/query using s3 table engine to get visuals from data stored in s3 .
v
so you are saying , suppose if i retain after 7 days data into s3 by configuring then , after that clickhouse will automatically query old data from s3
Yes
s
thanks bro for clearification
v
actually i also had that doubt that if i need to write some code/query using s3 table engine to get visuals from data stored in s3
No, SigNoz handles everything for you
s
actually i want to deeply understand about clickhouse working and storage pipeline , that's why i m exploring so that i can handle all issues whatever comes while going into production experiment .
so acc to you , clickhouse official documentation is enough right ?
v
Yes, you can follow this guide to connect to clickhouse: https://signoz.io/docs/operate/clickhouse/connect-to-clickhouse/
s
okay
one more thing , i think i should discuss is that , i m thinking to use ec2 over elastic load balancing for replication but will be keeping vertically scalable rather than sharding after estimating the current scale i need to handle, will it be the good option in terms of best practices .
v
yes it should be fine
s
yeah , actually i m deploying it into production as a experiment for application performance analysis
so i was exploring some open source apm , i found this suitable in terms of features , usecases coverage , technical architecture wise
so i started reading more about observebility , opentelem and signoz in detail so that i can setup completely infrastructure in scalable way so as to remove dependency on saas based apm's
now i understood its working , deployed on stage and now trying to get proper grip on all components including best deployment stretagy