- Add
x-elastic-product-origin
header to Elasticsearch requests #185
- Version bump to pick up doc fix in #172
- Added request header
Elastic-Api-Version
for serverless #174
- Fixes a memory leak that occurs when a pipeline containing this filter terminates, which could become significant if the pipeline is cycled repeatedly #173
- Added checking for
query
andquery_template
. #171
- Fixes a regression introduced in 3.15.0 which could prevent a connection from being established to Elasticsearch in some SSL configurations
- Added SSL settings for: #168
ssl_enabled
: Enable/disable the SSL settings. If not provided, the value is inferred from the hosts schemessl_certificate
: OpenSSL-style X.509 certificate file to authenticate the clientssl_key
: OpenSSL-style RSA private key that corresponds to thessl_certificate
ssl_truststore_path
: The JKS truststore to validate the server's certificatessl_truststore_type
: The format of the truststore filessl_truststore_password
: The truststore passwordssl_keystore_path
: The keystore used to present a certificate to the serverssl_keystore_type
: The format of the keystore filessl_keystore_password
: The keystore passwordssl_cipher_suites
: The list of cipher suites to usessl_supported_protocols
: Supported protocols with versionsssl_verification_mode
: Defines how to verify the certificates presented by another party in the TLS connection
- Reviewed and deprecated SSL settings to comply with Logstash's naming convention
- Deprecated
ssl
in favor ofssl_enabled
- Deprecated
ca_file
in favor ofssl_certificate_authorities
- Deprecated
keystore
in favor ofssl_keystore_path
- Deprecated
keystore_password
in favor ofssl_keystore_password
- Deprecated
- Added support for configurable retries with new
retry_on_failure
andretry_on_status
options #160
- Added support for this plugin identifying itself to Elasticsearch with an SSL/TLS client certificate using a new
keystore
option #162
- Added support for
ca_trusted_fingerprint
when run on Logstash 8.3+ #158
- Fix: hosts => "es_host:port" regression #156
- Feat: update Elasticsearch client to 7.14.0 #150
- Feat: add user-agent header passed to the Elasticsearch HTTP connection #152
- Fixed SSL handshake hang indefinitely with proxy setup #151
- Fix: a regression (in LS 7.14.0) where due the elasticsearch client update (from 5.0.5 to 7.5.0) the
Authorization
header isn't passed, this leads to the plugin not being able to leverageuser
/password
credentials set by the user. #148 - Fix: default setting for
hosts
not working (since 3.7.0) GH-147 - Fix: mutating @hosts variable which leads to issues with multiple worker threads GH-129
- [DOC] Update links to use shared attributes #144
- [DOC] Fixed links to restructured Logstash-to-cloud docs #142
- [DOC] Document the permissions required in secured clusters #140
- Add support to define a proxy with the proxy config option #134
- Added api_key support #132
- [DOC] Removed outdated compatibility notice #131
- Fix: solves an issue where non-ascii unicode values in a template were not handled correctly #128
- Feat: support cloud_id / cloud_auth configuration #122
- Loosen restrictions on Elasticsearch gem (#120)
- Add support for extracting hits total from Elasticsearch 7.x responses
- Added connection check during register to avoid failures during processing
- Changed Elasticsearch Client transport to use Manticore
- Changed amount of logging details during connection failure
- Adds
[@metadata][total_hits]
with total hits returned from the query (#106) - Improves error logging to fully inspect caught exceptions (#105)
- Fix: The filter now only calls
filter_matched
on events that actually matched. This fixes issues where all events would have success-related actions happened when no match had actually happened (add_tag
,add_field
,remove_tag
,remove_field
)
- Enhancement : if elasticsearch response contains any shard failure, then
tag_on_failure
tags are added to Logstash event - Enhancement : add support for nested fields
- Enhancement : add 'docinfo_fields' option
- Enhancement : add 'aggregation_fields' option
- Update gemspec summary
index
setting now supports field formatting, such asindex => "%{myindex}"
(Boris Gorbylev)
- Fix a thread safety issue when using this filter with multiple workers on heavy load, we now create an elasticsearch client for every LogStash worker. #76
- Fix some documentation issues
- Docs: Fix broken link to Logstash docs.
- Support ca_file setting when using https uri in hosts parameter
- Docs: Bump patch level for doc build.
- Change the queries loglevel from info to debug.
- Docs: Add requirement to use version 3.1.1 or higher to support sending Content-Type headers.
- Upgrade es-ruby client to support correct content-type
- Support for full use of query DSL. Added query_template to use full DSL.
- Fix couple of bugs related to incorrect variable names
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Fix: wrong usage of search params, now if index is properly specified it's passed to search so it's performed not to all indices if this is not the explicit intention.
- Breaking: Updated plugin to use new Java Event APIs
- Improved the configuration options to be more easy to understand and match what the expectations are from the documentation.
- Initial refactoring to include later one a common client for all the ES plugins.
- Adding support for having an index in the query pattern.
- Improved documentation.
- Added intitial integration and unit tests.
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0
- removed require statement for a file that is no longer present in logstash-core.