-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving to the logstash-output-opensearch plugin #190
Comments
Please see below for common functionality and Plugin differences between the logstash-output-amazon_es and logtstash-output-opensearch plugins. Common Functionality
Plugin Differences
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The OpenSearch project has created a new Logstash output plugin which can send events to OpenSearch 1.x or Elasticsearch 7.x clusters - logstash-output-opensearch. Starting with logstash-output-opensearch 1.2 it also supports SigV4 signing.
Having both the logstash-output-opensearch and logstash-output-amazon_es plugins can be confusing since it becomes unclear which one to use. With that in mind, we are looking into eventually replacing the logstash-output-amazon_es plugin with the logstash-output-opensearch plugin.
For now, we will place the logstash-output-amazon_es plugin into a maintenance mode. We will supply critical bug fixes and security patches. But, new features and functionality should be considered for the logstash-output-opensearch plugin instead.
Both plugins have some overlapping compatibility:
As noted in the above table, the logstash-output-opensearch plugin does not support Elasticsearch 6.x. I've opened a feature request on that repo to support it - opensearch-project/logstash-output-opensearch#123.
We will provide a migration guide to help teams and individuals migrate to the logstash-output-opensearch plugin.
We will also triage issues from this GitHub repository and add them to the logstash-output-opensearch repository as needed. We will mostly focus on feature requests.
The text was updated successfully, but these errors were encountered: