# Marvel: Error 400 Bad Request: \[index\_not\_found\_exception\] no such index, with: {"index":"\[.marvel-es-1-\*\]"}

**URL:** <https://discuss.elastic.co/t/marvel-error-400-bad-request-index-not-found-exception-no-such-index-with-index-marvel-es-1/52720>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [June 14, 2016, 10:36am UTC](https://discuss.elastic.co/t/marvel-error-400-bad-request-index-not-found-exception-no-such-index-with-index-marvel-es-1/52720 "2016-06-14T10:36:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kiran\_Reddy](https://avatars.discourse-cdn.com/v4/letter/k/e9a140/32.png) [@Kiran\_Reddy](https://discuss.elastic.co/u/Kiran_Reddy)\
**Post date:** [June 14, 2016, 10:36am UTC](https://discuss.elastic.co/t/marvel-error-400-bad-request-index-not-found-exception-no-such-index-with-index-marvel-es-1/52720/1 "2016-06-14T10:36:52Z")

</div>

Hi all,

First of all i am new to elastic search and therefore this might be a silly mistake on my side if so, I apologize before hand.

I am getting the below error when ever i try to access the marvel plugin on kibana.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/d/d6b32af72c1915175623a11c2e7d031d57097c59.png)

Please help me resolving it. I have the below products installed  
ElasticSearch 2.3.3  
Kibana 4.5.1  
shield 2.3.3

The error occurs only when accessing the marvel plugin from a specific user whose role description is as below.

# The required permissions for the kibana 4 server

kibana4\_server:  
cluster:  
- cluster:monitor/nodes/info  
- cluster:monitor/health  
indices:  
'.kibana':  
- indices:admin/exists  
- indices:admin/mapping/put  
- indices:admin/mappings/fields/get  
- indices:admin/refresh  
- indices:admin/validate/query  
- indices:data/read/get  
- indices:data/read/mget  
- indices:data/read/search  
- indices:data/write/delete  
- indices:data/write/index  
- indices:data/write/update  
'\*':  
- indices:admin/mappings/fields/get  
- indices:admin/validate/query  
- indices:data/read/search  
- indices:data/read/msearch  
- indices:admin/get

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [June 14, 2016, 4:55pm UTC](https://discuss.elastic.co/t/marvel-error-400-bad-request-index-not-found-exception-no-such-index-with-index-marvel-es-1/52720/2 "2016-06-14T16:55:54Z")

</div>

> I have the below products installed
> 
> - Elasticsaerch 2.3.3
> - Kibana 4.5.1
> - Shield 2.3.3

As you're trying to use Marvel, you also need Marvel installed. I assume based on the error that you have Marvel installed within Kibana. The easiest way to check if it's installed is to visit the Kibana Status page:

Kibana Status Page: [http://host:5601/app/status](http://host:5601/app/status)

If `marvel` is not listed there, then it is not installed. You can follow step #5 from [Installing Marvel](https://www.elastic.co/guide/en/marvel/current/installing-marvel.html#monitoring-cluster) for that.

On the other side, you need to have the Marvel Agent (and license plugin, but that's also a dependency of Shield) installed within Elasticsearch. The easiest way to check if that's installed is ES `_cat` plugins API.

```auto
$ curl -XGET http://host:_cat/plugins?v

```

If you do not see `marvel-agent` as installed, then you need to follow step #3 from the above link.

There's another possibility that your user cannot see the index because of a role misconfiguration. I would suggest simplifying your [Kibana 4 user role](https://www.elastic.co/guide/en/shield/current/kibana.html#kibana4-user-role) using the new, simplified roles:

```auto
my_kibana_user:
  cluster:
      - monitor
  indices:
    - names: '*'
      privileges:
        - view_index_metadata
        - read
    - names: '.kibana*' 
      privileges:
        - manage
        - read
        - index

```

**NOTE** : The kibana4\_server _role_ is used by the server and it's predefined in the roles.yml!

Your user also needs to have the [pre-defined `marvel_user` role](https://www.elastic.co/guide/en/shield/current/marvel.html#marvel-app-users).

At least one of those 3 issues is most likely to blame, and the `marvel_user` role seems like the most likely culprit. However, by using the latest Kibana role with `*` granting universal read access, it will give you the access needed.

---

<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:43pm UTC](https://discuss.elastic.co/t/marvel-error-400-bad-request-index-not-found-exception-no-such-index-with-index-marvel-es-1/52720/3 "2017-07-06T13:43:09Z")

</div>