Kibana not displaying X-pack features

[suyash]

Hi,

Iam first time user of ELK stack. I had installed Kibana 6.0.3 and ElasticSearch 6.0.3.

After running kibana and viewing the console , I am unable to view the x-pack features like graph,machinelearning..

Below is the log that I see

bin/kibana
  log   [17:41:08.238] [info][status][plugin:kibana@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.269] [info][status][plugin:elasticsearch@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.271] [info][status][plugin:xpack_main@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.275] [info][status][plugin:searchprofiler@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.277] [info][status][plugin:ml@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.304] [info][status][plugin:tilemap@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.305] [info][status][plugin:watcher@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.316] [info][status][plugin:license_management@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.318] [info][status][plugin:index_management@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.424] [info][status][plugin:timelion@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.426] [info][status][plugin:graph@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.428] [info][status][plugin:monitoring@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.429] [info][status][plugin:security@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.430] [warning][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml
  log   [17:41:08.432] [warning][security] Session cookies will be transmitted over insecure connections. This is not recommended.
  log   [17:41:08.451] [info][status][plugin:grokdebugger@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.455] [info][status][plugin:dashboard_mode@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.456] [info][status][plugin:logstash@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:08.468] [info][status][plugin:apm@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.472] [info][status][plugin:console@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.474] [info][status][plugin:console_extensions@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:08.476] [info][status][plugin:metrics@6.3.0] Status changed from uninitialized to green - Ready
  log   [17:41:09.025] [info][status][plugin:reporting@6.3.0] Status changed from uninitialized to yellow - Waiting for Elasticsearch
  log   [17:41:09.050] [info][listening] Server running at http://localhost:5601
  log   [17:41:09.055] [info][status][plugin:elasticsearch@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.064] [info][license][xpack] Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active
  log   [17:41:09.087] [info][status][plugin:xpack_main@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.087] [info][status][plugin:searchprofiler@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.088] [info][status][plugin:ml@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.088] [info][status][plugin:tilemap@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.089] [info][status][plugin:watcher@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.089] [info][status][plugin:index_management@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.089] [info][status][plugin:graph@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.090] [info][status][plugin:security@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.090] [info][status][plugin:grokdebugger@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.090] [info][status][plugin:logstash@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.091] [info][status][plugin:reporting@6.3.0] Status changed from yellow to green - Ready
  log   [17:41:09.099] [info][kibana-monitoring][monitoring-ui] Starting all Kibana monitoring collectors
  log   [17:41:09.106] [info][license][xpack] Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active

I went through the discussion forum link on similar case, but still not able to resolve
https://discuss.elastic.co/t/x-pack-enabled-kibana-not-showingup-xpack-features/134708

Any help on this would be much appreciated. Thanks.

[Stacey_Gammon]

You are running the basic license. You need to start a trial to see all the xpack stuff.

Management > License management should have an easy way to start the trial:

[suyash]

Hi Stacey,

Thank you very much for replying .I went through the reference documentation, which mentioned that I should be able to view the x-pack features by default .

https://www.elastic.co/guide/en/kibana/6.3/setup-xpack-kb.html

Graph is automatically enabled in Elasticsearch and Kibana.

To start exploring connections in your data:

Open Kibana in your web browser and log in. If you are running Kibana locally, go to http://localhost:5601/.
Click Graph in the side navigation to open the graph explorer.

I just want to confirm whether it would be displayed under basic license itself.

Thanks.

[Stacey_Gammon]

No they aren't available under the basic license. I have filed an issue in our docs repo, as it does indeed seem misleading. Thanks for highlighting the issue!

[suyash]

Thank you for your clarification.
Very much appreciated.