-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Support for non-Elastic *search engines e.g. AWS Opensearch #189
Comments
Will it require a new appender, or can it auto-detect which gem is loaded and use that one automatically? I.e. Is the new opensearch-ruby gem a drop-in replacement? |
If the API is the same, other than the gem and class name, I can create a proof of concept branch if you want to try it out? |
Thanks for the response. At this time the gem APIs are close if not identical - who knows what will happen over time. As for "Will it require a new appender, or can it auto-detect which gem is loaded and use that one automatically?", I'm not sure what you mean by "it", but it's pretty clear that Elastic users will continue to use the |
Just happily installed
rails_semantic_logger
in our project, very happy to be using it, thank you! However, we're migrating to AWS OpenSearch rather than Elastic's offering, due to our take on Elastic's approach to Free Software licensing and the community.I naively added the
elasticsearch
gem toGemfile
and of course:I can pin to 7.13.0 for now as per https://opensearch.org/docs/latest/clients/index/, but it doesn't feel like a long term solution. Will
semantic_logger
be able to support the opensearch-ruby as an alternative?The text was updated successfully, but these errors were encountered: