Marvel 2.0 - Index Template Override



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:

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


(Tanguy) #2


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:

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

New indices created by marvel will match this template.

-- Tanguy

(Mark Walkom) #3

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

(system) #4