This article is the third of a four-part series of articles about Elasticsearch monitoring. In the first article, we put together an Elasticsearch guide, covering how Elasticsearch works and why the setup and tuning of Elasticsearch requires a good knowledge of configuration options and performance metrics.
With Solr 9 the Autoscaling Framework was removed – for being too complex and not terribly reliable – and instead we have Replica Placement Plugins. Unlike Autoscaling, replica placement only happens when you create a collection or add a new replica. Hence the name: it’s about where to place these new replicas. In this article, we’ll look at the available replica placement plugins, what you can use them for and how to use them.
Elastic Enterprise Search 8.6 enables customers to index searchable content on file systems, network drives, MongoDB, and Amazon S3. With new connectors for network drives and Amazon S3, content indexed can easily be transformed for natural language processing (NLP) use cases with intuitive tooling to test and tune your search experience with the trained model of your choice.
When we created Cribl Search, we wanted to give systems administrators the ability to query data without having to spend resources on collection and processing first — but we didn’t stop there. With Search, we’re also making it possible to query all the data you’ve already collected, processed, and kept in places like object stores, file systems, analytics tools, S3 buckets, or other data stores.
