@@ -112,7 +112,7 @@ fluent-bit -i cpu -t cpu -o es -p Host=192.168.2.3 -p Port=9200 \
112
112
113
113
In your main configuration file append the following ` Input ` and ` Output ` sections.
114
114
115
- % tabs %}
115
+ { % tabs %}
116
116
{% tab title="fluent-bit.yaml" %}
117
117
118
118
``` yaml
@@ -234,7 +234,7 @@ to the
234
234
235
235
Example configuration:
236
236
237
- % tabs %}
237
+ { % tabs %}
238
238
{% tab title="fluent-bit.yaml" %}
239
239
240
240
``` yaml
@@ -296,7 +296,7 @@ Rejecting mapping update to [products] as the final mapping would have more than
296
296
297
297
This means that you can't set up your configuration like the following:.
298
298
299
- % tabs %}
299
+ { % tabs %}
300
300
{% tab title="fluent-bit.yaml" %}
301
301
302
302
``` yaml
@@ -352,7 +352,7 @@ This doesn't work in Elasticsearch versions 5.6 through 6.1
352
352
Ensure you set an explicit map such as ` doc ` or ` flb_type ` in the configuration,
353
353
as seen on the last line:
354
354
355
- % tabs %}
355
+ { % tabs %}
356
356
{% tab title="fluent-bit.yaml" %}
357
357
358
358
``` yaml
@@ -406,7 +406,7 @@ If you see `action_request_validation_exception` errors on your pipeline with
406
406
Fluent Bit versions greater than v1.8.2, correct them by turning on ` Generate_ID `
407
407
as follows:
408
408
409
- % tabs %}
409
+ { % tabs %}
410
410
{% tab title="fluent-bit.yaml" %}
411
411
412
412
``` yaml
@@ -441,7 +441,7 @@ pipeline:
441
441
The following snippet demonstrates using the namespace name as extracted by the
442
442
` kubernetes ` filter as ` logstash ` prefix:
443
443
444
- % tabs %}
444
+ { % tabs %}
445
445
{% tab title="fluent-bit.yaml" %}
446
446
447
447
``` yaml
0 commit comments