logstash-input-elastic_serverless_forwarder 0.1.3-java → 0.1.4-java

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '08bce725c7626a1e3cc794ab1679b2ca61de4f10fb58a4c6efb895af4a4c2a5f'
-  data.tar.gz: b997c8f5c4a7011f219ea2cf338d6813c2cd58350918e9f2fe1d58ece1c43e11
+  metadata.gz: de05ac4680e3274f57b3a934e616127d9efe8702f16c63bdf2e9f5afd08bdab4
+  data.tar.gz: 13e09a76c888dcb3db065cb50e678738a5561c339eecfc79318119c321e7437a
 SHA512:
-  metadata.gz: 9f69616a38002781b3f896f67c09cf780f708419bceef0789ef3e7f93f88bafafdea34539468bbb4de793c1231434282912b15dc6dad69da0aabdd63d29d0fd8
-  data.tar.gz: 3b306b08747a7f86611f785ba3b3d477707172b15eb096e2a7854a2bbc6937e2c376a65eb23c8f3e7758a3b6aae81bbb79dc31d73986246ce9264ced232aa698
+  metadata.gz: 1580d128d385d1523dce54fc23dcd8161536ddb2339eaac43f187cf44cc318e3e17e8ab1a3d2532221798c1b13da324cd7d8121487a9b36f7fb4b7d9fb84a507
+  data.tar.gz: 88bb2ebf1aed3c24ad21e4af63320bc7809e85686bbe1b34cfdeb3c6f076c6798284e3eda83d6e87d2b6e2c47ec783023605c099d1be0fba9552e22abf211398

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+## 0.1.4
+  - [DOC] Adds tips for using the logstash-input-elastic_serverless_forwarder plugin with the Elasticsearch output plugin [#7](https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/pull/7)
+
 ## 0.1.3
   - Deprecates the `ssl` option in favor of `ssl_enabled` [#6](https://github.com/logstash-plugins/logstash-input-elastic_serverless_forwarder/pull/6)
   - Bumps `logstash-input-http` gem version to `>= 3.7.2` (SSL-normalized)

data/docs/index.asciidoc

@@ -132,6 +132,36 @@ You can configure this plugin to authenticate requests using HTTP Basic authenti
 NOTE: Basic Authentication is not a substitute for SSL, as it provides neither secrecy nor security on its own.
       When used with SSL disabled, HTTP Basic credentials are transmitted in effectively clear-text and can be easily recovered by an adversary.
 
+[id="plugins-{type}s-{plugin}-es-output-notes"]
+==== Using {esf-name} with the Elasticsearch output
+Here are some tips for configuring the {esf} input to work with the elasticsearch output:
+
+* Set the `document_id` in the output configuration when you use the {esf}  input with an {logstash-ref}/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch[Elasticsearch output plugin].
++
+[source,ruby]
+----
+output {
+  elasticsearch {
+      ...
+      document_id => "%{[@metadata][_id]}"
+      ...
+  }
+}
+----
+* Starting from version 1.10.0 of {esf-name}, configuring `document_id` as shown in the example above is sufficient (the `_id` field is no longer available, and instead, Logstash now receives the `@metadata._id` field).
+
+* For {esf-name} v1.9.0 and earlier, rename the field `_id` to `@metadata._id` with a filter:
++
+[source,ruby]
+----
+filter {
+    # support ESF < 1.10
+    if [_id] and ![@metadata][_id] {
+      mutate { rename => { "_id" => "[@metadata][_id]" } }
+    }
+}
+----
+
 [id="plugins-{type}s-{plugin}-options"]
 ==== {esf-name} Input Configuration Options
 

data/logstash-input-elastic_serverless_forwarder.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name = 'logstash-input-elastic_serverless_forwarder'
-  s.version = '0.1.3'
+  s.version = '0.1.4'
   s.licenses = ['Apache License (2.0)']
   s.summary = "Receives events from Elastic Serverless Forwarder over HTTP or HTTPS"
   s.description     = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: logstash-input-elastic_serverless_forwarder
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: java
 authors:
 - Elastic
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-09-14 00:00:00.000000000 Z
+date: 2023-11-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement