I really love using Graylog (https://www.graylog.org/) for my hobby project, but writing complex pipeline rules for log parsing is somethings a pain
My pain points so far:
* support for parsing JSON is basic
* language for rule writing is limited
My highlight while creating this rule:
* you cannot parse and select arbitrary JSON sub paths - I had to manually cut the string
* you cannot do arithmetic expressions, so I had to add two substring calls instead of one