Skip to content

Commit bb3e386

Browse files
authored
Merge pull request #20732 from pneedle-rh/fix_typo
Fixing typos.
2 parents a9cce55 + 7084c2c commit bb3e386

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/cluster-logging-collector-json.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ oc set env ds/rsyslog MERGE_JSON_LOG=true <1>
4242

4343
*Setting MERGE_JSON_LOG and CDM_UNDEFINED_TO_STRING*
4444

45-
If you set the `MERGE_JSON_LOG` and `CDM_UNDEFINED_TO_STRING` enviroment variables to `true`, you might receive an Elasticsearch *400* error. The error occurs because when `MERGE_JSON_LOG=true`, Fluentd adds fields with data types other than *string*. When you set `CDM_UNDEFINED_TO_STRING=true`, Fluentd attempts to add those fields as a *string* value resulting in the Elasticsearch *400* error. The error clears when the indices roll over for the next day.
45+
If you set the `MERGE_JSON_LOG` and `CDM_UNDEFINED_TO_STRING` environment variables to `true`, you might receive an Elasticsearch *400* error. The error occurs because when `MERGE_JSON_LOG=true`, Fluentd adds fields with data types other than *string*. When you set `CDM_UNDEFINED_TO_STRING=true`, Fluentd attempts to add those fields as a *string* value resulting in the Elasticsearch *400* error. The error clears when the indices roll over for the next day.
4646

4747
When Fluentd rolls over the indices for the next day's logs, it will create a brand new index. The field definitions are updated and you will not get the *400* error.
4848

0 commit comments

Comments
 (0)