- SSL settings that were marked deprecated in version
5.6.0
are now marked obsolete, and will prevent the plugin from starting. - These settings are:
cacert
, which should be replaced byssl_certificate_authorities
client_cert
, which should be replaced byssl_certificate
client_key
, which should be replaced byssl_key
keystore
, which should be replaced byssl_keystore_path
keystore_password
, which should be replaced byssl_keystore_password
keystore_type
, which should be replaced byssl_keystore_password
truststore
, which should be replaced byssl_truststore_path>
truststore_password
, which should be replaced byssl_truststore_password
truststore_type
, which should be replaced byssl_truststore_type
- #147
- Added new development
rackup
dependency to fix tests
- Added new
ssl_enabled
setting for enabling/disabling the SSL configurations #144
- Added body logging for non 2xx responses #142
- Added standardized SSL settings and deprecates their non-standard counterparts. Deprecated settings will continue to work, and will provide pipeline maintainers with guidance toward using their standardized counterparts #140
- Added new
ssl_truststore_path
,ssl_truststore_password
, andssl_truststore_type
settings for configuring SSL-trust using a PKCS-12 or JKS trust store, deprecating theirtruststore
,truststore_password
, andtruststore_type
counterparts. - Added new
ssl_certificate_authorities
setting for configuring SSL-trust using a PEM-formatted list certificate authorities, deprecating itscacert
counterpart. - Added new
ssl_keystore_path
,ssl_keystore_password
, andssl_keystore_type
settings for configuring SSL-identity using a PKCS-12 or JKS key store, deprecating theirkeystore
,keystore_password
, andkeystore_type
counterparts. - Added new
ssl_certificate
andssl_key
settings for configuring SSL-identity using a PEM-formatted certificate/key pair, deprecating theirclient_cert
andclient_key
counterparts. - Added the
ssl_cipher_suites
option
- Feat: added
ssl_supported_protocols
option #131
- Fix retry indefinitely in termination process. This feature requires Logstash 8.1 #129
- Docs: Add retry policy description #130
- Introduce retryable unknown exceptions for "connection reset by peer" and "timeout" #127
- Feat: support ssl_verification_mode option #126
- Reduce amount of default logging on a failed request #122
- Relax dependency on http_client mixin since current major works on both
- Fixed handling of empty
retryable_codes
#99
- Docs: Set the default_codec doc attribute.
- Added json_batch format
- Make 429 responses log at debug, not error level. They are really just flow control
- Add check to avoid hanging pipeline if an empty event array is passed in. #80
- Update gemspec summary
- Adding a new option
http_compression
for sending compressed payload with theContent-Encoding: gzip
header to the configured http endpoint #66
- Fix some documentation issues
- Breaking: bump dependency in breaking version of logstash-mixin-http_client
- Docs: Add plugin description.
- Docs: Update plugin title.
- Fix deadlock that could occur in certain situations. All users should upgrade to the latest version. This deadlock was caused by certain async HTTP APIs being called out of order thus creating a race.
- Add
user
andpassword
options to support HTTP basic auth
- Allow nested array in field definition, See #53
- Allow nested field definitions in
mappings
- Major overhaul of internals, adds new retry options
- Allow users to specify non-standard response codes as ignorable
- Set concurrency level to shared allowing for greater efficiency across threads
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- breaking,config: Remove deprecated config 'verify_ssl'. Please use 'ssl_certificate_validation'.
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- 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
- Require http_client mixin with better keepalive handling
- Properly close the client on #close
- Optimized execution for Logstash 2.2 ng pipeline
- fixed memory leak
- fixed potential race condition on async callbacks
- silenced specs equest logs and other spec robustness fixes
- 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
- Concurrent execution
- Add many HTTP options via the http_client mixin
- Switch to manticore as HTTP Client