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
Fixes for new documentation of Blob input plugin configuration options and updated code examples. (#2201)
* Updated to include new input plugin doc for Windows System Statistics. Applies to #2139.
Signed-off-by: Eric D. Schabell <eric@schabell.org>
* Updated to include new input plugin doc for Windows System Statistics. Applies to #2139.
Signed-off-by: Eric D. Schabell <eric@schabell.org>
* Lint fix for winstat input plugin doc fix.
Signed-off-by: Eric D. Schabell <eric@schabell.org>
* Fixes for new documentation of Blob input plugin configuration options and updated code examples.
Signed-off-by: Eric D. Schabell <eric@schabell.org>
---------
Signed-off-by: Eric D. Schabell <eric@schabell.org>
Copy file name to clipboardExpand all lines: pipeline/inputs/blob.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,12 +23,12 @@ The plugin supports the following configuration parameters:
23
23
|`threaded`| Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). When enabled, the plugin runs in a separate thread, which can improve performance for I/O-bound operations. |`false`|
24
24
|`threaded.ring_buffer.capacity`| Set custom ring buffer capacity when the input runs in threaded mode. This determines how many records can be buffered in the ring buffer before blocking. |`1024`|
25
25
|`threaded.ring_buffer.window`| Set custom ring buffer window percentage for threaded inputs. This controls when the ring buffer is considered "full" and triggers backpressure handling. |`5`|
26
-
|`upload_success_action`| Action to perform on the file after successful processing. Supported values: `delete` (delete the file), `move` (move the file), `none` (no action). When set to `move`, use `upload_success_suffix` to specify the destination. |_none_|
27
-
|`upload_success_suffix`| Suffix to append to the filename when moving a file after successful processing. Only used when `upload_success_action` is set to `move`. For example, if set to `.processed`, a file named `data.bin` will be moved to `data.bin.processed`. |_none_|
28
-
|`upload_success_message`|Custom message to include in the log when a file is successfully processed. This can be used for debugging or monitoring purposes. |_none_|
29
-
|`upload_failure_action`| Action to perform on the file after processing failure. Supported values: `delete` (delete the file), `move` (move the file), `none` (no action). When set to `move`, use `upload_failure_suffix` to specify the destination. |_none_|
30
-
|`upload_failure_suffix`| Suffix to append to the filename when moving a file after processing failure. Only used when `upload_failure_action` is set to `move`. For example, if set to `.failed`, a file named `data.bin` will be moved to `data.bin.failed` if processing fails. |_none_|
31
-
|`upload_failure_message`|Custom message to include in the log when file processing fails. This can be used for debugging or monitoring purposes. |_none_|
26
+
|`upload_success_action`| Action to perform on the file after successful upload. Supported values: `delete` (delete the file), `add_suffix` (rename file by appending a suffix), `emit_log` (emit a log record with a custom message). When set to `add_suffix`, use `upload_success_suffix` to specify the suffix. When set to `emit_log`, use `upload_success_message` to specify the message. |_none_|
27
+
|`upload_success_suffix`| Suffix to append to the filename after successful upload. Only used when `upload_success_action` is set to `add_suffix`. For example, if set to `.processed`, a file named `data.bin` will be renamed to `data.bin.processed`. |_none_|
28
+
|`upload_success_message`|Message to emit as a log record after successful upload. Only used when `upload_success_action`is set to `emit_log`. This can be used for debugging or monitoring purposes. |_none_|
29
+
|`upload_failure_action`| Action to perform on the file after upload failure. Supported values: `delete` (delete the file), `add_suffix` (rename file by appending a suffix), `emit_log` (emit a log record with a custom message). When set to `add_suffix`, use `upload_failure_suffix` to specify the suffix. When set to `emit_log`, use `upload_failure_message` to specify the message. |_none_|
30
+
|`upload_failure_suffix`| Suffix to append to the filename after upload failure. Only used when `upload_failure_action` is set to `add_suffix`. For example, if set to `.failed`, a file named `data.bin` will be renamed to `data.bin.failed`. |_none_|
31
+
|`upload_failure_message`|Message to emit as a log record after upload failure. Only used when `upload_failure_action` is set to `emit_log`. This can be used for debugging or monitoring purposes. |_none_|
32
32
33
33
## How it works
34
34
@@ -206,9 +206,9 @@ pipeline:
206
206
{% endtab %}
207
207
{% endtabs %}
208
208
209
-
### Configuration with file actions after processing
209
+
### Configuration with file actions after upload
210
210
211
-
This example moves files after successful processing and handles failures:
211
+
This example renames files after successful upload and handles failures:
0 commit comments