New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement multi-line-timeout #140
Comments
Hi! This is a docs bug, syslog-ng OSE never knew timeout with multi-line messages. It is an issue though, if there is no garbage arrives, syslog-ng would stop processing data from this source. But if you think it through, a missing garbage from the input means either the configuration is bad, or the input stream is bad. Garbage is mandatory to be able to process a whole message. |
I don't agree, garbage is not required. In most cases, there is no garbage at all, for example tomcat log starts with date and that's all. A newer date indicates that a new message started. Not speaking about possible message loss in a normal situation. |
You are right, I wasn't correct. What I wanted to mean is when no garbage or prefix is present for a long time, then it can be a misconfiguration. And what I wanted to demonstrate is that the lack of timeout in the OSE is not a bug, instead it is a missing feature. It can be implemented after the logproto refactor is merged into the OSE. |
just stumbled upon this, and I agree with @pzoleex it is a bug as the last message never makes it. |
It's a missing feature from syslog-ng OSE that has been never implemented. The docs says different though. This An option could be implemented like |
I stumbled again on this issue when trying to send some legacy multi-line logs from files with very low traffic. Many of those have one entry per file, and thus the log never makes it downstream. I'd love to have some idea as to if/when this will be implemented. thanks! |
This needs to be reclassified as a bug. Using Syslog-ng needs to flush the buffer when it:
|
👍 |
I'm bumping this issue, as one of our users complained again ;-) |
It also misses the last message in case of a file rotation with multi-line-mode(indented), I think that a multi-line-timeout parameter, as @ngergo wrote, would be a very nice feature. |
well, it seems that syslog-ng does not detect any files in this mode and/or at least not displaying any incoming message.
To reproduce the issue: create the source file with this content:
then start syslog-ng with the config below.
The result:
Thats all, syslog-ng does not recognize the file.
Expected result: syslog-ng processes the file then creates the proper multi line message when the timeout is reached:
"A message is considered complete if no new lines arrive to the message for 10 seconds, even if no line matching the multi-line-garbage() option is received."
config
The text was updated successfully, but these errors were encountered: