Problem
A simple rule: if a line starts with two spaces or is empty it is continuation of a previous rule.
I set continuous_line_regexp to /^( |$)/.
Now most logs disappear, but somehow 3 events every hour don't.
Steps to replicate
log that looks like
[OK] All scheduled tasks are executed!
[OK] Job "'/usr/local/bin/php' '-d display_errors=stderr'
'/var/www/bin/console' '--env=prod' 'cron:run'" executed successfully.
time: 0.099830150604248
[OK] All scheduled tasks are executed!
[OK] Job "'/usr/local/bin/php' '-d display_errors=stderr'
'/var/www/bin/console' '--env=prod' 'cron:run'" executed successfully.
time: 0.0097789764404297
[OK] Job "'/usr/local/bin/php' '-d display_errors=stderr'
'/var/www/bin/console' '--env=prod' 'XXXX:YYYY'"
executed successfully.
only the last event is present (consistently every time it happerns) in the result correctly concatenated all the rest are missing.
Found another event that survives:
[OK] Job "XXXX\YYYY_redacted_long_string" executed
successfully.
I can't figure out the pattern. Maybe the fact that one broken event contains just a singe start line followed by what I hoped would be a continuation line and the other broken event contains an empty line in the middle. But even if pattern doesn't match I would expect the log lines come out of the plugin incorrectly concatenated in stead of disappearing.
Your environment
this plugin is running as part of kubernetes logging operator.
Problem
A simple rule: if a line starts with two spaces or is empty it is continuation of a previous rule.
I set
continuous_line_regexpto/^( |$)/.Now most logs disappear, but somehow 3 events every hour don't.
Steps to replicate
log that looks like
only the last event is present (consistently every time it happerns) in the result correctly concatenated all the rest are missing.
Found another event that survives:
I can't figure out the pattern. Maybe the fact that one broken event contains just a singe start line followed by what I hoped would be a continuation line and the other broken event contains an empty line in the middle. But even if pattern doesn't match I would expect the log lines come out of the plugin incorrectly concatenated in stead of disappearing.
Your environment
this plugin is running as part of kubernetes logging operator.