{"id":26494,"date":"2015-09-22T15:43:32","date_gmt":"2015-09-22T10:13:32","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=26494"},"modified":"2016-01-19T13:31:50","modified_gmt":"2016-01-19T08:01:50","slug":"applying-grok-patterns-in-elk","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/applying-grok-patterns-in-elk\/","title":{"rendered":"Applying GROK Patterns in ELK"},"content":{"rendered":"

Recently, I worked on filters in Logstash using different tools like grok, date etc. Many of us find grok patterns complex to write, so here I am writing this blog to make writing grok patterns easier.<\/p>\n

Use Case<\/strong><\/h3>\n

I had a use-case in which I had to filter logs from catalina.out, but it was difficult to filter the logs as there is not fixed pattern of logs in catalina.out. So I have created my own multiple filters to filter out the logs.<\/p>\n

Scope<\/strong><\/h3>\n

How to write filters in Logstash config file using different tools like grok and date?<\/p>\n

What is Logstash?<\/strong><\/h3>\n

An open source tool, written in JRuby, that requires Java on your machine, used for collecting and parsing logs. Installation steps can be referred here<\/a>.<\/p>\n

What is Filter?<\/strong><\/h3>\n

It is an in-line processing mechanism that parses the unstructured data and gives structured data as output. Currently, grok is the best way to structure crappy data in logs.<\/p>\n

What is GROK?<\/strong><\/h3>\n

It is used to match ‘n’ number of complex patterns on ‘n’ number of inputs and have customizable outputs thereby helps us to focus on ideas over syntax.
\nIt ships about 120 patterns with itself by default, hence eliminating repetitiveness and brings the idea of REUSABILITY<\/p>\n

Syntax<\/strong> of GROK is %{SYNTAX:SEMANTIC} where ,
\nSYNTAX:- Is the Pattern
\nSEMANTIC:- Is the name which we give to the matched pattern.<\/p>\n

<\/h3>\n

\u00a0For Example:<\/strong><\/h3>\n

We have Nginx-access logs like:
\n10.0.2.119 – – [09\/Sep\/2015:11:50:55 +0000] “GET \/versionInfo.txt HTTP\/1.1” 200 219 “-” “ELB-HealthChecker\/1.0” 0.003 0.003 .
\n10.0.2.119 – – [09\/Sep\/2015:11:50:55 +0000] “GET \/versionInfo.txt HTTP\/1.1” 200 219 “-” “ELB-HealthChecker\/1.0” 0.003 0.003<\/p>\n

Now, GROK Pattern can be written as shown below:<\/p>\n

[js]filter {
\nif [type] == "nginx-access" {
\ngrok {
\nmatch => [ "message" => "%{IP:client} %{USERNAME} %{USERNAME} \\[%{HTTPDATE:timestamp}\\] (?:"%{WORD:request} %{URIPATHPARAM:path} HTTP\/%{NUMBER:version}" %{NUMBER:response} %{NUMBER:bytes} "%{USERNAME}" %{GREEDYDATA:responseMessage})" ]
\n}
\n}
\n}
\n[\/js]<\/p>\n

 <\/p>\n

where,
\n%{IP}<\/strong>: It is used to filter the IP whether it is IPv4 or IPv6
\n%{USERNAME}:<\/strong> It is used to filter text, numbers, some special characters.
\n%{HTTPDATE}:<\/strong> It is used the timestamp according to the format in logs
\n%{WORD}<\/strong>: It is used to filter text upto one word
\n%{URIPATHPARAM}:<\/strong> It is used filter path from the logs.
\n%{NUMBER}<\/strong>: It is used to filter the number
\n%{GREEDYDATA}:<\/strong> It is used to filter the rest of the message.<\/p>\n

There are predefined formats which can be referred here<\/a>, using which we can make our own filters to see logs in the format we want in Logstash.<\/p>\n

GROK Pattern for Tomcat Logs<\/strong><\/h3>\n

The filter given below is according to the use case defined above:<\/p>\n

[js]
\nfilter {
\nif [type] == "catalina" {
\nmultiline {
\npattern => "(^\\s*|%{MONTH} %{MONTHDAY}, 20%{YEAR} %{HOUR}:?%{MINUTE}(?::?%{SECOND}) (?:AM|PM))|(^20%{YEAR}-%{MONTHNUM}-%{MONTHDAY} %{HOUR}:?%{MINUTE}(?::?%{SECOND}) %{ISO8601_TIMEZONE})"
\nnegate => true
\nwhat => "previous"
\n}
\nif "_grokparsefailure" in [tags] {
\ndrop { }
\n}
\ngrok {
\nmatch => { "message" => "(?:%{DATESTAMP:timestamp})(?:\\s*)(?:%{SYSLOG5424SD})(?:\\s*)(?:%{LOGLEVEL:log_type})(?:\\s*)%{GREEDYDATA:Message}" }
\nmatch => { "message" => "(?:\\s*)%{LOGLEVEL:log_type}(?:\\s*)%{GREEDYDATA:Message}" }
\nmatch => { "message" => "(?:\\s*)(?:%{GREEDYDATA:cache})" }
\n}
\ndate {
\nmatch => [ "timestamp", "yyyy-MM-dd HH:mm:ss,SSS Z", "MMM dd, yyyy HH:mm:ss a", "yy-MM-dd HH:mm:ss,SSS" ]
\n}
\n}
\n}[\/js]<\/p>\n

 <\/p>\n

Since Tomcat logs are multiline, we have defined date patterns in multiline. It is not full filter, it is used just to catch multiline logs in Tomcat or any application that generates multiline logs. At the first time, it will throw _grokparsefailure for sure because till now we have only matched the date. After successful date matching, it will surely match the pattern defined under grok function and henceforth will not throw any such error. There are different date patterns in Tomcat so multiple date patterns have been defined under date function, to match any of them.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Recently, I worked on filters in Logstash using different tools like grok, date etc. Many of us find grok patterns complex to write, so here I am writing this blog to make writing grok patterns easier. Use Case I had a use-case in which I had to filter logs from catalina.out, but it was difficult […]<\/p>\n","protected":false},"author":261,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":31,"footnotes":""},"categories":[2348],"tags":[],"class_list":["post-26494","post","type-post","status-publish","format-standard","hentry","category-devops-technology"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t