# Marvel: sudden errors with index\_stats type

**URL:** <https://discuss.elastic.co/t/marvel-sudden-errors-with-index-stats-type/17456>\
**Category:** Elasticsearch\
**Created:** [May 12, 2014, 10:13am UTC](https://discuss.elastic.co/t/marvel-sudden-errors-with-index-stats-type/17456 "2014-05-12T10:13:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![poohsen](https://avatars.discourse-cdn.com/v4/letter/p/c89c15/32.png) [@poohsen](https://discuss.elastic.co/u/poohsen)\
**Post date:** [May 12, 2014, 10:13am UTC](https://discuss.elastic.co/t/marvel-sudden-errors-with-index-stats-type/17456/1 "2014-05-12T10:13:38Z")

</div>

Hi,

I'm sort of new to ES and currently evaluating how well it will work for  
storing and querying our log data.  
I installed Marvel and it worked fine for a while but now I'm suddenly  
getting weird errors and the index stats are gone from Kibana:

[2014-05-09 13:35:43,035][ERROR][marvel.agent.exporter] [Bushmaster] create failure (index:[.marvel-2014.05.09] type: [index\_stats]): MapperParsingException[failed to parse [index]]; nested: MapperParsingException[failed to parse date field [.marvel-2014.05.08], tried both date format [dateOptionalTime], and timestamp number with locale []]; nested: IllegalArgumentException[Invalid format: ".marvel-2014.05.08"];  
[2014-05-09 13:35:43,037][ERROR][marvel.agent.exporter] [Bushmaster] create failure (index:[.marvel-2014.05.09] type: [index\_stats]): MapperParsingException[failed to parse [index]]; nested: MapperParsingException[failed to parse date field [.marvel-2014.05.09], tried both date format [dateOptionalTime], and timestamp number with locale []]; nested: IllegalArgumentException[Invalid format: ".marvel-2014.05.09"];

I created a gist detailing the steps I took so far trying to understand/debug what's going on. While debugging, I realized that I'm unable to recreate a marvel index with the same mapping that it "normally" has (either created by marvel or by ES automapping). I detailed this in the gist, too:

> <https://gist.github.com/poohsen/a3d3bb319010bf0c5648>

Since I didn't temper with Marvel indices to begin with, I don't really see how it suddenly could've gone wrong other than because of a bug.

Any hints are appreciated.

Regards,

Chris

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/61d54877-c232-4a50-ae5d-301316fcc19a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/61d54877-c232-4a50-ae5d-301316fcc19a%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:30am UTC](https://discuss.elastic.co/t/marvel-sudden-errors-with-index-stats-type/17456/2 "2017-07-06T01:30:12Z")

</div>


