2017-07-18 40 views
0

用郵件的時間戳替換事件的時間戳對我來說不起作用。這裏是細節。Logstash:替換郵件不工作的時間戳

示例日誌:

20170119 144002.184140 0005B9427CA0_CU_1 user.notice ProcMon:: 10.220.0.13 is valid IP Address 

模式:

CSSYSLOGTIMESTAMP %{YEAR}%{MONTHNUM}%{MONTHDAY}[T ]%{HOUR}%{MINUTE}%{SECOND}.%{NONNEGINT:MSEC} 

篩選:

filter { 
    grok { 
    patterns_dir => ["/root/logstash-5.5.0/patterns"] 
    match => { "message" => "^%{CSSYSLOGTIMESTAMP:syslog_timestamp} %{DATA:syslog_hostname} %{DATA:syslog_level} %{DATA:app_name}: %{GREEDYDATA:syslog_message}" } 
    } 

    date { 
    match => ["syslog_timestamp" , "yyyyMMdd HHmmss.SSS"] 
    target => "@timestamp" 
    add_field => { "debug" => "timestampMatched"} 
    } 
} 

Logstash調試輸出:

[2017-07-18T10:25:01,152][DEBUG][logstash.pipeline  ] filter received {"event"=>{"@timestamp"=>2017-07-18T04:54:55.170Z, "offset"=>747452, "@version"=>"1", "input_type"=>"log", "beat"=>{"hostname"=>"node1", "name"=>"node1", "version"=>"5.5.0"}, "host"=>"node1", "source"=>"/root/samplelogs/Debug.log", "message"=>"20170119 144002.184140 0005B9427CA0_CU_1 user.notice ProcMon:: 10.220.0.13 is valid IP Address", "type"=>"log", "tags"=>["beats_input_codec_plain_applied"]}} 
[2017-07-18T10:25:01,154][DEBUG][logstash.filters.grok ] Running grok filter {:event=>2017-07-18T04:54:55.170Z node1 20170119 144002.184140 0005B9427CA0_CU_1 user.notice ProcMon:: 10.220.0.13 is valid IP Address} 
[2017-07-18T10:25:01,159][DEBUG][logstash.filters.grok ] Event now: {:event=>2017-07-18T04:54:55.170Z node1 20170119 144002.184140 0005B9427CA0_CU_1 user.notice ProcMon:: 10.220.0.13 is valid IP Address} 
[2017-07-18T10:25:01,165][DEBUG][logstash.pipeline  ] output received {"event"=>{"MSEC"=>"184140", "offset"=>747452, "input_type"=>"log", "source"=>"/root/samplelogs/Debug.log", "message"=>"20170119 144002.184140 0005B9427CA0_CU_1 user.notice ProcMon:: 10.220.0.13 is valid IP Address", "type"=>"log", "syslog_message"=>"10.220.0.13 is valid IP Address", "tags"=>["beats_input_codec_plain_applied", "_dateparsefailure"], "app_name"=>"ProcMon:", "@timestamp"=>2017-07-18T04:54:55.170Z, "syslog_hostname"=>"0005B9427CA0_CU_1", "syslog_timestamp"=>"20170119 144002.184140", "@version"=>"1", "beat"=>{"hostname"=>"node1", "name"=>"node1", "version"=>"5.5.0"}, "host"=>"node1", "syslog_level"=>"user.notice"}} 

我可以看到所有的字段被正確提取。消息時間戳記在syslog_timestamp字段中創建。但@timestamp不會被消息時間戳替換。 我在做什麼錯?謝謝。

回答

1

發現此問題。由於參考文檔中提到的文本,我只使用了最多3位小數(SSS)。

"S: fraction of a second Maximum precision is milliseconds (SSS). Beyond that, zeroes are appended." 

但事實證明,您仍然需要在定義過濾器時使用6S。

+0

date.match不能像grok.match一樣工作。 date.match要求整個字符串完全適合該模式。額外的字符是不容忍的。 – kubanczyk