It's a pretty simple tweak to the regex(es) for syslog / syslog2. So far as I can tell in testing this doesn't break any existing parsing/processing, though obviously with another optional (uncaptured) group there's always the potential for an impact on parsing performance, even though I haven't seen any perceptible change in performance with the change when parsing log files I've modified specifically to match the currently expected syslog format.
It's a pretty simple tweak to the regex(es) for syslog / syslog2. So far as I can tell in testing this doesn't break any existing parsing/processing, though obviously with another optional (uncaptured) group there's always the potential for an impact on parsing performance, even though I haven't seen any perceptible change in performance with the change when parsing log files I've modified specifically to match the currently expected syslog format.
Intended to address issue #681.