@@ -112,7 +112,7 @@ fluent-bit -i cpu -t cpu -o es -p Host=192.168.2.3 -p Port=9200 \
112112
113113In your main configuration file append the following ` Input ` and ` Output ` sections.
114114
115- % tabs %}
115+ { % tabs %}
116116{% tab title="fluent-bit.yaml" %}
117117
118118``` yaml
@@ -234,7 +234,7 @@ to the
234234
235235Example configuration:
236236
237- % tabs %}
237+ { % tabs %}
238238{% tab title="fluent-bit.yaml" %}
239239
240240``` yaml
@@ -296,7 +296,7 @@ Rejecting mapping update to [products] as the final mapping would have more than
296296
297297This means that you can't set up your configuration like the following:.
298298
299- % tabs %}
299+ { % tabs %}
300300{% tab title="fluent-bit.yaml" %}
301301
302302``` yaml
@@ -352,7 +352,7 @@ This doesn't work in Elasticsearch versions 5.6 through 6.1
352352Ensure you set an explicit map such as ` doc ` or ` flb_type ` in the configuration,
353353as seen on the last line:
354354
355- % tabs %}
355+ { % tabs %}
356356{% tab title="fluent-bit.yaml" %}
357357
358358``` yaml
@@ -406,7 +406,7 @@ If you see `action_request_validation_exception` errors on your pipeline with
406406Fluent Bit versions greater than v1.8.2, correct them by turning on ` Generate_ID `
407407as follows:
408408
409- % tabs %}
409+ { % tabs %}
410410{% tab title="fluent-bit.yaml" %}
411411
412412``` yaml
@@ -441,7 +441,7 @@ pipeline:
441441The following snippet demonstrates using the namespace name as extracted by the
442442` kubernetes ` filter as ` logstash ` prefix:
443443
444- % tabs %}
444+ { % tabs %}
445445{% tab title="fluent-bit.yaml" %}
446446
447447``` yaml
0 commit comments