场景:生产环境可集中式分析特定日志,便于管理,以及快速解决程序问题等。
常见:nginx、apache的访问日志,错误日志 日志等。可以把错误日志提取出并解决。
安装方式:
1)编译安装 常用组合 ELK+Reids+插件
)优点:方便管理
)缺点:需要手动安装配置,相对yum繁琐
2)yum安装
)优点:安装配置方便
)缺点:相对编译不太好管理(依赖关系等因素)
My eg:
注意事项:elk安装比较简单,但是要注意最低配置。这里我个人用的是编译安装,并且自己写的脚本。yum安装脚本可直接用。
[root@elk config]# /etc//node-elasticsearch status node(elasticsearch) is running... [root@elk config]# /etc//elasticsearch status elasticsearch is already running... [root@elk config]# java -version java version "_112" Java(TM) SE Runtime Environment (build _112-b15) Java HotSpot(TM) 64-Bit Server VM (build -b15, mixed mode) [root@elk config]# /etc//kibana status kibana is running... [root@elk config]#
注意地方:
:
[root@elk config]# cat |grep -v"$^"|grep -v "#" : elk : node1 : : 9200 : true -origin: "*" [root@elk config]# #elasticsearch配置允许跨域访问,这样head插件可以访问es。 #: true #-origin: "*"
:
[root@elk config]# cat |grep #: “localhost:9200” : “:9200” #url访问
logstash获取日志样板:(重点)
[root@elk config]# [root@elk config]# cat input { file { path => "/usr/local/tomcat-/logs/" #tomcat的日志路径 start_position => "beginning" } } filter { if [path] =~ "access" { mutate { replace => { "type" => "tomcat " } } grok { match => { "message" => "%{COMBINEDAPACHELOG}" } } } date { match => [ "timestamp" , "dd/MMM/yyyy:HH:mm:ss Z" ] } } output { elasticsearch { hosts => [":9200"] #elasticsearch地址 } stdout { codec => rubydebug } } [root@elk config]#
启动:logstash -f (测试)
kibana访问:
摘取tomcat最后启动成功状态日志:
January 11th 2017, 15:39::/usr/local/tomcat-/logs/ @timestamp:January 11th 2017, 15:39: @version:1 host: message:信息: Destroying ProtocolHandler ["ajp-bio-8009"] tags: _id:AVmMeAegJ7ojQvedm4_L _type:logs _index:logstash- _score: - January 11th 2017, 15:39::/usr/local/tomcat-/logs/ @timestamp:January 11th 2017, 15:39: @version:1 host: message:信息: Stopping ProtocolHandler ["ajp-bio-8009"] tags: _id:AVmMeAegJ7ojQvedm4_H _type:logs _index:logstash- _score: - January 11th 2017, 15:39::/usr/local/tomcat-/logs/ @timestamp:January 11th 2017, 15:39: @version:1 host: message:信息: Stopping ProtocolHandler ["http-bio-80"] tags: _id:AVmMeAegJ7ojQvedm4_F _type:logs _index:logstash- _score: -