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
Updated exec input plugin doc config parameter table and general standardization. Fixes#2249. (#2250)
* Updated exec input pluing doc config parameter table and general standardization. Fixes#2249.
Signed-off-by: Eric D. Schabell <[email protected]>
* Grammer change per reviewer request.
Signed-off-by: Eric D. Schabell <[email protected]>
* Grammer change per reviewer request.
Signed-off-by: Eric D. Schabell <[email protected]>
---------
Signed-off-by: Eric D. Schabell <[email protected]>
|`Command`| The command to execute, passed to [popen](https://man7.org/linux/man-pages/man3/popen.3.html) without any additional escaping or processing. Can include pipelines, redirection, command-substitution, or other information.|
24
-
|`Parser`| Specify the name of a parser to interpret the entry as a structured message. |
|`Buf_Size`| Size of the buffer. See [unit sizes](../../administration/configuring-fluent-bit.md#unit-sizes) for allowed values.|
28
-
|`Oneshot`| Only run once at startup. This allows collection of data precedent to Fluent Bit startup (Boolean, default: `false`).|
29
-
|`Exit_After_Oneshot`| Exit as soon as the one-shot command exits. This allows the `exec` plugin to be used as a wrapper for another command, sending the target command's output to any Fluent Bit sink, then exits. (Boolean, default: `false`).|
30
-
|`Propagate_Exit_Code`|When exiting due to `Exit_After_Oneshot`, cause Fluent Bit to exit with the exit code of the command exited by this plugin. Follows [shell conventions for exit code propagation](https://www.gnu.org/software/bash/manual/html_node/Exit-Status.html). (Boolean, default: `false`).|
31
-
|`Threaded`| Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). Default: `false`.|
|`buf_size`| Size of the buffer. See [unit sizes](../../administration/configuring-fluent-bit.md#unit-sizes) for allowed values. |`4096`|
24
+
|`command`| The command to execute, passed to [popen](https://man7.org/linux/man-pages/man3/popen.3.html) without any additional escaping or processing. Can include pipelines, redirection, command-substitution, or other information.|_none_|
25
+
|`exit_after_oneshot`| Exit as soon as the one-shot command exits. This allows the `exec` plugin to be used as a wrapper for another command, sending the target command's output to any Fluent Bit sink, then exits. When enabled, `oneshot` is automatically set to `true`.|`false`|
|`oneshot`| Only run once at startup. This allows collection of data before to Fluent Bit startup. |`false`|
29
+
|`parser`| Specify the name of a parser to interpret the entry as a structured message. |_none_|
30
+
|`propagate_exit_code`|Cause Fluent Bit to exit with the exit code of the command exited by this plugin. Follows [shell conventions for exit code propagation](https://www.gnu.org/software/bash/manual/html_node/Exit-Status.html). Requires `exit_after_oneshot=true`. |`false`|
31
+
|`threaded`| Indicates whether to run this input in its own [thread](../../administration/multithreading.md#inputs). |`false`|
32
32
33
33
## Get started
34
34
@@ -102,7 +102,7 @@ pipeline:
102
102
103
103
## Use as a command wrapper
104
104
105
-
To use Fluent Bit with the `exec` plugin to wrap another command, use the `Exit_After_Oneshot` and `Propagate_Exit_Code` options:
105
+
To use Fluent Bit with the `exec` plugin to wrap another command, use the `exit_after_oneshot` and `propagate_exit_code` options:
106
106
107
107
{% tabs %}
108
108
{% tab title="fluent-bit.yaml" %}
@@ -165,7 +165,7 @@ Translation of command exit codes to Fluent Bit exit code follows [the usual she
165
165
166
166
### Parsing command output
167
167
168
-
By default, the `exec` plugin emits one message per command output line, with a single field `exec` containing the full message. Use the `Parser` directive to specify the name of a parser configuration to use to process the command input.
168
+
By default, the `exec` plugin emits one message per command output line, with a single field `exec` containing the full message. Use the `parser` option to specify the name of a parser configuration to use to process the command input.
0 commit comments