当前位置: 首页 > news >正文

网站开发用什么系统比较好?做网站开发使用百分比的好处

网站开发用什么系统比较好?,做网站开发使用百分比的好处,上街网站建设,中山做网站前言#xff1a; kibana是比较好安装的#xff0c;但https密码就比较麻烦一些了#xff0c;下面将就如何安装一个可在生产使用的kibana做一个简单的讲述 一#xff0c; kibana版本和下载地址 这里我想还是强调一下#xff0c;kibana的版本需要和elasticsearch的版本一…前言 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上面的 [rootnode4 ~]# cat instances.yml instances:- name: node-1dns: [192.168.123.11]- name: node-2dns: [192.168.123.12]- name: node-3dns: [192.168.123.13] - name: node-4dns: [192.168.123.14]- name: node-5dns: [192.168.123.15]执行以下命令生成证书包 ###注生成的证书格式是pem的可以直接使用无需任何转换哪个服务器都可以随便找个服务器就可以了 /data/es/bin/x-pack/certutil cert ca --pem --in instances.yml --out /root/certs.zip 解压上面在root根目录下生成的证书包 在15服务器上证书放置在此目录下 [rootcentos5 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.keykibana的配置文件 [rootcentos5 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 servers 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 settings 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 doesnt 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 settings 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 此时是前台启动直接看日志 [rootcentos5 kibana]# tail -n 10 /var/log/kibana/kibana.log {type:log,timestamp:2023-12-15T23:48:48Z,tags:[status,plugin:searchprofiler6.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:ml6.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:tilemap6.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:watcher6.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_management6.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:graph6.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:security6.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:grokdebugger6.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:logstash6.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:reporting6.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.dnsts.com.cn/news/141345.html

相关文章:

  • 建公司网站一般多少钱浅谈海尔的电子商务网站建设
  • 我的世界怎么自己做皮肤并上传网站怎么做网页的超链接
  • 钟落潭有没有做网站的网站如何做seo
  • 网站建设全部代码常德网站建设专业品牌
  • 承接做网站杭州seo 云优化科技
  • 静态购物网站模版网站开发服务器资源怎么弄
  • 高端网站建设方案范文手机 写wordpress
  • 新余市建设厅网站wordpress第一篇文章id
  • 潍坊专业建站ueditor wordpress4.7
  • 免费注册个人网站不花钱wordpress发不出验证邮件
  • 网站能找到做网站的人wordpress 建的网站吗
  • 动易的网站系统网站seo优化技术入门
  • 做网站公司如何赚钱网站关键词排名怎么做上去
  • 百度网站的优点专门做网页设计网站
  • 如何免费建立官方网站wordpress 2016
  • 济南软月建站怎么做自己的网站教程
  • 为企业做网站还有前途吗怎么建站网站
  • 长治网站制作安徽省住房与城乡建设厅网站
  • 域名和主机搭建好了怎么做网站网站开发经验
  • 清晰化网站在手机上创建网站
  • 教我做网站杭州 做网站
  • 科室建设网站收银会员卡管理系统
  • 广东营销网站制作软件开发资源网站
  • 个人建站网站三五做网站
  • 如何做网站监控wordpress侧面小工具
  • dt高端网站设计国外在线crm系统suitecrm
  • 2023年企业黄页查询手机端网站seo
  • 字体 wordpressseo点击软件手机
  • 公司网站哪家做的好网络工程师工资
  • 网站seo内部优化现在一般做网站用什么技术