# Indices size is very big

**URL:** <https://discuss.elastic.co/t/indices-size-is-very-big/230567>\
**Category:** Elasticsearch\
**Created:** [April 30, 2020, 1:52pm UTC](https://discuss.elastic.co/t/indices-size-is-very-big/230567 "2020-04-30T13:52:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![devops\_army](https://avatars.discourse-cdn.com/v4/letter/d/3be4f8/32.png) [@devops\_army](https://discuss.elastic.co/u/devops_army)\
**Post date:** [April 30, 2020, 1:52pm UTC](https://discuss.elastic.co/t/indices-size-is-very-big/230567/1 "2020-04-30T13:52:19Z")

</div>

Hi All,

I had configured ELK stack deployed in Kubernetes and there are multiple components deployed and logs will be stored using ELK. On an average , per day index size is 30GB and how couple of weeks I can see my indices size is showing as 120gb.

How can I findout which application sends more number of logs to ELK stack?

Regards  
VK

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [April 30, 2020, 2:51pm UTC](https://discuss.elastic.co/t/indices-size-is-very-big/230567/2 "2020-04-30T14:51:32Z")

</div>

Depending on where you see "index size", it may include primary and replica shards. So if you have 30G of ingest and 2 replicas, 30G x 3 would be 90G.

Use Kibana Discover and Visualize to study your data, like events per host.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 28, 2020, 2:51pm UTC](https://discuss.elastic.co/t/indices-size-is-very-big/230567/3 "2020-05-28T14:51:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.