前段時間公司需要做一個日誌分析的需求，於是開始了對於日誌分析這方面的研究。現在系統中整合的是Fluem + elastaticSearch + 還有influxdb，如果基於這些做日誌分析的話，就可能需要使用Flume + kafka + elastaticSearch但是我對比了一下Flume和logstash 他們共同的特點是支援的採集方式很全，支援分散式。區別在於Flume作為生產方傳輸資料的功能比較強大，而logstash在做資料處理時支援grok表示式，在收集資料集進行格式化比較有優勢，綜合分析需求最後還是選擇使用ELK這一套技術架構。

廢話不多說了，開始幹正事。

版本:  elasticsearch-5.2.2

logstash-5.2.2

kafka_2.10-0.10.2.1(logstash + kafka必須使用0.9以上版本)

注意：版本問題一定要搞清楚，千萬別亂了，本人在版本上出過兩個問題，第一次是JavaAPI消費不了kafka裡面的資料。另一個是logstash的資料傳不進kafka。

一、首選安裝ElastaticSearch

1、首先在opt資料夾建立elasticsearch資料夾

mkdir elasticsearch

2、把elasticsearch-5.2.2.tar.gz拷貝到該目錄下解壓

tar -zxvf elasticsearch-5.2.2.tar.gz

network.host: 0.0.0.0

4、啟動。ES啟動為了安全是不支援root啟動的，需要使用其他使用者啟動

[[email protected] elasticsearch-5.2.2]# su me
[[email protected] elasticsearch-5.2.2]$ cd /opt/elasticsearch/elasticsearch-5.2.2/bin/
[[email protected]
 
 bin]$ ls -l
total 360
-rwxrwxrwx. 1 root root   7852 May 26 05:28 elasticsearch
-rwxrwxrwx. 1 root root   3341 May 26 05:28 elasticsearch.bat
-rwxrwxrwx. 1 root root    828 May 26 05:28 elasticsearch.in.bat
-rwxrwxrwx. 1 root root    404 May 26 05:28 elasticsearch.in.sh
-rwxrwxrwx. 1 root root   2540 May 26 05:28 elasticsearch-plugin
-rwxrwxrwx. 1 root root    733 May 26 05:28 elasticsearch-plugin.bat
-rwxrwxrwx. 1 root root  11239 May 26 05:28 elasticsearch-service.bat
-rwxrwxrwx. 1 root root 104448 May 26 05:28 elasticsearch-service-mgr.exe
-rwxrwxrwx. 1 root root 103936 May 26 05:28 elasticsearch-service-x64.exe
-rwxrwxrwx. 1 root root  80896 May 26 05:28 elasticsearch-service-x86.exe
-rwxrwxrwx. 1 root root    223 May 26 05:28 elasticsearch-systemd-pre-exec
-rwxrwxrwx. 1 root root   2514 May 26 05:28 elasticsearch-translog
-rwxrwxrwx. 1 root root   1435 May 26 05:28 elasticsearch-translog.bat
-rwxrwxrwx. 1 root root  16442 May 26 05:28 hs_err_pid6021.log
[[email protected] bin]$ ./elasticsearch

# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space

-Xms512m
-Xmx512m

mkdir Logstash

tar -zxvf logstash-5.2.2.tar.gz

input {
    file {
        path => "/opt/tomcat/apache-tomcat-8.5.15/logs/localhost_access_log.*.txt"#監控       本地的Tomcat access日誌
        start_position => "beginning"
    }
}

filter {
  grok {
      patterns_dir => "/opt/logstash/logstash-5.2.2/patterns" #指定正則檔案的存放位置
      match => {
      "message" => "%{ACCESSLOG}" #呼叫access日誌正則
      }
  }
}
output{
    stdout{ #標準輸出控制檯
        codec => rubydebug
    }
    elasticsearch {
      hosts => ["10.255.0.167"] #輸出到ES
        index => "tomcat-acccess" #索引名
    }
}

./logstash -f tomcat_access.config

mkdir zookeeper
mkdir kafka

tar -zxvf zookeeper-3.4.9.tar.gz

1. 啟動ZK服務:       ./zkServer.sh start
2. 停止ZK服務:       ./zkServer.sh stop
3. 重啟ZK服務:       ./zkServer.sh restart
4. 檢視ZK服務狀態:   ./zkServer.sh status

5.啟動後執行jps(QuorumPeerMain程序就是zookeeper獨立的程序s說明啟動成功)

6.在/opt/kafka目錄下解壓kafka_2.11-0.10.2.1.tgz

tar -zxvf kafka_2.11-0.10.2.1.tgz

# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# see kafka.server.KafkaConfig for additional details and defaults

############################# Server Basics #############################

# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0

# Switch to enable topic deletion or not, default value is false
#delete.topic.enable=true

############################# Socket Server Settings #############################

# The address the socket server listens on. It will get the value returned from 
# java.net.InetAddress.getCanonicalHostName() if not configured.
#   FORMAT:
#     listeners = listener_name://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
#listeners=PLAINTEXT://:9092

# Hostname and port the broker will advertise to producers and consumers. If not set, 
# it uses the value for "listeners" if configured.  Otherwise, it will use the value
# returned from java.net.InetAddress.getCanonicalHostName().
advertised.listeners=PLAINTEXT://10.255.0.167:9092

# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL

# The number of threads handling network requests
num.network.threads=3

# The number of threads doing disk I/O
num.io.threads=8

# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400

# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400

# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600


############################# Log Basics #############################

# A comma seperated list of directories under which to store log files
log.dirs=/tmp/kafka-logs

# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1

# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1

############################# Log Flush Policy #############################

# Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
#    1. Durability: Unflushed data may be lost if you are not using replication.
#    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
#    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.

# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000

# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000

############################# Log Retention Policy #############################

# The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
# from the end of the log.

# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining
# segments don't drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824

# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824

# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000

############################# Zookeeper #############################

# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000

./kafka-server-start.sh ../config/server.properties

./bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic test

bin/kafka-console-producer.sh --broker-list 10.255.0.167:9092 --topic test #該成自己的對應的IP

bin/kafka-console-consumer.sh --zookeeper 10.255.0.167:2181 --topic test #du對應自己的IP

#通過group_id 檢視當前詳細的消費情況
bin/kafka-consumer-groups.sh --group logstashtest--describe --zookeeper 127.0.0.1:2181
#檢視topic屬性
bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic topicname
#檢視kafka log檔案詳細資訊
bin/kafka-run-class.sh kafka.tools.DumpLogSegments --files /tmp/kafka-logs/test3-0/00000000000000000000.log  --print-data-log   #--files 對應的data資料路徑