Graylog2 / Graylog2/graylog2-server
Simplify regex notation handling
Open
feature
triaged
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
Currently Graylog Pipelines (and maybe some other parts) require complicated manual escaping in regexes.
Even my pattern works perfectly after 10 minutes debug with https://regex101.com/ then I have to spend 20 minutes more trying to guess what exactly Graylog doesn't like in Pipeline configuration window in something like regex_replace.
Suggestion:
make regex engine frontend more user-friendly, in perfect case it must accept already verified patterns as is, without messing with manual escaping
Contributor guide
Assessment
This issue has not been assessed yet.