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
# This plugin is the recommended method of storing logs in Elasticsearch.
33
-
# If you plan on using the Kibana web interface, you'll want to use this output.
34
-
#
35
-
# This output only speaks the HTTP protocol. HTTP is the preferred protocol for interacting with Elasticsearch as of Logstash 2.0.
25
+
# This output only speaks the HTTP protocol. HTTP is the preferred protocol for interacting with OpenSearch.
36
26
# We strongly encourage the use of HTTP over the node protocol for a number of reasons. HTTP is only marginally slower,
37
-
# yet far easier to administer and work with. When using the HTTP protocol one may upgrade Elasticsearch versions without having
27
+
# yet far easier to administer and work with. When using the HTTP protocol one may upgrade OpenSearch versions without having
38
28
# to upgrade Logstash in lock-step.
39
29
#
40
-
# You can learn more about Elasticsearch at <https://www.elastic.co/products/elasticsearch>
41
-
#
42
-
# ==== Template management for Elasticsearch 5.x
43
-
# Index template for this version (Logstash 5.0) has been changed to reflect Elasticsearch's mapping changes in version 5.0.
44
-
# Most importantly, the subfield for string multi-fields has changed from `.raw` to `.keyword` to match ES default
45
-
# behavior.
46
-
#
47
-
# ** Users installing ES 5.x and LS 5.x **
48
-
# This change will not affect you and you will continue to use the ES defaults.
49
-
#
50
-
# ** Users upgrading from LS 2.x to LS 5.x with ES 5.x **
51
-
# LS will not force upgrade the template, if `logstash` template already exists. This means you will still use
52
-
# `.raw` for sub-fields coming from 2.x. If you choose to use the new template, you will have to reindex your data after
53
-
# the new template is installed.
30
+
# You can learn more about OpenSearch at <https://opensearch.org/>
54
31
#
55
32
# ==== Retry Policy
56
-
#
57
-
# The retry policy has changed significantly in the 2.2.0 release.
58
-
# This plugin uses the Elasticsearch bulk API to optimize its imports into Elasticsearch. These requests may experience
33
+
# This plugin uses the OpenSearch bulk API to optimize its imports into OpenSearch. These requests may experience
59
34
# either partial or total failures.
60
35
#
61
36
# The following errors are retried infinitely:
@@ -65,7 +40,7 @@
65
40
# - 503 (Service unavailable) errors
66
41
#
67
42
# NOTE: 409 exceptions are no longer retried. Please set a higher `retry_on_conflict` value if you experience 409 exceptions.
68
-
# It is more performant for Elasticsearch to retry these exceptions than this plugin.
43
+
# It is more performant for OpenSearch to retry these exceptions than this plugin.
69
44
#
70
45
# ==== Batch Sizes ====
71
46
# This plugin attempts to send batches of events as a single request. However, if
@@ -84,12 +59,10 @@
84
59
#
85
60
# ==== HTTP Compression
86
61
#
87
-
# This plugin supports request and response compression. Response compression is enabled by default and
88
-
# for Elasticsearch versions 5.0 and later, the user doesn't have to set any configs in Elasticsearch for
89
-
# it to send back compressed response. For versions before 5.0, `http.compression` must be set to `true` in
90
-
# Elasticsearch[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html#modules-http] to take advantage of response compression when using this plugin
62
+
# This plugin supports request and response compression. Response compression is enabled by default,
63
+
# the user doesn't have to set any configs in OpenSearch for it to send back compressed response.
91
64
#
92
-
# For requests compression, regardless of the Elasticsearch version, users have to enable `http_compression`
65
+
# For requests compression, users have to enable `http_compression`
@@ -118,12 +91,11 @@ class LogStash::Outputs::OpenSearch < LogStash::Outputs::Base
118
91
# - delete: deletes a document by id (An id is required for this action)
119
92
# - create: indexes a document, fails if a document by that id already exists in the index.
120
93
# - update: updates a document by id. Update has a special case where you can upsert -- update a
121
-
# document if not already present. See the `upsert` option. NOTE: This does not work and is not supported
122
-
# in Elasticsearch 1.x. Please upgrade to ES 2.x or greater to use this feature with Logstash!
94
+
# document if not already present. See the `upsert` option.
123
95
# - A sprintf style string to change the action based on the content of the event. The value `%{[foo]}`
124
96
# would use the foo field for the action
125
97
#
126
-
# For more details on actions, check out the http://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html[Elasticsearch bulk API documentation]
98
+
# For more details on actions, check out the https://docs-beta.opensearch.org/opensearch/rest-api/bulk/[OpenSearch bulk API documentation]
Copy file name to clipboardExpand all lines: lib/logstash/plugin_mixins/opensearch/api_configs.rb
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -136,13 +136,13 @@ module APIConfigs
136
136
:custom_headers=>{:validate=>:hash,:default=>{}},
137
137
138
138
# Sets the host(s) of the remote instance. If given an array it will load balance requests across the hosts specified in the `hosts` parameter.
139
-
# Remember the `http` protocol uses the http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-http.html#modules-http[http] address (eg. 9200, not 9300).
139
+
# Remember the `http` protocol uses the http address (eg. 9200, not 9300).
140
140
# `"127.0.0.1"`
141
141
# `["127.0.0.1:9200","127.0.0.2:9200"]`
142
142
# `["http://127.0.0.1"]`
143
143
# `["https://127.0.0.1:9200"]`
144
144
# `["https://127.0.0.1:9200/mypath"]` (If using a proxy on a subpath)
145
-
# It is important to exclude http://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html[dedicated master nodes] from the `hosts` list
145
+
# It is important to exclude dedicated master nodes from the `hosts` list
146
146
# to prevent LS from sending bulk requests to the master nodes. So this parameter should only reference either data or client nodes in OpenSearch.
147
147
#
148
148
# Any special characters present in the URLs here MUST be URL escaped! This means `#` should be put in as `%23` for instance.
0 commit comments