Kibana is a free open-source analytics and visualization tool. You can install and configure Kibana to access the DevOps Insight server’s Elasticsearch instance. This section shows how to configure Kibana for this purpose.
Configuring the Kibana Server
-
Install the Kibana server.
This must be the same version as the Elasticsearch version used by DevOps Insight. For download and installation details, see https://www.elastic.co.
-
Open the
kibana.yml
file.This file is typically in the
/etc/kibana
directory if Kibana was installed via a repository or in the/opt/kibana/config
directory if extracted from a.zip
archive. -
Change the
elasticsearch.url
property to point to the Elasticsearch service on the machine where DevOps Insight is installed.Use the port number configured for Elasticsearch (port 9200 by default) in the URL. For example:
elasticsearch.url: "https://localhost:9200"
or
elasticsearch.url: "https://<your_domain>.com:9200".
-
Set the
elasticsearch.username
andelasticsearch.password
properties.Use the user name
kibanauser
and the password (changeme
by default) that you configured for the reporting user during DevOps Insight installation. For example:elasticsearch.username: "kibanauser"
elasticsearch.password: "changeme"
-
Disable the certificate validation.
To do so, set the
elasticsearch.ssl.verificationMode
property as follows:elasticsearch.ssl.verificationMode: none
-
(Optional) Specify the IP address that the Kibana server should listen to.
If the Kibana server should listen to all IPv4 addresses, set it to
0.0.0.0
as follows:server.host: "0.0.0.0"
Verifying the Kibana Server Configuration
-
Start the Kibana server.
-
Browse to the Kibana web application.
In the URL, use the machine where Kibana is running and the port number (5601 by default). For example, enter
localhost:5601
orhttps://<your_domain>.com:5601
. -
Log into the Kibana web application to verify that you can access the DevOps Insight data.
Log in as
kibanuser
, and enter the password specified during DevOps Insight installation.
The kibanauser user can access only the ef-* indices (but not indices such as searchguard-* and logstash-*). In the Elasticsearch log, this access limitation might cause errors to appear, which you can ignore.
|