# Kibana total data ingest and total index data ingest rate visulization

**URL:** https://discuss.elastic.co/t/kibana-total-data-ingest-and-total-index-data-ingest-rate-visulization/232102
**Category:** Kibana
**Created:** [May 11, 2020, 7:30pm UTC](https://discuss.elastic.co/t/kibana-total-data-ingest-and-total-index-data-ingest-rate-visulization/232102 "2020-05-11T19:30:26Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)
#### Post date: [May 11, 2020, 7:30pm UTC](https://discuss.elastic.co/t/kibana-total-data-ingest-and-total-index-data-ingest-rate-visulization/232102/1 "2020-05-11T19:30:26Z")

</div>

Is there a way to track the overall data ingest rate of an ECE deployment? I'd also like to create a visualization that does the same with a specific index so that I can maintain a good idea of what the daily ingest rate looks like. The problem that I'm running into is that we don't have a field like system.network.in.bytes populating since the data we are ingesting is not from a Beat which has fields like that. I've deconstructed the Inbound Traffic [Metircbeat] ECS visualization so I have an idea of how this could be done I'm just not sure there's even a way to do this with the data that we are getting.

---

<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: [May 11, 2020, 11:02pm UTC](https://discuss.elastic.co/t/kibana-total-data-ingest-and-total-index-data-ingest-rate-visulization/232102/2 "2020-05-11T23:02:10Z")

</div>

Did you try to look at monitoring? Here is a screenshot where I am running filebeat to ingest elasticsearch logs:

 ![Screen Shot 2020-05-11 at 7.00.46 PM](https://us1.discourse-cdn.com/elastic/original/3X/4/a/4a974cb80e22aec815f5f2fd130e2503478783f5.jpeg)

Here are our docs: [https://www.elastic.co/guide/en/elasticsearch/reference/7.6/monitor-elasticsearch-cluster.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/monitor-elasticsearch-cluster.html)

[https://www.elastic.co/guide/en/kibana/current/kibana-page.html](https://www.elastic.co/guide/en/kibana/current/kibana-page.html)

Let me know if this helps?

Thanks,  
Bhavya

---

<div class="post-metadata">

### Author: ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)
#### Post date: [May 12, 2020, 12:44pm UTC](https://discuss.elastic.co/t/kibana-total-data-ingest-and-total-index-data-ingest-rate-visulization/232102/3 "2020-05-12T12:44:07Z")

</div>

It looks like this could be an option as I could utilize the indexing rate and disk to get a rough idea of where things are headed. Thanks for the insight. 🙂

---

<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: [June 9, 2020, 12:44pm UTC](https://discuss.elastic.co/t/kibana-total-data-ingest-and-total-index-data-ingest-rate-visulization/232102/4 "2020-06-09T12:44:13Z")

</div>

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