elasticsearch|大数据|kibana的安装（https+密码）

前言：

kibana是比较好安装的，但https+密码就比较麻烦一些了，下面将就如何安装一个可在生产使用的kibana做一个简单的讲述

一，

kibana版本和下载地址

这里我想还是强调一下，kibana的版本需要和elasticsearch的版本一致，小版本都不能差，否则，kibana将不能正确连接到elasticsearch

本例我使用的是elasticsearch-6.3.2版本，因此，下载的kibana版本也是6.3.2

官方下载地址：

Kibana 6.3.2 | Elastic

两个版本二进制和rpm基本没有什么区别，想折腾点就二进制了，不想太麻烦rpm即可，看自己的需求啦。

不过要吐槽一下，官网下载比较慢，即使科学上网仍然很慢，因此，是需要一点耐心了

下载完毕后，没什么好说的，扔到服务器上就可以了

二，

elasticsearch的证书

kibana是安装在192.168.123.15上面的

[root@node4 ~]# cat instances.yml 
instances:- name: "node-1"dns: ['192.168.123.11']- name: "node-2"dns: ['192.168.123.12']- name: "node-3"dns: ['192.168.123.13']    - name: 'node-4'dns: ['192.168.123.14']- name: 'node-5'dns: ['192.168.123.15']

执行以下命令生成证书包：

###注：生成的证书格式是pem的，可以直接使用，无需任何转换（哪个服务器都可以，随便找个服务器就可以了）

/data/es/bin/x-pack/certutil cert ca --pem --in instances.yml --out /root/certs.zip
解压上面在root根目录下生成的证书包

在15服务器上，证书放置在此目录下：

[root@centos5 kibana]# ls -al ca.crt node-5.crt node-5.key 
-rw-r--r-- 1 root root 1200 Dec 15 23:07 ca.crt
-rw-r--r-- 1 root root 1180 Dec 15 23:07 node-5.crt
-rw-r--r-- 1 root root 1679 Dec 15 23:07 node-5.key

kibana的配置文件：

[root@centos5 kibana]# cat config/kibana.yml 
# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 15666# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: 192.168.123.15# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576# The Kibana server's name.  This is used for display purposes.
server.name: mykibana# The URL of the Elasticsearch instance to use for all your queries.
elasticsearch.url: https://192.168.123.11:19200# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"# The default application to load.
#kibana.defaultAppId: "home"# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
elasticsearch.username: elastic
elasticsearch.password: "123456"# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
server.ssl.enabled: true
server.ssl.certificate: /opt/kibana/node-5.crt
server.ssl.key: /opt/kibana/node-5.key# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
elasticsearch.ssl.certificateAuthorities: [ "/opt/kibana/ca.crt" ]# To disregard the validity of SSL certificates, change this setting's value to 'none'.
elasticsearch.ssl.verificationMode: certificate# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [ authorization ]# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 30000# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.
#elasticsearch.logQueries: false# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid# Enables you specify a file where Kibana stores log output.
logging.dest: /var/log/kibana/kibana.log# Set the value of this setting to true to suppress all logging output.
#logging.silent: false# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
#ops.interval: 5000# The default locale. This locale can be used in certain circumstances to substitute any missing
# translations.
i18n.defaultLocale: "zh-CN"

根据配置文件，创建目录：

mkdir /var/log/kibana

三，

启动kibana

/opt/kibana/bin/kibana

此时是前台启动，直接看日志：

[root@centos5 kibana]# tail -n 10  /var/log/kibana/kibana.log 
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:searchprofiler@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:ml@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:tilemap@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:watcher@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:index_management@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:graph@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:security@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:grokdebugger@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:logstash@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}
{"type":"log","@timestamp":"2023-12-15T23:48:48Z","tags":["status","plugin:reporting@6.3.2","info"],"pid":1572,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"This version of Kibana requires Elasticsearch v6.3.2 on all nodes. I found the following incompatible nodes in your cluster: v6.2.4 @ 192.168.123.14:19200 (192.168.123.14), v6.2.4 @ 192.168.123.13:19200 (192.168.123.13), v6.2.4 @ 192.168.123.12:19200 (192.168.123.12), v6.2.4 @ 192.168.123.11:19200 (192.168.123.11)"}

未完待续！！！

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处：http://www.mzph.cn/news/224892.shtml

如若内容造成侵权/违法违规/事实不符，请联系多彩编程网进行投诉反馈email:809451989@qq.com，一经查实，立即删除！

相关文章

下载文件 后端返回给前端 response header 响应头

下载文件 后端返回给前端 response header 响应头

当浏览器在请求资源时，会通过http返回头中的content-type决定如何显示/处理将要加载的数据，如果这个类型浏览器能够支持阅览，浏览器就会直接展示该资源，比如png、jpeg、video等格式。在某些下载文件的场景中，服务端可能…
阅读更多...
代码审计中的安全测试方法

代码审计中的安全测试方法

安全测试的定义和分类代码审计是一种针对软件代码的安全测试方法，目的是发现并修复软件中的安全漏洞。安全测试是指对软件系统进行安全性评估的过程，包括静态分析、动态测试、黑盒测试等多种方法。在安全测试中，最常用的方法之一就是代码审计…
阅读更多...
【FunASR】Paraformer语音识别-中文-通用-16k-离线-large-onnx

【FunASR】Paraformer语音识别-中文-通用-16k-离线-large-onnx

模型亮点 模型文件: damo/speech_paraformer-large-vad-punc_asr_nat-zh-cn-16k-common-vocab8404-pytorchParaformer-large长音频模型集成VAD、ASR、标点与时间戳功能，可直接对时长为数小时音频进行识别，并输出带标点文字与时间戳： ASR模型…
阅读更多...
vue中哪些数组的方法可以做到响应式

vue中哪些数组的方法可以做到响应式

Vue2 中为什么直接通过数组的索引修改元素是不会触发视图更新 vue2 为什么不直接监听数组 Vue2 对于数组提供了一些变异方法 重写数组方法源码分析 定义拦截器将拦截器挂载到数组上面收集依赖 扩展：理解Vue2如何解决数组和对象的响应式问题 对复杂对象的处理 复杂对…
阅读更多...
目标检测图片截取目标分类图片

目标检测图片截取目标分类图片

如果要训练一个分类模型却没有特定的分类数据集怎么办呢？可以换一种思路，将带有该目标的图片对所有想要的目标进行画标注框然后进行截图，就能得到特定的分类数据了。这么做的目的是：带有该目标的图片可能不会少，但是带…
阅读更多...
MySQL作为服务端的配置过程与实际案例

MySQL作为服务端的配置过程与实际案例

MySQL是一款流行的关系型数据库管理系统，广泛应用于各种业务场景中。作为服务端，MySQL的配置过程对于数据库的性能、安全性和稳定性至关重要。本文将详细介绍MySQL作为服务端的配置过程，并通过一个实际案例进行举例说明。 一、MySQL服务端配…
阅读更多...
VSCode如何编辑Markdown文件

VSCode如何编辑Markdown文件

VSCode如何编辑Markdown文件 一、安装插件二、常用命令 一、安装插件 需要在VSCode安装一个插件Markdown Theme Kit 二、常用命令 1、CtrlShiftV 预览模式
阅读更多...
Spring Boot中实现邮件推送

Spring Boot中实现邮件推送

当发送邮件时，可能会遇到各种异常情况。为了帮助您处理这些异常并提供一个完整的解决方案，下面是一篇关于在Spring Boot中实现邮件推送并处理异常的博客，以Markdown格式呈现： 在Spring Boot中实现邮件推送并处理异常 在许多应用…
阅读更多...
网络安全试题——附答案

网络安全试题——附答案

选择题示例： 在网络安全中，什么是“DDoS”攻击的全称？ a) Distributed Denial of Service b) Data Destruction of Service c) Direct Denial of Security d) Digital Defense of Servers 使用什么类型的加密可以确保在互联网上传输的数据是…
阅读更多...
云贝教育 |【技术文章】PG的流复制搭建

云贝教育 |【技术文章】PG的流复制搭建

一 主备机器规划主机名 主：192.168.2.103 db1 备：192.168.2.104 db2 二 创建流复制 2.1 修改主机配置(两台主机都修改) $ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localho…
阅读更多...
spring-cloud-stream-kafka生产速度慢

spring-cloud-stream-kafka生产速度慢

包版本spring-cloud-starter-stream-kafka:3.1.0 修改yaml配置 添加poller配置
阅读更多...
Python多态原理及实现

Python多态原理及实现

对于弱类型的语言来说，变量并没有声明类型，因此同一个变量完全可以在不同的时间引用不同的对象。当同一个变量在调用同一个方法时，完全可能呈现出多种行为（具体呈现出哪种行为由该变量所引用的对象来决定），…
阅读更多...
人工智能与低代码：前端技术的双重变革

人工智能与低代码：前端技术的双重变革

随着科技的飞速发展，人工智能（AI）和低代码开发平台已经成为当下热门的话题。在前端技术领域，这两大技术的崛起正在悄然改变开发模式，提高开发效率，降低技术门槛。本文将从以下几个方面，详细探讨…
阅读更多...
Netty介绍

Netty介绍

1. Netty介绍 是一个异步的、基于事件驱动的网络应用框架，用以开发高性能，高可靠性的网络io程序。Netty主要针对在TCP协议下，面向clients端的高并发应用，或者peer-to-peer场景下大量数据持续传输的应用。Netty本质上是一个NIO框架…
阅读更多...
12.15每日一题（备战蓝桥杯摘花生）

12.15每日一题（备战蓝桥杯摘花生）

12.15每日一题（备战蓝桥杯摘花生） 题目 摘花生 Hello Kitty想摘点花生送给她喜欢的米老鼠。 她来到一片有网格状道路的矩形花生地(如下图)，从西北角进去，东南角出来。 地里每个道路的交叉点上都有种着一株花生苗，上…
阅读更多...
都有哪些大厂开始适配鸿蒙原生应用呢

都有哪些大厂开始适配鸿蒙原生应用呢

12月8日，随着支付宝宣布启动鸿蒙原生应用开发以来，国内宣布接入鸿蒙原生应用开发的公司越来越多。事实上，自9月华为宣布鸿蒙原生应用全面启动以来，已有金融、旅行、社交等多个领域的企业和开发者陆续宣布加入鸿蒙生态，…
阅读更多...
配电房智能运维工具-电易云

配电房智能运维工具-电易云

配电房智能运维是将云计算、物联网、大数据与“互联网”服务理念相结合，采用“线上线下”的服务模式，为电力终端用户提供托管式配电智能运维服务。电易云智慧电力物联网是以提高电力运行安全，降低运维成本为目标，采用物联网、云计…
阅读更多...
Linux-CentOS7（无图形界面版）部署stable-diffusion-webui 全过程

Linux-CentOS7（无图形界面版）部署stable-diffusion-webui 全过程

Linux-CentOS7（无图形界面版）部署Stable Diffusion webui 全过程 前置要求 git的版本不能是CentOS默认的版本（1.8），版本太老，在后面安装过程会失败。去github上下载最新的git源码包 安装成功显示版本号 …
阅读更多...
ElasticSearch与HBase的分布式存储设计

ElasticSearch与HBase的分布式存储设计

本文内容覆盖如今两大非结构化数据库之间的区别 详情介绍 从各个角度详细对比 1. 官方定位 HBase 是 Hadoop 数据库，是一个分布式、可扩展的大数据存储。 当您需要对大数据进行随机、实时的读/写访问时，请使用 Apache HBase™。 这个项目的目标是在商用硬件集群上托管非常大…
阅读更多...
github 学习番外篇

github 学习番外篇

我们可以按照仓库开始的提示提交仓库 不知道为什么 出现了 我用 git branch 查看了一下，竟然没发现分支 后来发现是只有commit以后才会显示这个分支 后来显示 这是因为本地和远程仓库不同步的原因 这时候我们就需要git pull 一下 发现两个仓库由于不关联不能git…
阅读更多...
最新文章

Copyright @ 2022~2023