I am parsing proxy logs with Logstash and its Grok filter. The logs contain quoted strings :
1438120705 [.....] "SEF-EDP8" - "C"
"/GPM/1023/5745-7/456V/"
With the Grok Debugger the following pattern works like a charm :
%{NUMBER:ts} [......] (-|"%{USERNAME:token1}") (-|%{DATA:token2}) (-|"%{WORD:token3}") (-|"%{DATA:token4}")
This does not work with Logstash's Grok because of the double quotes in the grok pattern. Logstash error log :
Error: Expected one of #, {, } at line 9, column 204 (byte 374) after
filter {
grok {
match => { "message" => "%{NUMBER:ts} [......] ("
So I use the QuotedString grok pattern instead :
%{NUMBER:ts} [......] (-|%{QS:token1}) (-|%{DATA:token2}) (-|%{QS:token3}) (-|%{QS:token4})
This works with the Grok Debugger as well, but quotes are extracted with quoted strings. It doesn't work with Logstash either :
token1 : ""SEF-EDP8"" token2 : null token3 : ""C"" token4 :
""/GPM/1023/5745-7/456V/""
How can I make it work with Logstash? How can I remove these unwanted extra double quotes?
%{NUMBER:ts} \[[^\]]*] (-|"(%{DATA:token1})") (-|"(%{DATA:token2})") (-|"(%{DATA:token3})")( (-|"(%{DATA:token4})"))
. I have no more example input, so, not sure it will work with all of them. – HoverQS
matches the quotes strings by design. You needDATA
tokens. – Hover