分析Nginx日志时Logstash_grokparsefailure

Question

我正在尝试使用Logstash解析nginx日志，除了用包含nginx$remote\u用户的行获取这个\u grokparsefailure标记外，一切看起来都很好。当$remote_user为“-”（未指定$remote_user时的默认值）时，Logstash将执行此任务，但使用真正的$remote_用户，如[e-mail]它失败并放置一个\u grokparsefailure标签：

127.0.0.1--[17/Feb/2017:23:14:08 0100]"GET/favicon.icoHTTP/1.1"302 169"http://training-hub.tn/trainer/"Mozilla/5.0（X11；Linuxx86_64）AppleWebKit/537.36（KHTML， like Gecko）Chrome/56.0.2924.87Safari /537.36"

=====

127.0.0.1 - [e-mail][17/Feb/2017:23:14:07 0100]“GET/trainer/templates/home.tmpl.html HTTP/1.1”304 0http://training-hub.tn/trainer/“Mozilla/5.0（X11；Linux x86_64）AppleWebKit/537.36（KHTML，类似Gecko）Chrome/56.0.2924.87 Safari/537.36”

=====

我正在使用此配置文件：

input {     
    file {      
        path => "/home/dev/node/training-hub/logs/access_log"       
        start_position => "beginning"       
        sincedb_path => "/dev/null"
        ignore_older => 0
        type => "logs"  
    }
}

filter {    
    if[type] == "logs" {        
        mutate {            
             gsub => ["message", "::ffff:", ""]         
        }       
        grok {          
             match=> [
               "message" , "%{COMBINEDAPACHELOG}+%{GREEDYDATA:extra_fields}",
               "message" , "%{COMMONAPACHELOG}+%{GREEDYDATA:extra_fields}"
             ]
             overwrite=> [ "message" ]
        }

        mutate {
          convert=> ["response", "integer"]
          convert=> ["bytes", "integer"]
          convert=> ["responsetime", "float"]
        }
        geoip {
          source => "clientip"
          target => "geoip"
          database => "/etc/logstash/GeoLite2-City.mmdb"
          add_field => [ "[geoip][coordinates]", "%{[geoip][longitude]}" ]
          add_field => [ "[geoip][coordinates]", "%{[geoip][latitude]}"  ]
        }
        mutate {
          convert => [ "[geoip][coordinates]", "float"]
        }

        date {
          match=> [ "timestamp", "dd/MMM/YYYY:HH:mm:ss Z" ]
          remove_field=> [ "timestamp" ]
        }

        useragent {
          source=> "agent"
        }   
     } 
 }

output {    elasticsearch {         hosts => "localhost:9200"   } }

Answer 1

在使用许多值测试输出后，我意识到Logstash无法解析包含此类$remote\u user的日志行，因为它不是有效的用户名（电子邮件地址），因此我添加了mutate gsub过滤器以删除@和邮件地址的其余部分，从而获得有效的$remote\u user。

gsub=

现在，它工作得很好