从Flume到Kafka的日志流配置

上次我们把环境安装完了，这次我们就来搞定配置。
类似于武林的打通任督二脉，这次我们来打通从Nginx日志到Flume日志采集再到Kafka消费日志消息

参考：

https://www.jianshu.com/p/8d34a9a5fc01

https://cloud.tencent.com/developer/article/1147852

https://blog.csdn.net/liuwei0376/article/details/60877878

https://blog.csdn.net/qq807237096/article/details/78749325

https://blog.csdn.net/ctwy291314/article/details/80089844

Flume 配置

创建新的Flume的conf设置，用来采集nginx日志，并将日志传给kafka

[user@magic conf]$ touch conf/flume-log-conf.properties
[user@magic conf]$ vim conf/flume-log-conf.properties 

具体配置如下，source采用tail命令跟踪nginx的access的日志
然后通道采用内存通道，然后转发至9092端口，供给Kafka进行消费

agent1.sources=r1
agent1.channels=c1
agent1.sinks=k1
 
agent1.sources.r1.type=exec
agent1.sources.r1.command=tail -F /var/log/nginx/access.log
agent1.sources.r1.channels=c1
 
agent1.channels.c1.type=memory
agent1.channels.c1.capacity=10000
agent1.channels.c1.transactionCapacity=100
 
agent1.sinks.k1.type=org.apache.flume.sink.kafka.KafkaSink
agent1.sinks.k1.topic=log-collect
agent1.sinks.k1.brokerList=192.168.52.130:9092
agent1.sinks.k1.requiredAcks=1
agent1.sinks.k1.batchSize=20
agent1.sinks.k1.channel=c1

这边需要更改一下Nginx日志的权限，否则读不到nginx日志（默认640只允许Nginx服务的运行用户（注意不是启动Nginx的用户）及用户组运行

$ cat /etc/logrotate.d/nginx

更改create 640 nginx adm 为create 644 nginx adm就行了

假如原来有日志了，需要去将原本创建的日志文件改一下权限

$ sudo chmod a+r /etc/log/nginx/access.log 

Kafka配置

kafka的集群的话我们这边通过改配置达到实现，不过鉴于我们只有一个日志采集的，所以先配置一台服务器
基本上kafka的一个消费布置在一个Zookeeper上

[user@magic kafka_2.12-2.5.0]$ cat  config/server-1.properties 
# 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

############################# 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://magic: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://your.host.name: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 that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3

# The number of threads that the server uses for processing requests, which may include 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 separated list of directories under which to store log files
log.dirs=/home/user/data/kafka/kafkalogs-1

# 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

############################# Internal Topic Settings  #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=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 excessive 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 unless the remaining
# segments 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=magic:2181

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


############################# Group Coordinator Settings #############################

# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0

对于不同的Server-n的配置可以采用如下（就是需要改的地方）

# 当前机器在集群中的唯一标识，和zookeeper的myid性质一样
broker.id=n
listeners=PLAINTEXT://magic:9093 # 不同server的监听端口，别重复

# 当前kafka节点对外提供服务的端口
port=9093

# 配置kafka消息目录，主要用于存储kafka消息，要注意也要用不同的目录
log.dirs=/home/user/data/kafka/kafkalogs-n

运行

启动Flume

$ ./bin/flume-ng agent --conf ./conf --conf-file ./conf/flume-log-conf.properties --name agent1 -Dflume.root.logger=INFO,console

启动Kafka（多个服务器可采用多个配置

$ ./bin/kafka-server-start.sh -daemon ./config/server-1.properties

可用jps查看是否有Kafka进程，来确定是否启动成功

创建Topic

$ ./bin/kafka-topics.sh --create --zookeeper magic:2181 --replication-factor 1 --partitions 1 --topic log-collect

利用kafka控制到消费者查看及时消息日志，这边有个版本更新问题，0.9版本以前的kafka采用接收zookeeper的端口，0.9版本以后的直接采用kafka server监听的端口进行收集日志

$ ./bin/kafka-console-consumer.sh --zookeeper magic:2181 --topic log-collect --from-beginning # kafka version <0.9
$ ./bin/kafka-console-consumer.sh --bootstrap-server magic:9092 --topic log-collect --from-beginning #kafka version >=0.9

运行我们自己的web服务并尝试访问，发现可以成功收到日志消息