# Generating reports for a remote index

**URL:** <https://discuss.elastic.co/t/generating-reports-for-a-remote-index/198938>\
**Category:** Elasticsearch\
**Created:** [September 10, 2019, 4:56pm UTC](https://discuss.elastic.co/t/generating-reports-for-a-remote-index/198938 "2019-09-10T16:56:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![o1o1o11o1](https://avatars.discourse-cdn.com/v4/letter/o/74df32/32.png) [@o1o1o11o1](https://discuss.elastic.co/u/o1o1o11o1)\
**Post date:** [September 10, 2019, 4:56pm UTC](https://discuss.elastic.co/t/generating-reports-for-a-remote-index/198938/1 "2019-09-10T16:56:40Z")

</div>

Hello,

We have 3 ES clusters 7.1 running in a remote-cluster setup. All works well, except generating reports from Kibana on a remote index e.g. `*:remoteindex-*`. The user has the `kibana_user` and `reporting_user` roles, trying to generate a report returns:

```
"statusCode":403,"response":"{\"error\":{\"root_cause\":[{\"type\":\"security_exception\",\"reason\":\"action [cluster:monitor/state] is unauthorized for user [some_user]\"}],\"type\":\"security_exception\",\"reason\":\"action [cluster:monitor/state] is unauthorized for user [some_user]\"},\"status\":403}"}

```

I couldn't find a `monitor/state` built-in role. Generating reports for local indices works fine.

---

<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:** [October 8, 2019, 5:07pm UTC](https://discuss.elastic.co/t/generating-reports-for-a-remote-index/198938/2 "2019-10-08T17:07:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.