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
Copy file name to clipboardExpand all lines: concepts/buffering.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,6 @@ Network failures or latency in third party service is common. When data can't be
12
12
13
13
Fluent Bit buffering strategies are designed to solve problems associated with backpressure and general delivery failures. Fluent Bit offers a primary buffering mechanism in memory and an optional secondary one using the file system. With this hybrid solution you can accommodate any use case safely and keep a high performance while processing your data.
14
14
15
-
These mechanisms aren't mutually exclusive. When data is ready to be processed or delivered it's always be in memory, while other data in the queue might be in the file system until is ready to be processed and moved up to memory.
15
+
These mechanisms aren't mutually exclusive. When data is ready to be processed or delivered it's always be in memory. Other data in the queue might be in the file system until is ready to be processed and moved up to memory.
16
16
17
17
To learn more about the buffering configuration in Fluent Bit, see [Buffering and Storage](../administration/buffering-and-storage.md).
Copy file name to clipboardExpand all lines: concepts/data-pipeline/router.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ pipeline:
78
78
79
79
Routing reads the `Input``Tag` and the `Output``Match` rules. If data has a `Tag` that doesn't match at routing time, the data is deleted.
80
80
81
-
## Routing with Wildcard
81
+
## Routing with wildcards
82
82
83
83
Routing is flexible enough to support wildcards in the `Match` pattern. The following example defines a common destination for both sources of data:
84
84
@@ -122,7 +122,7 @@ pipeline:
122
122
123
123
The match rule is set to `my_*`, which matches any Tag starting with `my_`.
124
124
125
-
## Routing with Regex
125
+
## Routing with regular expressions
126
126
127
127
Routing also provides support for regular expressions with the `Match_Regex` pattern, allowing for more complex and precise matching criteria. The following example demonstrates how to route data from sources based on a regular expression:
0 commit comments