› ›

Grok Debugger

[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.

This content applies to:

You can build and debug grok patterns in the Grok Debugger before you use them in your data processing pipelines. Grok is a pattern-matching syntax that you can use to parse and structure arbitrary text. Grok is good for parsing syslog, apache, and other webserver logs, mysql logs, and in general, any log format written for human consumption.

Grok patterns are supported in Elasticsearch runtime fields, the Elasticsearch grok ingest processor, and the Logstash grok filter. For syntax, see Grokking grok.

Elastic ships with more than 120 reusable grok patterns. For a complete list of patterns, see Elasticsearch grok patterns and Logstash grok patterns.

Because Elasticsearch and Logstash share the same grok implementation and pattern libraries, any grok pattern that you create in the Grok Debugger will work in both Elasticsearch and Logstash.

Get started

edit

This example walks you through using the Grok Debugger.

Required roles

The Admin role is required to use the Grok Debugger. For more information, refer to Assign user roles and privileges

From the main menu, click Developer Tools, then click Grok Debugger.
In Sample Data, enter a message that is representative of the data you want to parse. For example:
```
55.3.244.1 GET /index.html 15824 0.043
```
In Grok Pattern, enter the grok pattern that you want to apply to the data.

To parse the log line in this example, use:
```
%{IP:client} %{WORD:method} %{URIPATHPARAM:request} %{NUMBER:bytes} %{NUMBER:duration}
```
Click Simulate.

You’ll see the simulated event that results from applying the grok pattern.

Test custom patterns

edit

If the default grok pattern dictionary doesn’t contain the patterns you need, you can define, test, and debug custom patterns using the Grok Debugger.

Custom patterns that you enter in the Grok Debugger are not saved. Custom patterns are only available for the current debugging session and have no side effects.

Follow this example to define a custom pattern.

In Sample Data, enter the following sample message:

Jan  1 06:25:43 mailserver14 postfix/cleanup[21403]: BEF25A72965: message-id=<20130101142543.5828399CCAF@mailserver14.example.com>

Enter this grok pattern:
```
%{SYSLOGBASE} %{POSTFIX_QUEUEID:queue_id}: %{MSG:syslog_message}
```
Notice that the grok pattern references custom patterns called POSTFIX_QUEUEID and MSG.
Expand Custom Patterns and enter pattern definitions for the custom patterns that you want to use in the grok expression. You must specify each pattern definition on its own line.

For this example, you must specify pattern definitions for POSTFIX_QUEUEID and MSG:
```
POSTFIX_QUEUEID [0-9A-F]{10,11}
MSG message-id=<%{GREEDYDATA}>
```
Click Simulate.

You’ll see the simulated output event that results from applying the grok pattern that contains the custom pattern:

If an error occurs, you can continue iterating over the custom pattern until the output matches your expected event.

« Search Profiler Painless Lab »