You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 to Gemfile and of course:
E [2308:SemanticLogger::Appender::Elas] SemanticLogger::Appender::Elasticsearch -- Async: Restarting due to exception -- Exception: Elasticsearch::UnsupportedProductError: The client noticed that the server is not Elasticsearch and we do not support this unknown product.
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?
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 elasticsearch-ruby gem, and AWS OpenSearch users will use the opensearch-ruby gem (or elasticsearch-ruby pinned to 7.13.0). It is possible at runtime to fingerprint the ES/OS server via an HTTP request, but of course this is too late in the day to decide which gem to install.
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: