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
*Description:* Specifies the time {{ site.product.short_name }} waits without reading new data from the source, before
7
-
the last (potentially partial) message is flushed and sent through the pipeline as a LogMessage.
6
+
*Description:* Specifies the time (in seconds) {{ site.product.short_name }} waits without reading new data from the source, before the last (potentially partial) message is flushed and sent through the pipeline as a LogMessage.
8
7
9
-
Since the multi-line source detects the end of a message after finding the beginning of the subsequent message
10
-
(indented or no-garbage/suffix mode), this option can be used to flush the last multi-line message
11
-
in the file after a multi-line-timeout()-second timeout.
8
+
Since the multi-line source detects the end of a message via finding the beginning of the subsequent message (indented or no-garbage/suffix mode), this option can be used to flush the last multi-line message in the file after a given time.
12
9
13
-
There is no default value, so it must be explicitly configured. It should be a higher value than follow-freq(), so we recommend to set it to a multiple value of follow-freq().
10
+
There is no default value, so it must be explicitly configured with a value higher than follow-freq(). We recommend it to be set to a multiple of follow-freq().
14
11
15
12
### Example: multi-line-timeout()
16
13
@@ -25,4 +22,4 @@ source s_multi {
25
22
}
26
23
```
27
24
28
-
For more details see the blogpost Multi-line-timeout: making sure your last multi-line message is not lost.
25
+
For more details see the blog post Multi-line-timeout: making sure your last multi-line message is not lost.
0 commit comments