You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem including expected versus actual behavior:
Logstash allows special characters in field names to create the hidden EMAIL REDACTED fields in logstash. These are used to store data which is not sent to the outputs by default.
When debugging grok expressions containing this syntax, the debugger either throws an error or fails silently. (error in Chrome on Mac, silent fail on Deb9 with Chromium). While not critical for the overall functionality, it is annoying that these field names have to be substituted before and after debugging.
Steps to reproduce:
enter any data to match
attempt to match nested special field: EMAIL REDACTED
Errors in browser console (if relevant):
GrokDebugger: Provided Grok patterns do not match data in the input
The text was updated successfully, but these errors were encountered:
Original comment by @LucaWintergerst:
Kibana version: 6.0.0
Elasticsearch version: 6.0.0
Description of the problem including expected versus actual behavior:
Logstash allows special characters in field names to create the hidden EMAIL REDACTED fields in logstash. These are used to store data which is not sent to the outputs by default.
When debugging grok expressions containing this syntax, the debugger either throws an error or fails silently. (error in Chrome on Mac, silent fail on Deb9 with Chromium). While not critical for the overall functionality, it is annoying that these field names have to be substituted before and after debugging.
Steps to reproduce:
Errors in browser console (if relevant):
GrokDebugger: Provided Grok patterns do not match data in the input
The text was updated successfully, but these errors were encountered: