# Sum index size based on unique identifier

**URL:** <https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581>\
**Category:** Kibana\
**Created:** [March 24, 2022, 2:17pm UTC](https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581 "2022-03-24T14:17:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![phager](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@phager](https://discuss.elastic.co/u/phager)\
**Post date:** [March 24, 2022, 2:17pm UTC](https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581/1 "2022-03-24T14:17:36Z")

</div>

I have data within Elasticsearch indexed by customer, i.e. index-custnumber-2022-w11, that I would like to sum index size per unique customer into a chart in Kibana. I can run curl -X GET "localhost:9200/\_cat/indices/index-custnumber-\*?v=true&s=index&pretty" to view the index sizes for each index but have not been able to visualize for reference on total space each customer is using within Kibana.

What is the best way to visualize this in Kibana?

Elasticsearch v7.16.3

Kibana v7.16.3

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [March 24, 2022, 4:59pm UTC](https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581/2 "2022-03-24T16:59:23Z")

</div>

@flash1293 can we please get some help here?

Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\
**Post date:** [March 29, 2022, 8:31am UTC](https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581/3 "2022-03-29T08:31:03Z")

</div>

Kibana visualizations can't access the meta information about indices directly. A workaround for that I can think of is to have a script running somewhere via cronjob which is fetching the index information (documents, size, customer id, ...) and indexing them again as regular documents into a separate index. Then Kibana will be able to build visualizations based on this new index.

---

<div class="post-metadata">

**Author:** ![phager](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@phager](https://discuss.elastic.co/u/phager)\
**Post date:** [March 29, 2022, 12:33pm UTC](https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581/4 "2022-03-29T12:33:29Z")

</div>

Thank you for that information.

---

<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:** [April 26, 2022, 12:34pm UTC](https://discuss.elastic.co/t/sum-index-size-based-on-unique-identifier/300581/5 "2022-04-26T12:34:04Z")

</div>

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