# Limit storage needs by automatically remove data after 28 days **URL:** \ **Category:** SIEM\ **Created:** [April 12, 2023, 6:44pm UTC](https://discuss.elastic.co/t/limit-storage-needs-by-automatically-remove-data-after-28-days/329865 "2023-04-12T18:44:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![GKre](https://avatars.discourse-cdn.com/v4/letter/g/ecae2f/32.png) [@GKre](https://discuss.elastic.co/u/GKre)\ **Post date:** [April 12, 2023, 6:44pm UTC](https://discuss.elastic.co/t/limit-storage-needs-by-automatically-remove-data-after-28-days/329865/1 "2023-04-12T18:44:36Z")
I have my small test environment up and running. It is collecting data from different sources. Now i wonder how i can handle the effective file storage. Only 1 node in the cluster - non productive. Is it possible to configure the system to automatically remove data older than 28 days or - what would be much better - by setting a storage limit to 60 GB so that old data above this limit will be deleted? I checked this forum but did not find the answer. Any hint for me? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 13, 2023, 12:11am UTC](https://discuss.elastic.co/t/limit-storage-needs-by-automatically-remove-data-after-28-days/329865/2 "2023-04-13T00:11:46Z")
ILM is exactly for this... perhaps take a look. > **[ILM: Manage the index lifecycle | Elasticsearch Guide \[8.7\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)** What are you using to ingest your data? ---
**Author:** ![GKre](https://avatars.discourse-cdn.com/v4/letter/g/ecae2f/32.png) [@GKre](https://discuss.elastic.co/u/GKre)\ **Post date:** [April 13, 2023, 4:55am UTC](https://discuss.elastic.co/t/limit-storage-needs-by-automatically-remove-data-after-28-days/329865/3 "2023-04-13T04:55:12Z")
> [@stephenb](#): > > What are you using to ingest your data? Thanks for this hint. I had been there but i wondered where i could see an "overview" of the data space needed? The value i can see in "index management" ar far away from the reason why my HD run out of space? I am using "Elastic Agent" and "System" integrations for the moment and "Elastic Defend" also. What i'd like to have is a kind of "Overview" over all "indices" or what else is using space so i could focus on the "big ones" Is something like this configurable or available? Guess i will have to take a close look into the ILM Manual 😉 ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 13, 2023, 5:39am UTC](https://discuss.elastic.co/t/limit-storage-needs-by-automatically-remove-data-after-28-days/329865/4 "2023-04-13T05:39:23Z")
I think there is a storage analyzer coming in the next couple releases Otherwise. Stack Management - Index Management Show hidden indices Sort by size ![Screenshot 2023-04-12 at 10.35.34 PM](https://us1.discourse-cdn.com/elastic/original/3X/5/4/544ff37b074ecec0a14d391cb9ad8bd29e835a21.jpeg) Also the in Kibana -\> Dev Tools Will show nodes and space `GET /_cat/nodes/?v&h=name,du,dt,dup,hp,hc,rm,rp,r` Will list indices descending by size `GET /_cat/indices/*?v&s=pri.store.size:desc` Adjusting ILM is the proper method ... All these indices already have default ILM policies You can adjust them, it will warn you are adjust "System Default" but it is fine. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 11, 2023, 5:39am UTC](https://discuss.elastic.co/t/limit-storage-needs-by-automatically-remove-data-after-28-days/329865/5 "2023-05-11T05:39:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.