# Reporting not able to use multiple kibana environments

**URL:** <https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [September 29, 2016, 5:33am UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766 "2016-09-29T05:33:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nubber](https://avatars.discourse-cdn.com/v4/letter/n/9e8a1a/32.png) [@Nubber](https://discuss.elastic.co/u/Nubber)\
**Post date:** [September 29, 2016, 5:33am UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/1 "2016-09-29T05:33:43Z")

</div>

In Plugin Package we found under path reporting/server/lib/constants.js that index of reporting is fixed. For our environment we would need that this is customizable.  
Please be aware that this would be needed for our environment and is a blocker for using this helpful plugin.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 29, 2016, 5:35am UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/2 "2016-09-29T05:35:07Z")

</div>

What's the use case behind wanting it customisable?

---

<div class="post-metadata">

**Author:** ![Nubber](https://avatars.discourse-cdn.com/v4/letter/n/9e8a1a/32.png) [@Nubber](https://discuss.elastic.co/u/Nubber)\
**Post date:** [September 29, 2016, 10:16am UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/3 "2016-09-29T10:16:01Z")

</div>

We use different kibanas for different indexes in connection with shield working on one elasticsearch cluster - hence multiple tenancy. But with only one index for reporting, reporting is available with the same report at every environment. But that is not a wanted scenario in our case.

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [October 10, 2016, 11:24pm UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/4 "2016-10-10T23:24:25Z")

</div>

This is a known issue with Reporting, and something we're actively trying to fix. Multiple tenancy is one of the bigger things we're trying to fix across all of our products, not just Reporting.

You're right, it's not possible at all right now, but we hope to get something workable out soon, even if it doesn't solve all multi-tenancy use cases right away.

---

<div class="post-metadata">

**Author:** ![Nubber](https://avatars.discourse-cdn.com/v4/letter/n/9e8a1a/32.png) [@Nubber](https://discuss.elastic.co/u/Nubber)\
**Post date:** [October 14, 2016, 6:32am UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/5 "2016-10-14T06:32:18Z")

</div>

Thank you, so please keep us updated.

---

<div class="post-metadata">

**Author:** ![Nubber](https://avatars.discourse-cdn.com/v4/letter/n/9e8a1a/32.png) [@Nubber](https://discuss.elastic.co/u/Nubber)\
**Post date:** [December 28, 2016, 11:30pm UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/6 "2016-12-28T23:30:12Z")

</div>

Hi there,

are there any news regarding this issue? because I've seen that in most new version 5.1.1 this issue is still alive.

Thank you in advance.

---

<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:42pm UTC](https://discuss.elastic.co/t/reporting-not-able-to-use-multiple-kibana-environments/61766/7 "2017-07-06T13:42:46Z")

</div>


