# ELK 5.3.2 with X-Pack - don't have "Monitoring" menu in Kibana

**URL:** https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529
**Category:** Kibana
**Created:** [May 4, 2017, 10:03am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529 "2017-05-04T10:03:17Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)
#### Post date: [May 4, 2017, 10:03am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/1 "2017-05-04T10:03:17Z")

</div>

I don't see "Monitoring" menu in Kibana at all.  
I added "xpack.monitoring.enabled: true" into Kibana/Elastic configs, I do see monitoring indices  
green open .monitoring-data-2 E25MaWstS\_KsKn7m2Fp3iw 1 0 2 0 4kb 4kb  
green open .monitoring-es-2-2017.05.04 3iDodJbQTTmGKlsEtHbAZg 1 0 358 6 258.6kb 258.6kb

But "Monitoring" tab is missing from the menu.

Any ideas?

TIA, Vitaly

---

<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: [May 4, 2017, 10:07am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/2 "2017-05-04T10:07:23Z")

</div>

Did you restart KB?

---

<div class="post-metadata">

### Author: ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)
#### Post date: [May 4, 2017, 10:24am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/3 "2017-05-04T10:24:33Z")

</div>

Yes, restarted Kibana; and I don't see something relevant in its logs.

---

<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: [May 4, 2017, 10:30am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/4 "2017-05-04T10:30:26Z")

</div>

And you installed X-Pack in KB too?

---

<div class="post-metadata">

### Author: ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)
#### Post date: [May 4, 2017, 10:44am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/5 "2017-05-04T10:44:49Z")

</div>

Yes:  
/usr/share/kibana/bin/kibana-plugin list  
x-pack@5.3.2

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [May 4, 2017, 10:55am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/6 "2017-05-04T10:55:58Z")

</div>

May be clean the browser cache?

---

<div class="post-metadata">

### Author: ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)
#### Post date: [May 4, 2017, 10:57am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/7 "2017-05-04T10:57:00Z")

</div>

Oops! The same stupid ownership issue as with Elactic.  
After  
chown -R kibana /usr/share/kibana/plugins/x-pack  
chown -R kibana /usr/share/kibana/optimize/

and restarting Kibana I have Monitoring/Graphs menus.

Weird that it was nothing into logs. And in general, it's not an issues that I'll expect from enterprise software...

Mark, many thanks!

---

<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: [May 4, 2017, 10:58am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/8 "2017-05-04T10:58:13Z")

</div>

That is not standard behaviour.  
Can you replicate it?

---

<div class="post-metadata">

### Author: ![Vitaly\_il](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaly_il/32/130964_2.png) [@Vitaly\_il](https://discuss.elastic.co/u/Vitaly_il)
#### Post date: [May 4, 2017, 11:32am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/9 "2017-05-04T11:32:12Z")

</div>

It was "fresh" CIS-hardened Ubuntu 14.04 image. I don't have another Ubuntu instance for testing right now, but i'm pretty sure that these issues are reproducible (I mean this one and [https://github.com/elastic/elasticsearch/issues/24480](https://github.com/elastic/elasticsearch/issues/24480)).

---

<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: [June 1, 2017, 11:32am UTC](https://discuss.elastic.co/t/elk-5-3-2-with-x-pack-dont-have-monitoring-menu-in-kibana/84529/10 "2017-06-01T11:32:16Z")

</div>

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