# Kibana ignores console.enabled setting

**URL:** <https://discuss.elastic.co/t/kibana-ignores-console-enabled-setting/96981>\
**Category:** Kibana\
**Created:** [August 14, 2017, 2:32pm UTC](https://discuss.elastic.co/t/kibana-ignores-console-enabled-setting/96981 "2017-08-14T14:32:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [August 14, 2017, 3:09pm UTC](https://discuss.elastic.co/t/kibana-ignores-console-enabled-setting/96981/2 "2017-08-14T15:09:25Z")

</div>

Hi,

Dev tools contain only console in OSS Kibana and also has profiler and grokdebugger if you have x-pack.  
**_console.enabled: false_** should definitely work for disabling console. But profiler and grok debugger will need to be disabled separately as well. Can you please check if your Kibana has x-pack installed?

Also whenever you change /add/delete anything in Kibana.yml - when you restart, Kibana will need to optimize again. It looks like this in logs: `log [15:03:08.119] [info][optimize] Optimizing and caching bundles for kibana, stateSessionStorageRedirect, timelion and status_page. This may take a few minutes`

Can you please check if you see this in your logs?

Thanks  
Bhavya

---

_[View the full topic](https://discuss.elastic.co/t/kibana-ignores-console-enabled-setting/96981)._