# Problems with apache and marvel plugin

**URL:** <https://discuss.elastic.co/t/problems-with-apache-and-marvel-plugin/35623>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [November 26, 2015, 4:40am UTC](https://discuss.elastic.co/t/problems-with-apache-and-marvel-plugin/35623 "2015-11-26T04:40:05Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [December 3, 2015, 8:41am UTC](https://discuss.elastic.co/t/problems-with-apache-and-marvel-plugin/35623/9 "2015-12-03T08:41:52Z")

</div>

Can you check the logs on Elasticsearch side?

If you see something like this:

```auto
[2015-12-02 00:11:34,633][INFO][rest.suppressed] /.marvel-es-*/_field_stats Params: {level=indices, ignore_unavailable=true, index=.marvel-es-*}
java.lang.NullPointerException
	at org.elasticsearch.action.fieldstats.TransportFieldStatsTransportAction.newResponse(TransportFieldStatsTransportAction.java:122)

```

I think you hit this issue: [https://github.com/elastic/elasticsearch/pull/14868](https://github.com/elastic/elasticsearch/pull/14868)

It should be fixed in the next bugfix release.

---

_[View the full topic](https://discuss.elastic.co/t/problems-with-apache-and-marvel-plugin/35623)._