Skip to content

Commit dc3e91b

Browse files
Merge pull request #2030 from fluent/alexakreizinger/sc-143165/vale-final-sweep-for-pipeline-and-pipeline
2 parents fc1f8d4 + c29428f commit dc3e91b

File tree

3 files changed

+10
-7
lines changed

3 files changed

+10
-7
lines changed

pipeline/processors/conditional-processing.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,11 @@ Conditional processing is available in Fluent Bit version 4.0 and greater.
99
You can turn a standard processor into a conditional processor by adding a `condition` block to the processor's YAML configuration settings.
1010

1111
{% hint style="info" %}
12+
1213
- Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/README.md) support processors, including conditional processors.
14+
1315
- Conditional processing isn't supported if you're using a [filter as a processor](../filters).
16+
1417
{% endhint %}
1518

1619
These `condition` blocks use the following syntax:
@@ -22,7 +25,7 @@ These `condition` blocks use the following syntax:
2225
pipeline:
2326
inputs:
2427
<...>
25-
28+
2629
processors:
2730
logs:
2831
- name: processor_name
@@ -273,4 +276,4 @@ pipeline:
273276
{% endtab %}
274277
{% endtabs %}
275278

276-
This configuration adds an `alert` field to error logs from critical services, and adds a `paging_required` field to errors that contain specific critical patterns.
279+
This configuration adds an `alert` field to error logs from critical services, and adds a `paging_required` field to errors that contain specific critical patterns.

pipeline/processors/content-modifier.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ The actions specify the type of operation to run on top of a specific key or con
6565
| Action | Description |
6666
| ------- | ------------------------------------------------------------ |
6767
| `insert` | Inserts a new key with a value into the target context. The `key` and `value` parameters are required. |
68-
| `upsert` | Given a specific key with a value, the `upsert` operation will try to update the value of the key. If the key does not exist, a new key will be created. The `key` and `value` parameters are required. |
68+
| `upsert` | Given a specific key with a value, the `upsert` operation will try to update the value of the key. If the key doesn't exist, a new key will be created. The `key` and `value` parameters are required. |
6969
| `delete` | Deletes a key from the target context. The `key` parameter is required. |
7070
| `rename` | Changes the name of a key. The `value` set in the configuration will represent the new name. The `key` and `value` parameters are required. |
7171
| `hash` | Replaces the key value with a hash generated by the SHA-256 algorithm, the binary value generated is finally set as a hex string representation. The `key` parameter is required. |
@@ -281,4 +281,4 @@ pipeline:
281281
```
282282

283283
{% endtab %}
284-
{% endtabs %}
284+
{% endtabs %}

pipeline/processors/sampling.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ The latency condition uses the following `conditions` configuration parameters:
103103
| `threshold_ms_low` | Specifies the lower latency threshold. Traces with a duration less than or equal to this value will be sampled. | `0` |
104104
| `threshold_ms_high` | Specifies the upper latency threshold. Traces with a duration greater than or equal to this value will be sampled. | `0` |
105105

106-
The following example waits five seconds before making a decision. It then samples traces based on latency, capturing short traces of 200&nbsp;ms or less and long traces of 3000&nbsp;ms or more. Traces between 200&nbsp;ms and 3000&nbsp;ms are not sampled unless another condition applies.
106+
The following example waits five seconds before making a decision. It then samples traces based on latency, capturing short traces of 200&nbsp;ms or less and long traces of 3000&nbsp;ms or more. Traces between 200&nbsp;ms and 3000&nbsp;ms won't be sampled unless another condition applies.
107107

108108
{% tabs %}
109109
{% tab title="fluent-bit.yaml" %}
@@ -151,7 +151,7 @@ The span count condition uses the following `conditions` configuration parameter
151151
| `max_spans` | Specifies the minimum number of spans a trace must have to be sampled. | _none_ |
152152
| `min_spans` | Specifies the maximum number of spans a trace can have to be sampled. | _none_ |
153153

154-
The following example configuration waits five seconds before making a decision. It then samples traces with at least three spans but no more than five spans. Traces with less than three spans or greater than five spans are not sampled unless another condition applies.
154+
The following example configuration waits five seconds before making a decision. It then samples traces with at least three spans but no more than five spans. Traces with less than three spans or greater than five spans won't be sampled unless another condition applies.
155155

156156
{% tabs %}
157157
{% tab title="fluent-bit.yaml" %}
@@ -451,4 +451,4 @@ pipeline:
451451
{% endtab %}
452452
{% endtabs %}
453453

454-
For more details about further processing, read the [content modifier](../processors/content-modifier.md) processor documentation.
454+
For more details about further processing, read the [content modifier](../processors/content-modifier.md) processor documentation.

0 commit comments

Comments
 (0)