# Monitoring Gaps in Marvel Data

**URL:** <https://discuss.elastic.co/t/monitoring-gaps-in-marvel-data/139394>\
**Category:** Elasticsearch\
**Created:** [July 10, 2018, 3:52pm UTC](https://discuss.elastic.co/t/monitoring-gaps-in-marvel-data/139394 "2018-07-10T15:52:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tebriel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tebriel/32/44889_2.png) [@tebriel](https://discuss.elastic.co/u/tebriel)\
**Post date:** [July 10, 2018, 3:52pm UTC](https://discuss.elastic.co/t/monitoring-gaps-in-marvel-data/139394/1 "2018-07-10T15:52:04Z")

</div>

So...first, yes, I know that I'm using 2.4.6 and that's old and out of date. I'm on an upgrade path to 6.3.1, we're waiting on rolling out logstash updates everywhere. That said, when I had all my traffic being mirrored to ES6, I experienced the same problem, I just don't have a live cluster to show this on. I'm seeing gaps in monitoring data, especially when I drill down to the 15 minute span. The gaps are at different times on each node. Attached is an example graph. I tried increasing the shards from 1 to 3 (6 data node cluster, 3 masters, 1 replica everywhere, split across two AWS AZs using Routing Awareness). Is there something I'm missing? Should I see such consistent, repeating gaps?

 ![26%20AM](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1fba16a7dd66e5cbf4aab4757406645d22367d26.png)

---

<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:** [August 7, 2018, 3:52pm UTC](https://discuss.elastic.co/t/monitoring-gaps-in-marvel-data/139394/2 "2018-08-07T15:52:09Z")

</div>

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