我要评分
获取效率
正确性
完整性
易理解

Deploying Kibana

Deployment Planning

Node

IP Address

Number of Drives

OS

JDK

Node 1

IPaddress2

System drive: 1 x RAID 0 (1 x 1.2 TB SAS HDD)

Data drive: 4 x RAID 5 (12 x 1.2 TB SAS HDD)

aarch64-linux-4.14.0-115.el7a.0.1.aarch64

OpenJDK version "1.8.0_181"

Deployment Process

  1. Download and decompress the Kibana installation package.
    1
    2
    wget https://artifacts.elastic.co/downloads/kibana/kibana-6.7.0-linux-x86_64.tar.gz
    tar -zxf kibana-6.7.0-linux-x86_64.tar.gz
    
  2. Set parameters.
    1. Open the configuration file.
      1
      vi kibana-6.7.0-linux-x86_64/config/kibana.yml
      
    2. Press i to enter the insert mode and modify the parameters as required.
      server.port: 5601
      server.host: "0.0.0.0"
      elasticsearch.hosts: "http://IPaddress2:9200"
      kibana.index: ".kibana"
    3. Press Esc, type :wq!, and press Enter to save the file and exit.
  3. Replace the node folder in kibana-6.7.0-linux-x86_64.
    1. Download the Node.js of the ARM64 version.
      1
      2
      3
      wget https://nodejs.org/dist/v10.15.2/node-v10.15.2-linux-arm64.tar.xz
      xz -d node-v10.15.2-linux-arm64.tar.xz
      tar -xvf node-v10.15.2-linux-arm64.tar
      

      Kibana provides only the Kibana installation package with Node.js for x86. Therefore, you need to download the ARM64 Node.js installation package by yourself and decompress it to overwrite the node folder generated after kibana-6.7.0-linux-x86_64.tar.gz is decompressed.

    2. Replace the node folder.
      1
      2
      rm -rf kibana-6.7.0-linux-x86_64/node//node
      mv node-v10.15.2-linux-arm64/* kibana-6.7.0-linux-x86_64/node/
      
  4. Run Kibana.
    1
    ./kibana-6.7.0-linux-x86_64/bin/kibana
    
  5. Enter the following URL in the address box of a browser to access the UI:
    http://IPaddress2:5601

Testing the Deployment

  • View all indexes in the cluster.
    • Enter the following information in the Dev Tools console:
      GET _cat/indices?v
    • The result is as follows:

  • View data of all types under an index in the cluster.
    • Enter the following information in the Dev Tools console:
      GET /geonames/_search
      {
        "query": {
          "match_all": {}
        }
      }

      geonames indicates the index to be queried.

    • The result is as follows: