# Marvel Refresh Rate

**URL:** <https://discuss.elastic.co/t/marvel-refresh-rate/25739>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [July 16, 2015, 6:23pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739 "2015-07-16T18:23:22Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![koka424](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@koka424](https://discuss.elastic.co/u/koka424)\
**Post date:** [July 16, 2015, 6:23pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/1 "2015-07-16T18:23:22Z")

</div>

I just got marvel up and running and everything looks good except the nodes and indices keep getting grayed out. A little ! symbol is next to the nodes and indices saying that it hasnt received an update in over 1 minute. Due to the size of the cluster marvel is automatically adjusting the refresh rate to 2 minutes. It wont allow me to change it. How can I either:

1. Increase the timeout to over 2 minutes on the alert to keep the nodes/indices from being grayed out.

Or

1. Force marvel/kibana to accept a refresh rate on the dashboard of 1 minute?

Thanks.

Elasticsearch 1.1.1 ( data cluster )  
Elasticsearch 1.6 ( monitoring cluster )  
Marvel 1.3.1

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 17, 2015, 2:39am UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/2 "2015-07-17T02:39:29Z")

</div>

How big is your cluster?

---

<div class="post-metadata">

**Author:** ![koka424](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@koka424](https://discuss.elastic.co/u/koka424)\
**Post date:** [July 17, 2015, 12:26pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/3 "2015-07-17T12:26:37Z")

</div>

10 nodes with 3.84TB of data. I have seen one or two posts where this warning pops up with small clusters as well. Unfortunately, they did not post the cause or what was done to resolve it.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 17, 2015, 2:26pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/4 "2015-07-17T14:26:29Z")

</div>

Maybe they had a subscription for it? 😉

However, do you have NTP setup?

---

<div class="post-metadata">

**Author:** ![koka424](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@koka424](https://discuss.elastic.co/u/koka424)\
**Post date:** [July 17, 2015, 2:46pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/5 "2015-07-17T14:46:39Z")

</div>

I purchased 10 license for a 10 node cluster. We have a separate 4 node cluster we use for logging that I am sending all of the data to. I logged into marvel on the logging cluster and applied the license there. Could this be a licensing issue? Do the nodes in the logging cluster count towards the licensing for marvel?

I did see that time drift was the main cause. All servers are running NTP and the time is synced.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 18, 2015, 4:28am UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/6 "2015-07-18T04:28:33Z")

</div>

You probably won't need that large of a cluster for monitoring, unless you want to keep data for a looooong time 🙂

> [@koka424](#):
>
> I purchased 10 license for a 10 node cluster.

Awesome 🙂

---

<div class="post-metadata">

**Author:** ![koka424](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@koka424](https://discuss.elastic.co/u/koka424)\
**Post date:** [July 20, 2015, 1:43pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/7 "2015-07-20T13:43:14Z")

</div>

Alright so if licensing isn't and issue and all of the times on the servers are in sync, what can I do to fix this? Is it possible to force the refresh rate to 1 minute? Or is it possible to change the time that marvel alerts on the servers to 2 minutes?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 23, 2015, 12:09am UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/8 "2015-07-23T00:09:44Z")

</div>

I've asked someone from the Marvel team to comment in here, hopefully we can get you an answer.

---

<div class="post-metadata">

**Author:** ![koka424](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@koka424](https://discuss.elastic.co/u/koka424)\
**Post date:** [August 17, 2015, 12:26pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/9 "2015-08-17T12:26:40Z")

</div>

I appreciate you reaching out to the Marvel team. Was anyone able to take a look at this?

---

<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:** [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/marvel-refresh-rate/25739/10 "2017-07-06T13:47:40Z")

</div>

Closed on July 6, 2017, 1:47pm UTC


