# Why reporting is a part of x-pack?

**URL:** <https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217>\
**Category:** Kibana\
**Created:** [December 26, 2017, 1:51pm UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217 "2017-12-26T13:51:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![yishain11](https://avatars.discourse-cdn.com/v4/letter/y/df705f/32.png) [@yishain11](https://discuss.elastic.co/u/yishain11)\
**Post date:** [December 26, 2017, 1:51pm UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217/1 "2017-12-26T13:51:07Z")

</div>

I want to ask a general question, regrading generating reports from kibana:  
A very useful feature of kibana is the abilty to generate reports and export dashboards and visualizations automaticly. The thing I don't get is why generating reports is fixed to installing a package that it's main focus is authentication and security.  
Plus, I tried severel times to install x-pack in my elastic stack 6.X just to get the reporting feature, and the amount of security configuration and security related error handeling was overwhelming.  
Why do I need to struggle with the security stuff that I'm not interested in just to get the reporting stuff?  
Is there a possibility that in one of the next versions of the elastic stack thos two things will be seperated?  
By the way: if it's not the place for this message, please show where should I write it.  
Thank you!

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [December 26, 2017, 3:11pm UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217/2 "2017-12-26T15:11:00Z")

</div>

Hi @yishain11,

When it comes to specialized functionality, it is generally added to X-pack instead of Kibana core. Reporting, which includes pdf and csv exports, falls into that bucket. There's a grey zone of course, and I understand this could be useful in more general situations too.

As for the security-setup that comes with X-pack, you can avoid this by turning off the security-plugin.

In both the `config/elasticsearch.yml` and the `config/kibana.yml` files, turn of the plugin by adding this line:

```auto
xpack.security.enabled: false

```

This will turn off security, but keep Reporting activated.

---

<div class="post-metadata">

**Author:** ![yishain11](https://avatars.discourse-cdn.com/v4/letter/y/df705f/32.png) [@yishain11](https://discuss.elastic.co/u/yishain11)\
**Post date:** [December 26, 2017, 3:32pm UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217/3 "2017-12-26T15:32:51Z")

</div>

Hi, thanks for the answer.  
If I set the security plugin off, can I ignore all the setup in the x-pack documentation? Because the documentation of x-pack doesn't show this option at all, but present as if you can't install x-pack without it.

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [December 26, 2017, 3:36pm UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217/4 "2017-12-26T15:36:26Z")

</div>

yes, you'll be able to ignore the setup for that particular plugin. [https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html#xpack-enabling](https://www.elastic.co/guide/en/x-pack/current/installing-xpack.html#xpack-enabling)

So when you turn off `xpack.security` you can ignore all the other parameters under `xpack.security.*` (so ignore everything here [https://www.elastic.co/guide/en/elasticsearch/reference/6.1/security-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.1/security-settings.html)).

---

<div class="post-metadata">

**Author:** ![yishain11](https://avatars.discourse-cdn.com/v4/letter/y/df705f/32.png) [@yishain11](https://discuss.elastic.co/u/yishain11)\
**Post date:** [December 27, 2017, 9:13am UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217/5 "2017-12-27T09:13:15Z")

</div>

Thank you. Everything works

---

<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:** [January 24, 2018, 9:13am UTC](https://discuss.elastic.co/t/why-reporting-is-a-part-of-x-pack/113217/6 "2018-01-24T09:13:25Z")

</div>

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