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
- Add note that strftime format values beginning with % (logstash_dateformat,
time_key_format) must be quoted in YAML, since % is a reserved character and
an unquoted value like `logstash_dateformat: %Y.%m.%d` fails to parse
- Fix MD060 table alignment in the write_operation tables
- Fix MD060 header spacing in the OpenSearch parameters table
Fixes#2624
Signed-off-by: Eric D. Schabell <eric@schabell.org>
Copy file name to clipboardExpand all lines: pipeline/outputs/elasticsearch.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,12 @@ The _Elasticsearch_ (`es`) output plugin lets you ingest your records into an [E
52
52
53
53
If you have used a common relational database, the parameters `index` and `type` can be compared to the `database` and `table` concepts.
54
54
55
+
{% hint style="info" %}
56
+
57
+
In YAML configuration, quote any [strftime](https://man7.org/linux/man-pages/man3/strftime.3.html) format value that begins with `%`, such as `logstash_dateformat` and `time_key_format`. YAML treats `%` as a reserved character, so an unquoted value like `logstash_dateformat: %Y.%m.%d` fails to parse. Use `logstash_dateformat: "%Y.%m.%d"` instead.
58
+
59
+
{% endhint %}
60
+
55
61
### TLS / SSL
56
62
57
63
The Elasticsearch output plugin supports TLS/SSL. For more details about the properties available and general configuration, see [TLS/SSL](../../administration/transport-security.md).
@@ -60,12 +66,12 @@ The Elasticsearch output plugin supports TLS/SSL. For more details about the pro
60
66
61
67
The `write_operation` can be any of:
62
68
63
-
| Operation | Description |
64
-
| -----------| ----------- |
65
-
|`create`| Adds new data. If the data already exists (based on its id), the op is skipped.|
66
-
|`index`| New data is added while existing data (based on its id) is replaced (reindexed).|
67
-
|`update`| Updates existing data (based on its id). If no data is found, the op is skipped. |
68
-
|`upsert`| Merge or insert if the data doesn't exist, updates if the data exists (based on its id).|
Copy file name to clipboardExpand all lines: pipeline/outputs/opensearch.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The _OpenSearch_ output plugin lets you ingest your records into an [OpenSearch]
15
15
This plugin supports the following parameters:
16
16
17
17
| Key | Description | Default |
18
-
|:--- |:----------- |:------- |
18
+
|:--- |:----------- |:------- |
19
19
|`aws_auth`| Enable AWS Sigv4 Authentication for Amazon OpenSearch Service. |`Off`|
20
20
|`aws_external_id`| External ID for the AWS IAM Role specified with `aws_role_arn`. |_none_|
21
21
|`aws_profile`| AWS profile name. |`default`|
@@ -55,6 +55,12 @@ This plugin supports the following parameters:
55
55
56
56
The parameters `index` and `type` can be confusing if you are new to OpenSearch. If you have used a common relational database before, they can be compared to the `database` and `table` concepts. Also see [the FAQ](opensearch.md#faq).
57
57
58
+
{% hint style="info" %}
59
+
60
+
In YAML configuration, quote any [strftime](https://man7.org/linux/man-pages/man3/strftime.3.html) format value that begins with `%`, such as `logstash_dateformat` and `time_key_format`. YAML treats `%` as a reserved character, so an unquoted value like `logstash_dateformat: %Y.%m.%d` fails to parse. Use `logstash_dateformat: "%Y.%m.%d"` instead.
61
+
62
+
{% endhint %}
63
+
58
64
### TLS / SSL
59
65
60
66
The OpenSearch output plugin supports TLS/SSL. For more details about the properties available and general configuration, see [TLS/SSL](../../administration/transport-security.md).
@@ -63,11 +69,11 @@ The OpenSearch output plugin supports TLS/SSL. For more details about the proper
0 commit comments