Elk 搭建记录(windows版)
1.最简单的logstash
logstash 由三部分配置组成 input、filter 和 output
1.安装下载 https://www.elastic.co/cn/downloads/logstash
2.选择目录解压
3.cmd切换到bin目录
3.1新建一个 first-pipeline.conf 配置文件，构建一个标准的input、 output
input {
stdin{
}
}
output {
stdout {
codec => rubydebug
}
}
执行命令启动logstash [ -f 指定配置文件， 后面的–config参数还未研究]
logstash -f first-pipeline.conf --config.reload.automatic
成功启动后会如下图 提示启动成功
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-PVDrSp9B-1609895836658)(C:\Users\dell\AppData\Roaming\Typora\typora-user-images\image-20201127171800842.png)]
可以看到 光标在闪，此处可以输入信息–> input 之后 output–>输出到控制台
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-mWNY2urQ-1609895836660)(C:\Users\dell\AppData\Roaming\Typora\typora-user-images\image-20201127171947850.png)]
2.进阶到logstash从kafaka取消息发送到 mongo 和 es
配置文件如下待补充和完善。官网6.5版本 https://www.elastic.co/guide/en/logstash/6.5/plugins-inputs-kafka.html#plugins-inputs-kafka-bootstrap_servers
input {
kafka {
bootstrap_servers => "192.168.41.71:9092" # 集群的话，中间用 [,] 逗号隔开
client_id => "freekai_logstash"
topics => ["freekaiTopic"]
auto_offset_reset => "latest"
type => "kafka1" # 定义type 用于下面 output输出时的判断
}
kafka {
bootstrap_servers => "192.168.41.71:9092"
client_id => "freekai_logstash2"
topics => ["freekaiTopic2"]
auto_offset_reset => "latest"
type => "kafka2"
}
}
output {
stdout {
codec => rubydebug
}
if[type] == "kafka1"{
mongodb {
uri => "mongodb://127.0.0.1:27017"
database => "test"
collection => "trace_log"
codec => json { charset => "UTF-8" }
}
}
if[type] == "kafka2"{
elasticsearch{
hosts => ["http://127.0.0.1"]
index => "trace_log"
timeout => 300
}
}
}
3.启动Zk、启动kafka
zk的启动很简单，进入对应的bin目录，双击ZkServer.bat文件即可
kafka的启动
进入kafka的安装目录--> bin的上一层目录
cmd执行 bin\windows\kafka-server-start.bat config\server.properties
3.1 server.properties – kafka
# 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://: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=E:\BaiduNetdiskDownload\kafka\dataLogs
# 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=localhost:2181
# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000
############################# 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
问题：
1.缺少mongobd插件（tip：注意安装3.1.5版本的）
./logstash-plugin install --version=3.1.5 logstash-output-mongodb
# 否则可能会出现
ArgumentError: wrong number of arguments (given 2, expected 1)
2.logstash中的timestamp字段，比当前时间少8小时
#1.方案一（自测可用）
# 在logstash 的pipeline.conf中增加 filter， 对timestamp字段进行增加8小时的操作，
filter{
ruby {
code => "event.set('timestamp', event.get('@timestamp').time.localtime + 8*60*60)"
}
ruby {
code => "event.set('@timestamp',event.get('timestamp'))"
}
mutate {
remove_field => ["timestamp"]
}
}
# 2.方案二(未测试)
filter{
grok {
ruby {
code => "event.timestamp.time.localtime"
}
}
}