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
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.
The text was updated successfully, but these errors were encountered:
I now see that users keep reporting similar problems, like #109, #94 and various other related to time outs and disappearing log records. Also a PR #121 seems related as our events that get swallowed have the same timestamp as the 1 that remains. I conclude that this plugin isn't ready to be used in production.
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
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.
The text was updated successfully, but these errors were encountered: