# Marvel 2.0 - Index Template Override

**URL:** <https://discuss.elastic.co/t/marvel-2-0-index-template-override/35443>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [November 24, 2015, 11:52am UTC](https://discuss.elastic.co/t/marvel-2-0-index-template-override/35443 "2015-11-24T11:52:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [November 24, 2015, 11:52am UTC](https://discuss.elastic.co/t/marvel-2-0-index-template-override/35443/1 "2015-11-24T11:52:04Z")

</div>

Hi,  
Does kibana/marvel handle overriding the default index template e.g. to raise the shard value? I tried doing this the other day only to find that kibana/marvel could no longer find the cluster and I started to see Serialization exceptions in the elasticsearch client node logs.

After deleting the template and restarting the cluster, created according to the guidance shown here, though with a different name:

[https://www.elastic.co/guide/en/marvel/current/configuration.html](https://www.elastic.co/guide/en/marvel/current/configuration.html)

...the cluster was discovered again. However, I now have marvel running too few shards which will create its own problems.

Regards,  
David

---

<div class="post-metadata">

**Author:** ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)\
**Post date:** [November 24, 2015, 1:15pm UTC](https://discuss.elastic.co/t/marvel-2-0-index-template-override/35443/2 "2015-11-24T13:15:46Z")

</div>

Hi,

You can create another index template on your monitoring cluster that matches the marvel indices prefix and that declares the number of shards/replicas you want, for example:

```json
PUT /_template/marvel-with-shards 
{
  "template": ".marvel-es-2*", 
  "order":1,
  "settings": {
    "index.number_of_shards": 7, 
    "index.number_of_replicas": 3
  }
}

```

New indices created by marvel will match this template.

-- Tanguy

---

<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:** [November 25, 2015, 12:56am UTC](https://discuss.elastic.co/t/marvel-2-0-index-template-override/35443/3 "2015-11-25T00:56:42Z")

</div>

Unless you are dealing with large clusters creating big indices (ie 50GB a day and above), I wouldn't worry too much.

---

<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:46pm UTC](https://discuss.elastic.co/t/marvel-2-0-index-template-override/35443/4 "2017-07-06T13:46:47Z")

</div>