Improvements for Grok Debugging within Graylog

## What?

Grok is a very powerful solution for parsing logs without the barrier of learning regular expressions. There are some examples where this can be challenging to be performed in Graylog.

## An example custom Grok pattern


### Improvement 1: The Grok debugger tool should reflect the syntax used by Graylog

When escaping is required and not required is very unclear in Graylog GROK. Square brackets are the most common cause of grief. Here is a rule using exactly the copy-pasted pattern above, which parsed successfully in the Pattern editor:

### Improvement 2: Reflect the grok options used by Graylog
There is no way to indicate: "Named Captures Only" while using the pattern editor, so you often see many subpatterns you may not wish to see and in longer, complicated logs this can get difficult.

### Improvement 3: Searching Filter pattern only shows the top 8 results and they're double-spaced (can't search for 'word' or 'greedy')

### Improvement 4: Not having to arbitrarily name something just to do a debug test to build a rule

Just for comparison's sake - here is the same function in Kibana:

### Improvement 5: Word wrap in Pipeline rules

Without this - any grok pattern longer than 100 characters (most of them) become difficult to edit in the browser. Most of those I've conversed with use a workflow of 'Code Editor : Build & Debug -> Rule editor: Additional Build & Debug' so they can see what they're doing, but obviously there is no way of syntax-checking a pipeline rule in a code editor.

### Improvement 6: Allow multiline sample data

Its a bit misleading that it allows, and does not produce error or warning, multiple lines of log data but only parses the first. This behaviour initially leads the user to believe you're not matching the second line of log data. I have certainly spent time debugging a pattern wondering why I wasn't matching a second line.

# Thanks for your time.

## Why?

Currently, with certain online tools having gone offline recently - it is now a rather tedious process to create Grok patterns.

These are only suggestions - I would just love to see an improvement to using Grok in Graylog as its a very powerful way of extracting data and currently there are some challenges to realizing that power.

## Your Environment

* Graylog Version: Cloud 5.0.0 - but exact same as self-hosted
* Elasticsearch Version: ??
* MongoDB Version:??
* Operating System: ??
* Browser version: