Tags: logstash-plugins/logstash-output-elasticsearch
Tags
Properly handle 413 Payload Too Large errors (#1199) (#1206) * Properly handle `413` Payload Too Large errors Previously when Elasticsearch responds with a 413 (Payload Too Large) status, the manticore adapter raises an error before the response can be processed by the bulk_send error handling. This commit refactors the way `BadErrorResponse` codes are handled. Previously we had logic in the manticore adaptor which special cased raising errors on some codes. This commit refactors such that the adaptor raises on any error status and the caller is now responsible for special case handling the code. * 12.0.2 release prep * Use `error_code` instead of `code` when handling BadResponseCodeError Previously a few bugs spotted in code review were being obfuscated by the combinations of tests not running in CI and the incorrect method for retrieving a code from a BadResponseCodeError. This commit updates the method names and addresses the feedback from code review. --------- Co-authored-by: João Duarte <[email protected]>
Properly handle 413 Payload Too Large errors (#1199) * Properly handle `413` Payload Too Large errors Previously when Elasticsearch responds with a 413 (Payload Too Large) status, the manticore adapter raises an error before the response can be processed by the bulk_send error handling. This commit refactors the way `BadErrorResponse` codes are handled. Previously we had logic in the manticore adaptor which special cased raising errors on some codes. This commit refactors such that the adaptor raises on any error status and the caller is now responsible for special case handling the code. * 12.0.2 release prep * Use `error_code` instead of `code` when handling BadResponseCodeError Previously a few bugs spotted in code review were being obfuscated by the combinations of tests not running in CI and the incorrect method for retrieving a code from a BadResponseCodeError. This commit updates the method names and addresses the feedback from code review. --------- Co-authored-by: João Duarte <[email protected]>
Remove irrelevant warning (#1202) * Remove irrelevant warning This commit removes an old warning which is no longer relevant to any supported stack version. It is noisy and there is no action for the user to take. * Add changelog entry for log removal * 11.22.11 release prep Update version in preparation for a release.
Remove irrelevant warning (#1200) * Remove irrelevant warning This commit removes an old warning which is no longer relevant to any supported stack version. It is noisy and there is no action for the user to take. * Add changelog entry for log removal * 12.0.1 release prep Update version in preparation for a release.
Mark previously deprecated SSL settings as obsolete (#1197) * Mark previously deprecated SSL settings as obsolete - SSL settings that were marked deprecated in version `11.14.0` are now marked obsolete, and will prevent the plugin from starting. - These settings are: - `cacert`, which should be replaced by `ssl_certificate_authorities` - `keystore`, which should be replaced by `ssl_keystore_path` - `keystore_password`, which should be replaced by `ssl_keystore_password` - `ssl`, which should be replaced by `ssl_enabled` - `ssl_certificate_verification`, which should be replaced by `ssl_verification_mode` - `truststore`, which should be replaced by `ssl_truststore_path` - `truststore_password`, which should be replaced by `ssl_truststore_password` * Restore deleted footer Restore the deleted EOF as it is required for docs. * Remove reference to deprecated options * Remove characters copied from a diff view * Fix reference to old removed ssl setting Replace ssl with ssl_enabled. * Remove whitespace * Restore deleted pipe character * Add a note detailing removal Co-authored-by: Karen Metts <[email protected]> --------- Co-authored-by: Karen Metts <[email protected]>
Set x-elastic-product-origin header for ES requests (#1195) * Set x-elastic-product-origin header for ES requests This commit updates the Elasticsearch::Client used to make requests to ES to send along a header identifying the request as originating from an internal component. * Prep 11.22.10 release * Update integration test expectations Update integration tests to expect new headers where needed.
PreviousNext