From 06f7bd2c9504bdca4d04517b380cfb1dac558e4a Mon Sep 17 00:00:00 2001 From: lecaros Date: Thu, 17 Mar 2022 17:32:47 -0300 Subject: [PATCH] pipeline: inputs: tail: add yaml samples Signed-off-by: lecaros --- pipeline/inputs/tail.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/pipeline/inputs/tail.md b/pipeline/inputs/tail.md index ae9bc6763..f2a65f1cb 100644 --- a/pipeline/inputs/tail.md +++ b/pipeline/inputs/tail.md @@ -65,12 +65,26 @@ As stated in the [Multiline Parser documentation](../../administration/configuri If you are running Fluent Bit to process logs coming from containers like Docker or CRI, you can use the new built-in modes for such purposes. This will help to reassembly multiline messages originally split by Docker or CRI: +{% tabs %} +{% tab title="fluent-bit.conf" %} ```text [INPUT] name tail path /var/log/containers/*.log multiline.parser docker, cri ``` +{% endtab %} + +{% tab title="fluent-bit.yaml" %} +```yaml +pipeline: + inputs: + - tail: + path: /var/log/containers/*.log + multiline.parser: docker, cri +``` +{% endtab %} +{% endtabs %} The two options separated by a comma means multi-format: try `docker` and `cri` multiline formats. @@ -113,6 +127,8 @@ $ fluent-bit -i tail -p path=/var/log/syslog -o stdout In your main configuration file append the following _Input_ & _Output_ sections. An example visualization can be found [here](https://link.calyptia.com/vg2) +{% tabs %} +{% tab title="fluent-bit.conf" %} ```python [INPUT] Name tail @@ -122,6 +138,21 @@ In your main configuration file append the following _Input_ & _Output_ sections Name stdout Match * ``` +{% endtab %} + +{% tab title="fluent-bit.yaml" %} +```yaml +pipeline: + inputs: + - tail: + path: /var/log/syslog + + outputs: + - stdout: + match: * +``` +{% endtab %} +{% endtabs %} ![](../../.gitbook/assets/image%20%286%29.png)