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: pipeline/filters/modify.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ The plugin supports the following rules:
50
50
|`Move_to_start`|`WILDCARD:KEY`|_none_| Move key/value pairs with keys matching `KEY` to the start of the message. |
51
51
|`Move_to_end`|`WILDCARD:KEY`|_none_| Move key/value pairs with keys matching `KEY` to the end of the message. |
52
52
53
-
- Rules are case insensitive, parameters aren't.
53
+
- Rules are case insensitive, but parameters aren't.
54
54
- Any number of rules can be set in a filter instance.
55
55
- Rules are applied in the order they appear, with each rule operating on the result of the previous rule.
56
56
@@ -71,15 +71,17 @@ The plugin supports the following conditions:
71
71
|`Matching_keys_have_matching_values`|`REGEXP:KEY`|`REGEXP:VALUE`| Is `true` if all keys matching `KEY` have values that match `VALUE`. |
72
72
|`Matching_keys_do_not_have_matching_values`|`REGEXP:KEY`|`REGEXP:VALUE`| Is `true` if all keys matching `KEY` have values that don't match `VALUE`. |
73
73
74
-
- Conditions are case insensitive, parameters aren't.
74
+
- Conditions are case insensitive, but parameters aren't.
75
75
- Any number of conditions can be set.
76
76
- Conditions apply to the whole filter instance and all its rules. _Not_ to individual rules.
77
-
- All conditions have to be `true` for the rules to be applied.
77
+
- All conditions must be `true` for the rules to be applied.
78
78
- You can set [Record Accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor.md) as `STRING:KEY` for nested key.
79
79
80
80
## Example 1 - add and rename
81
81
82
-
To start filtering records, you can run the filter from the command line or through the configuration file. The following invokes the [Memory Usage Input Plugin](../inputs/memory-metrics.md), which outputs data similar to the following:
82
+
To start filtering records, you can run the filter from the command line or through
83
+
the configuration file. The following invokes the [Memory Usage Input Plugin](../inputs/memory-metrics.md),
0 commit comments