Describe the feature:
It would help a lot if you could switch the custom patterns field between JSON and "NAME pattern" format while editing the Grok processor.
Describe a specific use case for the feature:
While the Grok processor requires you to enter the custom patterns as a JSON array, the Grok debugger uses the way more common "NAME pattern" format which is also being used by Logstash.
Being able to switch between the two formats would help to work with the debugger and external tools or sources too.
It would also help reduce issues created by manual conversion like handling of special characters (quotes, backslashes, …) for JSON for example.
Describe the feature: It would help a lot if you could switch the custom patterns field between JSON and "NAME pattern" format while editing the Grok processor.
Describe a specific use case for the feature: While the Grok processor requires you to enter the custom patterns as a JSON array, the Grok debugger uses the way more common "NAME pattern" format which is also being used by Logstash.
Being able to switch between the two formats would help to work with the debugger and external tools or sources too.
It would also help reduce issues created by manual conversion like handling of special characters (quotes, backslashes, …) for JSON for example.