# elasticsearch

Elasticsearch is a distributed search and analytics engine, scalable data store, and vector database built on Apache Lucene.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Why Front migrated from Elasticsearch to ClickHouse for "pixel-perfect" analytics at scale

DevFeed: [Why Front migrated from Elasticsearch to ClickHouse for "pixel-perfect" analytics at scale](<https://devfeed.tech/articles/why-front-migrated-from-elasticsearch-to-clickhouse-for-pixel-perfect-analytics-at-scale-144379.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/front-elasticsearch-clickhouse>)

Author: ClickHouse

Published: 2026-11-18T00:00:00Z

Content type: news

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Analytics Pipeline](<https://devfeed.tech/topics/analytics-pipeline.md>), [metric-standardization](<https://devfeed.tech/topics/metric-standardization.md>), [product analytics](<https://devfeed.tech/topics/product-analytics.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>)

Tags: [aggregation](<https://devfeed.tech/tags/aggregation.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [aws](<https://devfeed.tech/tags/aws.md>), [b2b](<https://devfeed.tech/tags/b2b.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [days](<https://devfeed.tech/tags/days.md>), [development](<https://devfeed.tech/tags/development.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [metric](<https://devfeed.tech/tags/metric.md>), [more](<https://devfeed.tech/tags/more.md>), [pixel](<https://devfeed.tech/tags/pixel.md>), [scale](<https://devfeed.tech/tags/scale.md>)

### AI overview

Front moved customer-facing analytics from Elasticsearch to ClickHouse Cloud as its 25 TB workload and specialized Painless queries made new metrics slow and dependent on senior analytics engineers. It migrated gradually, writing each new event to both systems and comparing metrics, then defined each metric once in a shared framework that generates visualizations. For mutable conversations, VersionedCollapsingMergeTree reconciles changes such as deleted messages and merged threads. In one large customer's tag report, a 30-second query grew from 11 days of history in Elasticsearch to a month and a half in ClickHouse, using half as many machines of equal performance. The first metric built in the new framework took a junior engineer three days, versus several weeks for a senior engineer with Elasticsearch. The account also reports cloud-region moves dropping from days to minutes. Front says the change enables more flexible dashboards and plans to explore backlog metrics and AI-assisted metric creation.

### Source excerpt

Front powers customer-facing analytics for 9,000+ B2B companies with ClickHouse Cloud, cutting metric development from three weeks to three days and querying 4x more historical data.

## Prescale the search tier ahead of traffic with Minimum Search VCUs for Elasticsearch Serverless

DevFeed: [Prescale the search tier ahead of traffic with Minimum Search VCUs for Elasticsearch Serverless](<https://devfeed.tech/articles/prescale-the-search-tier-ahead-of-traffic-with-minimum-search-vcus-for-elasticsearch-serverless-140645.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/minimum-search-vcus-elasticsearch-serverless>)

Author: Yuvraj Gupta

Published: 2026-11-17T16:32:27Z

Content type: tutorial

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [billing](<https://devfeed.tech/tags/billing.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [elastic-cloud-serverless](<https://devfeed.tech/tags/elastic-cloud-serverless.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [operations](<https://devfeed.tech/tags/operations.md>), [search](<https://devfeed.tech/tags/search.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

Minimum Search VCUs lets you prescale an Elasticsearch Serverless search tier for predictable traffic while autoscaling remains active above the configured floor. Use the last 10 days of Search VCU usage to choose a whole-number minimum between observed baseline and peak, and set it about 30-60 minutes before demand arrives. The article cites sales and predictable workday or shift traffic as examples, and says to lower the minimum when the busy period ends. You are billed for at least the configured VCUs while enabled, even when idle or below that level; autoscaled capacity above the minimum is billed while provisioned. Configure it in the Elastic Cloud console by reviewing the VCUs chart, enabling the setting, entering a minimum, and confirming the change and billing implications. It can also be set or disabled through the API.

### Source excerpt

Set Minimum Search VCUs on Elasticsearch Serverless so the search tier stays provisioned at the level you choose. Autoscaling can still raise it as search load grows.

## CVE-2026-76823 - OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig

DevFeed: [CVE-2026-76823 - OpenCTI: Elasticsearch credentials disclosed to connector tokens through logsWorkerConfig](<https://devfeed.tech/articles/cve-2026-76823-opencti-elasticsearch-credentials-disclosed-to-connector-tokens-through-logsworkerconfig-136285.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-76823>)

Author: CVEFEED.io; github.com

Published: 2026-11-16T21:17:31Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [audit](<https://devfeed.tech/tags/audit.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [capability](<https://devfeed.tech/tags/capability.md>), [citeum](<https://devfeed.tech/tags/citeum.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76823](<https://devfeed.tech/tags/cve-2026-76823.md>), [delete](<https://devfeed.tech/tags/delete.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [history](<https://devfeed.tech/tags/history.md>), [impact](<https://devfeed.tech/tags/impact.md>), [index](<https://devfeed.tech/tags/index.md>), [opencti](<https://devfeed.tech/tags/opencti.md>), [opencti-platform](<https://devfeed.tech/tags/opencti-platform.md>), [published](<https://devfeed.tech/tags/published.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

Before OpenCTI 7.260706.0, the logsWorkerConfig GraphQL query uses the broad CONNECTORAPI capability and exposes Elasticsearch connection details, including credentials, to anyone holding a connector API bearer token. If those credentials are valid and Elasticsearch is reachable, a caller may read, modify, or delete OpenCTI indices and audit history outside application-layer controls; impact depends on credential privileges and network reachability. The issue is fixed in version 7.260706.0.

### Source excerpt

CVE ID :CVE-2026-76823 Published : Nov. 16, 2026, 9:17 p.m. | 1 hour, 37 minutes ago Description :OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260706.0, the logsWorkerConfig GraphQL query is authorized with the broad CONNECTORAPI capability and returns Elasticsearch connection details including elasticsearch_username, elasticsearch_password, elasticsearch_api_key, the URL, index, proxy, and TLS-verification setting. A holder of any connector API bearer token can retrieve this credential material. If the returned credentials are valid and Elasticsearch is reachable, the caller can directly read, modify, or delete OpenCTI indices and audit history outside application-layer role, marking, organization, and audit controls, with the practical impact bounded by the credentials' privileges and network reachability. This issue is fixed in version 7.260706.0. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Too much of a good thing: Why 20 candidates beat 200 when reranking search results

DevFeed: [Too much of a good thing: Why 20 candidates beat 200 when reranking search results](<https://devfeed.tech/articles/too-much-of-a-good-thing-why-20-candidates-beat-200-when-reranking-search-results-132453.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/jina-reranker-candidate-pool-size>)

Author: Scott Martens,Sofia Vasileva

Published: 2026-11-13T16:15:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [search-engines](<https://devfeed.tech/topics/search-engines.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [AI-driven information retrieval](<https://devfeed.tech/topics/ai-driven-information-retrieval.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [all](<https://devfeed.tech/tags/all.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bm25](<https://devfeed.tech/tags/bm25.md>), [but](<https://devfeed.tech/tags/but.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [good](<https://devfeed.tech/tags/good.md>), [help](<https://devfeed.tech/tags/help.md>), [jina-ai](<https://devfeed.tech/tags/jina-ai.md>), [just](<https://devfeed.tech/tags/just.md>), [ml-research](<https://devfeed.tech/tags/ml-research.md>), [more](<https://devfeed.tech/tags/more.md>), [relevance](<https://devfeed.tech/tags/relevance.md>), [reranker](<https://devfeed.tech/tags/reranker.md>), [reranking](<https://devfeed.tech/tags/reranking.md>), [results](<https://devfeed.tech/tags/results.md>), [search](<https://devfeed.tech/tags/search.md>), [semantic](<https://devfeed.tech/tags/semantic.md>), [semantic-search](<https://devfeed.tech/tags/semantic-search.md>), [thing](<https://devfeed.tech/tags/thing.md>), [v3-5](<https://devfeed.tech/tags/v3-5.md>)

### AI overview

Across 25 retrieval benchmarks, jina-reranker-v3.5 performed best with different candidate pool sizes depending on first-stage retrieval: about 100 candidates for Elasticsearch BM25 and 20 for jina-embeddings-v5-text-small semantic search. With BM25, 50 candidates retained nearly all the accuracy of 100 while halving token use; with semantic search, 200 candidates scored worse on average than using no reranker. The article attributes this to listwise rerankers processing candidates together, making them vulnerable to noise and attention dilution. Better initial retrieval leaves less for reranking to improve. Results varied by benchmark, so the authors recommend measuring on the target data. For Elasticsearch, they outline adding a text_similarity_reranker and tuning rank_window_size: start at 100 for BM25 or 20 for semantic search, then compare performance.

### Source excerpt

We expected more candidates to help, but across 25 benchmarks in Elasticsearch jina-reranker-v3.5 peaked at 100 candidates for BM25 and just 20 for semantic search, where 200 scored worse than no reranker at all.

## No pipeline, no second copy: Querying Amazon S3 from Elasticsearch with ES|QL

DevFeed: [No pipeline, no second copy: Querying Amazon S3 from Elasticsearch with ES|QL](<https://devfeed.tech/articles/no-pipeline-no-second-copy-querying-amazon-s3-from-elasticsearch-with-es-ql-130587.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/query-amazon-s3-esql-data-federation>)

Author: Udayasimha Theepireddy,Srinivas Pendyala

Published: 2026-11-11T17:00:00Z

Content type: tutorial

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [kibana](<https://devfeed.tech/topics/kibana.md>), [Parquet files in Amazon S3](<https://devfeed.tech/topics/parquet-files-in-amazon-s3.md>), [etl](<https://devfeed.tech/topics/etl.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [VPC Flow Logs](<https://devfeed.tech/topics/vpc-flow-logs.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [copy](<https://devfeed.tech/tags/copy.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [data](<https://devfeed.tech/tags/data.md>), [data-federation](<https://devfeed.tech/tags/data-federation.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [es-ql](<https://devfeed.tech/tags/es-ql.md>), [federated](<https://devfeed.tech/tags/federated.md>), [identity](<https://devfeed.tech/tags/identity.md>), [index](<https://devfeed.tech/tags/index.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [query](<https://devfeed.tech/tags/query.md>), [querying](<https://devfeed.tech/tags/querying.md>), [s3](<https://devfeed.tech/tags/s3.md>), [source](<https://devfeed.tech/tags/source.md>), [syntax](<https://devfeed.tech/tags/syntax.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

ES|QL Data Federation lets Elasticsearch query Parquet, CSV, TSV, and NDJSON files in Amazon S3 using the usual `FROM` syntax, without copying data into the cluster or defining mappings. It infers schemas from files and can push filters and column selection into the Parquet reader; datasets share a namespace with indices, allowing queries across hot indices and S3 data. Setup requires Elastic Cloud Hosted 9.5 or later with an Enterprise subscription; 9.5 requires enabling the feature and specifying the S3 region, while 9.6 enables it by default and detects the region. Federated identity uses temporary AWS credentials and is available only on Hosted; self-managed, ECE, and ECK deployments use static credentials. AWS access can be scoped to `s3:GetObject` and `s3:ListBucket`. Federation incurs S3 read and possible transfer costs, while indexing may be appropriate for workloads requiring kNN, joins, or time-series functions. The feature is described as experimental in 9.5 and 9.6, so the source recommends treating it as exploratory.

### Source excerpt

With ES|QL Data Federation, an S3 bucket is a data source you query with the same FROM syntax you use for an index, and federated identity keeps AWS credentials out of Elasticsearch.

## Fine-grained authorization for Elasticsearch RAG with SpiceDB

DevFeed: [Fine-grained authorization for Elasticsearch RAG with SpiceDB](<https://devfeed.tech/articles/fine-grained-authorization-for-elasticsearch-rag-with-spicedb-129234.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/fine-grained-authorization-elasticsearch-rag-spicedb>)

Author: Sohan Maheshwar,Carly Richmond

Published: 2026-11-11T16:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [Authorization](<https://devfeed.tech/topics/authorization.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-rag](<https://devfeed.tech/tags/agentic-rag.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-chatbot](<https://devfeed.tech/tags/ai-chatbot.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [chatbot](<https://devfeed.tech/tags/chatbot.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [graph](<https://devfeed.tech/tags/graph.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [llm](<https://devfeed.tech/tags/llm.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [rag](<https://devfeed.tech/tags/rag.md>), [rag-pipeline](<https://devfeed.tech/tags/rag-pipeline.md>), [vector-database](<https://devfeed.tech/tags/vector-database.md>)

### AI overview

The excerpt describes a RAG authorization design in which Elasticsearch retrieves relevant chunks and SpiceDB checks each chunk's document ID and user before content reaches the LLM. A deterministic LangGraph authorization node filters unauthorized documents; missing IDs, denied checks, or errors fail closed, and the agent cannot bypass the check. SpiceDB models access as relationships, supporting department membership, document sharing, and individual exceptions without changing roles or reindexing. Compared with Elasticsearch document-level security, this keeps relationship rules in a shared graph rather than denormalizing them into indexed documents. The excerpt notes that post-filtering can reduce available context, recommends overfetching and optional metadata prefilters, and describes LookupResources as an alternative for some access patterns, with result-size limits. Production setup requires keeping relationships synchronized and using a persistent SpiceDB datastore.

### Source excerpt

Department filters break the first time Engineering shares one document with Sales, so SpiceDB checks each retrieved chunk against a relationship graph before your Elasticsearch RAG pipeline passes it to the LLM.

## 56 scanned pages to a cited answer in 5 minutes: RAG pipeline for the documents search cannot read

DevFeed: [56 scanned pages to a cited answer in 5 minutes: RAG pipeline for the documents search cannot read](<https://devfeed.tech/articles/56-scanned-pages-to-a-cited-answer-in-5-minutes-rag-pipeline-for-the-documents-search-cannot-read-95936.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/rag-pipeline-scanned-pdf-jina-ocr>)

Author: Ben-Amin York Jr.

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [hybrid-search](<https://devfeed.tech/topics/hybrid-search.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [document ai](<https://devfeed.tech/topics/document-ai.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>), [pdf](<https://devfeed.tech/topics/pdf.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [back-end](<https://devfeed.tech/tags/back-end.md>), [base64](<https://devfeed.tech/tags/base64.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [chat](<https://devfeed.tech/tags/chat.md>), [chatbot](<https://devfeed.tech/tags/chatbot.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-haiku-4-5](<https://devfeed.tech/tags/claude-haiku-4-5.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [database](<https://devfeed.tech/tags/database.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [hybrid-search](<https://devfeed.tech/tags/hybrid-search.md>), [jina-ai](<https://devfeed.tech/tags/jina-ai.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [ocr](<https://devfeed.tech/tags/ocr.md>), [pdf](<https://devfeed.tech/tags/pdf.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [rag](<https://devfeed.tech/tags/rag.md>), [search](<https://devfeed.tech/tags/search.md>), [structured](<https://devfeed.tech/tags/structured.md>), [table](<https://devfeed.tech/tags/table.md>), [vector-database](<https://devfeed.tech/tags/vector-database.md>)

### AI overview

The described pipeline turns scanned PDFs into searchable, page-cited answers by sending each page image to jina-ocr-v1, which returns structured Markdown with tables, reading order, and inline handwriting. An Express server runs four pages in parallel through Elastic Inference Service and records page markers; Elasticsearch's semantic_text field chunks and embeds the Markdown at ingest. Hybrid retrieval combines lexical matching for exact terms with semantic matching for meaning, then Claude Haiku 4.5 generates answers grounded in retrieved sources and recommends only catalog products. The example uses a 56-page plant guide and a 48-plant catalog. Unlike the described legacy OCR chain of separate layout, recognition, table, and reading-order models, jina-ocr-v1 handles these in one pass. Each page must still be looped through individually; the article says legibility holds up to about 2048 x 2048 pixels. EIS is metered per token and billed as a Serverless add-on.

### Source excerpt

Ask a scanned, table-heavy PDF a question in plain language and get an answer stamped with the page it came from, because jina-ocr-v1 turns every page into structured Markdown that Elasticsearch embeds at ingest.

## The fastest work is the work you never do: 100x faster sorted queries in Elasticsearch

DevFeed: [The fastest work is the work you never do: 100x faster sorted queries in Elasticsearch](<https://devfeed.tech/articles/the-fastest-work-is-the-work-you-never-do-100x-faster-sorted-queries-in-elasticsearch-78803.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/elasticsearch-performance-tuning-esql-topn>)

Author: Attila Sahi

Published: 2026-10-05T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [es-ql](<https://devfeed.tech/tags/es-ql.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [inside-elastic](<https://devfeed.tech/tags/inside-elastic.md>), [lucene](<https://devfeed.tech/tags/lucene.md>)

### AI overview

Elasticsearch 9.6 introduces min-competitive TopN for ES|QL queries sorted by @timestamp. As the TopN heap fills, ES|QL shares its competitive threshold with Lucene and across execution drivers, allowing work on candidates that cannot improve the result to be skipped. In a benchmark over 346 million Nginx log documents, the query fell from about 500 seconds to 5 seconds on one node and gained 37x on Elastic Cloud Serverless. Benefits vary with the query and data; the current optimization applies to @timestamp-sorted queries.

### Source excerpt

How Elasticsearch 9.6 lets ES|QL push its current TopN threshold into Lucene, and how that 100x shows up on some sorted queries and barely registers on others.

## Check 100 candidates, not 10 million documents: Faster kNN filters in Elasticsearch

DevFeed: [Check 100 candidates, not 10 million documents: Faster kNN filters in Elasticsearch](<https://devfeed.tech/articles/check-100-candidates-not-10-million-documents-faster-knn-filters-in-elasticsearch-78859.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/knn-filter-post-filtering>)

Author: Panagiotis Bailis

Published: 2026-10-02T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [hybrid-search](<https://devfeed.tech/topics/hybrid-search.md>), [Qdrant](<https://devfeed.tech/topics/qdrant.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [inside-elastic](<https://devfeed.tech/tags/inside-elastic.md>), [lucene](<https://devfeed.tech/tags/lucene.md>), [search](<https://devfeed.tech/tags/search.md>), [vector](<https://devfeed.tech/tags/vector.md>), [vector-database](<https://devfeed.tech/tags/vector-database.md>), [vector-search](<https://devfeed.tech/tags/vector-search.md>)

### AI overview

Elasticsearch introduces adaptive post-filtering for filtered kNN queries, choosing per query whether to filter before or after vector search. In benchmarks on a 10-million-vector corpus, post-filtering was faster in 104 of 120 filtered comparisons, with recall within 0.01 of pre-filtering. The article describes candidate sizing, retry and fallback behavior, and the feature's planned default availability in Elasticsearch 9.6.

### Source excerpt

Elasticsearch now decides for each query whether to run a kNN filter before or after the vector search. On a 10M-vector corpus post-filtering was faster in 104 of 120 benchmark pairs while still returning k results.

## How LinkedIn extended ClickHouse from distributed tracing to metric discovery and analytics

DevFeed: [How LinkedIn extended ClickHouse from distributed tracing to metric discovery and analytics](<https://devfeed.tech/articles/how-linkedin-extended-clickhouse-from-distributed-tracing-to-metric-discovery-and-analytics-63145.md>)

Original publisher: [Read original article](<https://clickhouse.com/blog/linkedin-observability-at-scale>)

Author: ClickHouse

Published: 2026-10-01T11:47:10Z

Content type: article

Language: en

Sources: [ClickHouse Blog](<https://devfeed.tech/sources/clickhouse-blog.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [bloom-filter](<https://devfeed.tech/tags/bloom-filter.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

LinkedIn expanded its ClickHouse observability stack from distributed tracing to a metric metadata index that consolidates more than 13 billion metrics. The index serves over 150,000 queries per minute at an average latency of 68 milliseconds, while the migration reduced memory use to about one-fifth and compute to about two-thirds of the previous stack.

### Source excerpt

LinkedIn expanded its ClickHouse observability stack from distributed tracing to metric discovery and analytics, consolidating 13B+ metrics into one index serving 150k+ queries per minute.

## Migrating Elasticsearch Mappings to Azure Cosmos DB

DevFeed: [Migrating Elasticsearch Mappings to Azure Cosmos DB](<https://devfeed.tech/articles/migrating-elasticsearch-mappings-to-azure-cosmos-db-63195.md>)

Original publisher: [Read original article](<https://devblogs.microsoft.com/cosmosdb/migrating-elasticsearch-mappings-to-azure-cosmos-db/>)

Author: Madeline Egan

Published: 2026-10-01T07:00:57Z

Content type: tutorial

Language: en

Sources: [Azure Cosmos DB Blog](<https://devfeed.tech/sources/azure-cosmos-db-blog.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [azure functions](<https://devfeed.tech/topics/azure-functions.md>)

Tags: [azure-cosmos-db](<https://devfeed.tech/tags/azure-cosmos-db.md>), [azure-cosmos-db-for-nosql](<https://devfeed.tech/tags/azure-cosmos-db-for-nosql.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [migration](<https://devfeed.tech/tags/migration.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

The article explains how to migrate Elasticsearch mappings to Azure Cosmos DB container configuration. It recommends translating each field according to how the application queries it, using indexing, full-text, vector, and computed-property policies to preserve behavior. It also outlines inventory, policy design, validation, and rollout steps.

### Source excerpt

This post focuses on one of the most important design tasks when migrating from Elasticsearch to Azure Cosmos DB: translating an Elasticsearch mapping into Azure Cosmos DB container configuration. In Elasticsearch, a mapping defines how document fields are stored and indexed. Azure Cosmos DB is schema-agnostic, so there is no single mapping document to translate. [...] The post Migrating Elasticsearch Mappings to Azure Cosmos DB appeared first on Azure Cosmos DB Blog.

## Building production-ready AI in India

DevFeed: [Building production-ready AI in India](<https://devfeed.tech/articles/building-production-ready-ai-in-india-62682.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/mumbai-forge-the-future-hackathon-2026>)

Author: Ravindra Ramnani

Published: 2026-09-30T00:00:00Z

Content type: news

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Hacktoberfest](<https://devfeed.tech/topics/hacktoberfest.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [context-engineering](<https://devfeed.tech/tags/context-engineering.md>), [hackathon](<https://devfeed.tech/tags/hackathon.md>), [healthcare](<https://devfeed.tech/tags/healthcare.md>), [hybrid-search](<https://devfeed.tech/tags/hybrid-search.md>), [india](<https://devfeed.tech/tags/india.md>), [latency](<https://devfeed.tech/tags/latency.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

The Forge the Future Hackathon 2026 brought developer teams in India together to build production-ready AI applications. Elasticsearch supported hybrid search, context engineering, and real-time log monitoring. The article reports that finalists tackled enterprise challenges in areas including compliance, observability, and healthcare, with three teams named as winners.

### Source excerpt

See how developer teams in India built production-ready AI applications with Elasticsearch for the Forge the Future Hackathon 2026, with winners crowned at Elastic{ON} Mumbai.

## Using Jev as a search reranker: benchmarks and how to implement

DevFeed: [Using Jev as a search reranker: benchmarks and how to implement](<https://devfeed.tech/articles/using-jev-as-a-search-reranker-benchmarks-and-how-to-implement-78762.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/ecommerce-search-reranking-llm-alternative-jev>)

Author: Dustin Coates

Published: 2026-09-30T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [code search](<https://devfeed.tech/topics/code-search.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [hybrid-search](<https://devfeed.tech/topics/hybrid-search.md>), [LLM evaluation / benchmarking](<https://devfeed.tech/topics/llm-evaluation-benchmarking.md>), [sentence-transformers](<https://devfeed.tech/topics/sentence-transformers.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>)

Tags: [0-1](<https://devfeed.tech/tags/0-1.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bm25](<https://devfeed.tech/tags/bm25.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [hybrid-search](<https://devfeed.tech/tags/hybrid-search.md>), [implement](<https://devfeed.tech/tags/implement.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [jev](<https://devfeed.tech/tags/jev.md>), [python](<https://devfeed.tech/tags/python.md>), [relevance](<https://devfeed.tech/tags/relevance.md>), [reranking](<https://devfeed.tech/tags/reranking.md>), [search](<https://devfeed.tech/tags/search.md>), [shopping](<https://devfeed.tech/tags/shopping.md>)

### AI overview

The article describes a benchmark of Jev, TypeSafe AI's System One model, for reranking ecommerce search results retrieved by Elasticsearch. On a 250-query Amazon Shopping Queries test set, its best composite policy raised nDCG@10 from 0.9351 to 0.9565 and Exact MRR from 0.9201 to 0.9616. The benchmark compares several Jev scoring policies with BM25, hybrid retrieval, and a Jina reranker, and provides a Python implementation. The authors caution that this is one test on one dataset, with a high proportion of Exact judgments.

### Source excerpt

We had Jev score Elasticsearch hybrid search results and let a short Python policy do the reranking, taking nDCG@10 from 0.9351 to 0.9565 on 250 Amazon Shopping Queries, and the code is all here.

## Elastic Bridge: Eloquent-Style Queries for Elasticsearch and OpenSearch

DevFeed: [Elastic Bridge: Eloquent-Style Queries for Elasticsearch and OpenSearch](<https://devfeed.tech/articles/elastic-bridge-eloquent-style-queries-for-elasticsearch-and-opensearch-61663.md>)

Original publisher: [Read original article](<https://laravel-news.com/elastic-bridge>)

Author: Yannick Lyn Fatt

Published: 2026-09-29T04:03:08Z

Content type: article

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [opensearch](<https://devfeed.tech/topics/opensearch.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Laravel](<https://devfeed.tech/topics/laravel.md>), [Eloquent ORM](<https://devfeed.tech/topics/eloquent.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-packages](<https://devfeed.tech/tags/laravel-packages.md>), [opensearch](<https://devfeed.tech/tags/opensearch.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Elastic Bridge is a Laravel package that provides a fluent Eloquent-style PHP API for querying Elasticsearch and OpenSearch. The article covers index bridges, full-text search, filters, pagination, aggregations, testing without a live search cluster, installation requirements, and backend configuration.

### Source excerpt

Elastic Bridge brings fluent Elasticsearch and OpenSearch queries to Laravel, with model-style documents, aggregations, pagination, and testing fakes. The post Elastic Bridge: Eloquent-Style Queries for Elasticsearch and OpenSearch appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## How Elasticsearch Serverless hollow shards cut indexing-node shutdowns by 30%

DevFeed: [How Elasticsearch Serverless hollow shards cut indexing-node shutdowns by 30%](<https://devfeed.tech/articles/how-elasticsearch-serverless-hollow-shards-cut-indexing-node-shutdowns-by-30-78812.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/elasticsearch-serverless-hollow-shards>)

Author: Iraklis Psaroudakis,Eugene Cistiakovas

Published: 2026-09-29T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>)

Tags: [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [cost](<https://devfeed.tech/tags/cost.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-cloud](<https://devfeed.tech/tags/elastic-cloud.md>), [elastic-cloud-serverless](<https://devfeed.tech/tags/elastic-cloud-serverless.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [inside-elastic](<https://devfeed.tech/tags/inside-elastic.md>), [operations](<https://devfeed.tech/tags/operations.md>)

### AI overview

Elasticsearch Serverless hollow shards release idle Lucene writers and segment readers from indexing-node memory, retaining shard metadata until another write requires the engine to reload. In its first month in production, the change reduced high-percentile fleet indexing-node shutdown times by up to 30% and lowered indexing-tier heap usage. The tradeoff is a median 218 ms delay on the first write to a hollow shard; search latency is unchanged. Autoscaling still counts hollow shards as full, and the article notes that handling bursts of simultaneous unhollowing remains a planned improvement.

### Source excerpt

Idle indexing shards in Elasticsearch Serverless now drop their Lucene writers and segment readers from memory until the next write, freeing indexing-tier heap at the cost of a median 218ms wait on that first write.

## The best LLM writes correct Elasticsearch ES|QL 59% of the time. Here's what breaks the other 41%.

DevFeed: [The best LLM writes correct Elasticsearch ES|QL 59% of the time. Here's what breaks the other 41%.](<https://devfeed.tech/articles/the-best-llm-writes-correct-elasticsearch-es-ql-59-of-the-time-here-s-what-breaks-the-other-41-78894.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/text-to-esql-benchmark>)

Author: Jeffrey Rengifo,Gustavo Llermaly

Published: 2026-09-28T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [text2sql](<https://devfeed.tech/topics/text2sql.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [aggregate](<https://devfeed.tech/tags/aggregate.md>), [ai](<https://devfeed.tech/tags/ai.md>), [cardinality](<https://devfeed.tech/tags/cardinality.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [es-ql](<https://devfeed.tech/tags/es-ql.md>), [llm](<https://devfeed.tech/tags/llm.md>), [model](<https://devfeed.tech/tags/model.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query-languages](<https://devfeed.tech/tags/query-languages.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

The article benchmarks four language models on 6,000 ES|QL queries using BIRD's Mini-Dev questions and answer rows. The strongest model returned correct data on 59% of single-attempt queries. The analysis identifies mismatched join keys, invalid SQL syntax, counts inflated by one-to-many joins, and guessed data values as major failure sources. A compact ES|QL reference helped smaller models but reduced the strongest model's accuracy, while sample values can help address errors caused by assumptions about stored data.

### Source excerpt

We scored 6,000 ES|QL queries from four models against BIRD's answer key. Most misses come from mismatched join keys, SQL syntax the parser rejects, counting after a one-to-many join, or a value the model guessed.

## GPU-accelerated vector indexing in Elasticsearch with NVIDIA cuVS: 138M vectors in under 10 minutes

DevFeed: [GPU-accelerated vector indexing in Elasticsearch with NVIDIA cuVS: 138M vectors in under 10 minutes](<https://devfeed.tech/articles/gpu-accelerated-vector-indexing-in-elasticsearch-with-nvidia-cuvs-138m-vectors-in-under-10-minutes-78899.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/vector-indexing-gpu-elasticsearch-cuvs>)

Author: Bao Tong,Manas Singh,Corey Nolet

Published: 2026-09-25T00:00:00Z

Content type: article

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [CUDA](<https://devfeed.tech/topics/cuda.md>), [NVIDIA Blackwell](<https://devfeed.tech/topics/nvidia-blackwell.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-accelerated](<https://devfeed.tech/tags/gpu-accelerated.md>), [index-data](<https://devfeed.tech/tags/index-data.md>), [indexing](<https://devfeed.tech/tags/indexing.md>), [inside-elastic](<https://devfeed.tech/tags/inside-elastic.md>), [latency](<https://devfeed.tech/tags/latency.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [vector-database](<https://devfeed.tech/tags/vector-database.md>)

### AI overview

Elasticsearch and NVIDIA cuVS use GPUs to build vector indexes, with a benchmark indexing 138 million vectors in under 10 minutes. The article reports up to 7x higher indexing throughput, 6x lower p90 search latency during concurrent indexing, similar recall to CPU-built indexes, and shorter force-merge times.

### Source excerpt

Moving index builds to the GPU leaves the CPU free for queries, which is how vector indexing throughput went up 7x and p90 search latency fell 6x while indexing ran, with no change to recall.

## DevRel newsletter -- September 2026

DevFeed: [DevRel newsletter -- September 2026](<https://devfeed.tech/articles/devrel-newsletter-september-2026-60025.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/devrel-newsletter-september-2026>)

Author: Elastic DevRel team

Published: 2026-09-25T00:00:00Z

Content type: article

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [Parser](<https://devfeed.tech/topics/parser.md>), [Parsing](<https://devfeed.tech/topics/parsing.md>), [Mixture of Experts (MoE)](<https://devfeed.tech/topics/mixture-of-experts-moe.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [HTML](<https://devfeed.tech/topics/html.md>), [kibana](<https://devfeed.tech/topics/kibana.md>), [LaTeX](<https://devfeed.tech/topics/latex.md>), [on-prem](<https://devfeed.tech/topics/on-prem.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [api](<https://devfeed.tech/tags/api.md>), [apm](<https://devfeed.tech/tags/apm.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [devrel](<https://devfeed.tech/tags/devrel.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [events](<https://devfeed.tech/tags/events.md>), [inference](<https://devfeed.tech/tags/inference.md>), [large-language-model](<https://devfeed.tech/tags/large-language-model.md>), [latency](<https://devfeed.tech/tags/latency.md>), [llm](<https://devfeed.tech/tags/llm.md>), [newsletter](<https://devfeed.tech/tags/newsletter.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>)

### AI overview

Elastic's September 2026 DevRel newsletter covers jina-ocr-v1, an OCR and document-parsing model with layout-aware extraction, the Elastic CLI, Agent Skills, knowledge indicators for agents, LLM observability in Elastic APM, and a Cursor instrumentation study.

### Source excerpt

Hello from the Elastic DevRel team! In this newsletter, we cover jina-ocr-v1, the latest blogs and videos, and upcoming events like Elastic{ON}.

## Elastic Cloud on Azure gets a speed boost: Compute-optimized instances on Azure Cobalt ARM

DevFeed: [Elastic Cloud on Azure gets a speed boost: Compute-optimized instances on Azure Cobalt ARM](<https://devfeed.tech/articles/elastic-cloud-on-azure-gets-a-speed-boost-compute-optimized-instances-on-azure-cobalt-arm-59415.md>)

Original publisher: [Read original article](<https://www.elastic.co/blog/elastic-cloud-azure-cobalt-arm>)

Author: Joe Chin,Greg Crist

Published: 2026-09-24T00:00:00Z

Content type: release

Language: en

Sources: [Elastic Blog](<https://devfeed.tech/sources/elastic-blog-elasticsearch-kibana-and-elk-stack.md>)

Topics: [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>), [Arm](<https://devfeed.tech/topics/arm.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [arm](<https://devfeed.tech/tags/arm.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud-platform](<https://devfeed.tech/tags/cloud-platform.md>), [cloud-regions-deployment-microsoft-azure-optimizing](<https://devfeed.tech/tags/cloud-regions-deployment-microsoft-azure-optimizing.md>), [elastic-cloud](<https://devfeed.tech/tags/elastic-cloud.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [hybrid-search](<https://devfeed.tech/tags/hybrid-search.md>), [indexing](<https://devfeed.tech/tags/indexing.md>), [nvme](<https://devfeed.tech/tags/nvme.md>), [processors](<https://devfeed.tech/tags/processors.md>)

### AI overview

Elastic Cloud on Azure adds compute-optimized ARM hardware profiles using Microsoft's Cobalt processors and Dpldsv6 VM series. The article describes potential price-performance and throughput improvements for CPU-bound Elasticsearch workloads, including indexing, aggregations, and keyword, vector, semantic, and hybrid search.

### Source excerpt

Starting September 24, 2026, Elastic Cloud on Azure adds compute-optimized (ARM) hardware profiles backed by Microsoft's Cobalt ARM processors, delivering up to 37% better throughput than the previous generation Ampere Altra VMs at lower cost.

## Vector Search Is Now A Data Type, But The Money Math Has Not Gone Away

DevFeed: [Vector Search Is Now A Data Type, But The Money Math Has Not Gone Away](<https://devfeed.tech/articles/vector-search-is-now-a-data-type-but-the-money-math-has-not-gone-away-58281.md>)

Original publisher: [Read original article](<https://www.nextplatform.com/store/2026/09/22/vector-search-is-now-a-data-type-but-the-money-math-has-not-gone-away/5298393>)

Author: Itamar Syn-Hershko

Published: 2026-09-22T17:06:09Z

Content type: opinion

Language: en

Sources: [The Next Platform: In-depth coverage of high end computing](<https://devfeed.tech/sources/the-next-platform-in-depth-coverage-of-high-end-computing.md>)

Topics: [AI search](<https://devfeed.tech/topics/ai-search.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Database](<https://devfeed.tech/topics/database.md>), [Algorithms](<https://devfeed.tech/topics/algorithms.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ann](<https://devfeed.tech/tags/ann.md>), [approximate-nearest-neighbor-search](<https://devfeed.tech/tags/approximate-nearest-neighbor-search.md>), [database](<https://devfeed.tech/tags/database.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [embeddings](<https://devfeed.tech/tags/embeddings.md>), [hnsw](<https://devfeed.tech/tags/hnsw.md>), [opensearch](<https://devfeed.tech/tags/opensearch.md>), [store](<https://devfeed.tech/tags/store.md>), [vector](<https://devfeed.tech/tags/vector.md>), [vector-database](<https://devfeed.tech/tags/vector-database.md>), [vector-search](<https://devfeed.tech/tags/vector-search.md>)

### AI overview

The article argues that vector search is increasingly implemented as a data type and approximate nearest-neighbor index inside existing databases rather than through separate vector databases. It explains that consolidation reduces operational overhead but does not eliminate the cost of storing, compressing, and keeping embeddings in memory, and it describes the adoption of HNSW across major database and search platforms.

### Source excerpt

For a few years it looked like every AI stack would carry a dedicated vector database next to its pr ...

## Agentic workflows in Elasticsearch: pause an AI agent for human approval, resume 72 hours later

DevFeed: [Agentic workflows in Elasticsearch: pause an AI agent for human approval, resume 72 hours later](<https://devfeed.tech/articles/agentic-workflows-in-elasticsearch-pause-an-ai-agent-for-human-approval-resume-72-hours-later-78715.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/ai-agent-orchestration-human-approval-workflow>)

Author: Alex Salgado

Published: 2026-09-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>)

Tags: [agent-orchestration](<https://devfeed.tech/tags/agent-orchestration.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [index-data](<https://devfeed.tech/tags/index-data.md>), [operations](<https://devfeed.tech/tags/operations.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

This tutorial demonstrates an Elasticsearch workflow for diagnosing failed data ingestion and remediating it with AI agents while keeping human approval at key steps. Workflow state and audit records persist in Elasticsearch, allowing an approval gate to wait for up to 72 hours before resuming. The example includes alert-triggered diagnosis, approval or revision, automated reindexing, and a final verification or escalation decision.

### Source excerpt

Build AI agent orchestration where the workflow waits for a human approval and then executes the fix on its own, with nothing extra to provision and the whole decision trail queryable in Elasticsearch.

## AI video search with Elasticsearch and Jina: Find the exact seconds of footage you need

DevFeed: [AI video search with Elasticsearch and Jina: Find the exact seconds of footage you need](<https://devfeed.tech/articles/ai-video-search-with-elasticsearch-and-jina-find-the-exact-seconds-of-footage-you-need-78721.md>)

Original publisher: [Read original article](<https://www.elastic.co/search-labs/blog/ai-video-search-jina-embeddings>)

Author: JD Armada

Published: 2026-09-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [Elasticsearch Labs](<https://devfeed.tech/sources/elasticsearch-labs.md>)

Topics: [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [Embeddings](<https://devfeed.tech/topics/embeddings.md>), [cosine similarity search](<https://devfeed.tech/topics/cosine-similarity-search.md>), [Cohere API for embeddings](<https://devfeed.tech/topics/cohere-api-for-embeddings.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [jina-ai](<https://devfeed.tech/tags/jina-ai.md>), [query](<https://devfeed.tech/tags/query.md>), [search](<https://devfeed.tech/tags/search.md>), [vector](<https://devfeed.tech/tags/vector.md>), [vector-database](<https://devfeed.tech/tags/vector-database.md>)

### AI overview

This tutorial explains how to build an AI video search app that finds footage by text description and returns matching timestamps. It covers scene-based chunking, Jina multimodal embeddings, Elasticsearch vector indexing and nearest-neighbor search, and deduplicating results so editors can browse distinct clips. It also discusses proxy sizing and the index's memory costs as footage libraries grow.

### Source excerpt

Cut each clip at its shot boundaries and embed every scene as a vector, and a plain text query gives back the file plus the exact seconds to drop on a timeline.

## One SOC, 100 projects: running centralized alert triage on Elastic Security Serverless

DevFeed: [One SOC, 100 projects: running centralized alert triage on Elastic Security Serverless](<https://devfeed.tech/articles/one-soc-100-projects-running-centralized-alert-triage-on-elastic-security-serverless-48855.md>)

Original publisher: [Read original article](<https://www.elastic.co/security-labs/blog/centralized-alert-triage-cross-project-search>)

Author: Chuddy Park

Published: 2026-09-18T00:00:00Z

Content type: article

Language: en

Sources: [Elastic Security Labs](<https://devfeed.tech/sources/elastic-security-labs.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Security Operations Center](<https://devfeed.tech/topics/security-operations-center.md>), [Elastic Cloud](<https://devfeed.tech/topics/elastic-cloud.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [alert-triage](<https://devfeed.tech/tags/alert-triage.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [elastic](<https://devfeed.tech/tags/elastic.md>), [elastic-cloud](<https://devfeed.tech/tags/elastic-cloud.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [scale](<https://devfeed.tech/tags/scale.md>), [search](<https://devfeed.tech/tags/search.md>), [security](<https://devfeed.tech/tags/security.md>), [security-operations](<https://devfeed.tech/tags/security-operations.md>), [security-operations-center](<https://devfeed.tech/tags/security-operations-center.md>), [soc](<https://devfeed.tech/tags/soc.md>), [threat-hunting](<https://devfeed.tech/tags/threat-hunting.md>)

### AI overview

This technical post explains how Elastic Security Serverless uses cross-project search to support centralized alert triage across 100 linked projects. It describes the tested SOC workflow, detection-rule behavior, data isolation, query patterns, scaling considerations, and operational limitations.

### Source excerpt

We linked one Elastic Security project to 100 others and ran the full prebuilt detection catalog from the origin, with all the ingest landing in the linked projects. It held up, and where it deliberately does not reach is the interesting part.

## Telegraf 1.40 Release Notes

DevFeed: [Telegraf 1.40 Release Notes](<https://devfeed.tech/articles/telegraf-1-40-release-notes-56907.md>)

Original publisher: [Read original article](<https://www.influxdata.com/blog/telegraf-1-40-release-notes-influxdb/>)

Author: Sven Rebhan (InfluxData)

Published: 2026-09-15T00:00:00Z

Content type: release

Language: en

Sources: [InfluxData](<https://devfeed.tech/sources/influxdata.md>)

Topics: [Release notes](<https://devfeed.tech/topics/release-notes.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [databricks](<https://devfeed.tech/topics/databricks.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>), [elasticsearch](<https://devfeed.tech/topics/elasticsearch.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [cisco](<https://devfeed.tech/tags/cisco.md>), [databricks](<https://devfeed.tech/tags/databricks.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [developer](<https://devfeed.tech/tags/developer.md>), [elasticsearch](<https://devfeed.tech/tags/elasticsearch.md>), [github](<https://devfeed.tech/tags/github.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [notes](<https://devfeed.tech/tags/notes.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [product](<https://devfeed.tech/tags/product.md>), [release](<https://devfeed.tech/tags/release.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>)

### AI overview

Telegraf 1.40 adds Databricks Zerobus and Fritzbox Smarthome input plugins, fixes Cisco telemetry metrics, removes deprecated plugins and options, provides configuration migration support, and updates the Elasticsearch query input plugin with support for Elasticsearch v7, v8, and v9.

### Source excerpt

You can find the binaries for the latest Telegraf release on our Downloads page. Many thanks to all the open source community members who contributed to this effort! New plugins These are the newest plugins, first available in this version: Databricks Zerobus output (outputs.zerobus) Streams metrics to a Unity Catalog Delta table using the Databricks Zerobus Ingest service over gRPC to directly commit into Delta Contributed by zlata-stefanovic-db Fritzbox Smarthome input (inputs.fritzbox_smarthome) Reads metrics such as lamp state, energy consumption, etc., from Smarthome-capable FRITZ! routers using the AVM Home Automation interface. Contributed by hdecarne Important changes Here are some changes to highlight: Cisco Model-Driven-Telemetry fixes Several fixes changed the metric format Configured aliases are now respected for microburst and RIB messages, which might result in changes to the metric name Spurious, invalid metrics with wrong tag-sets were removed or corrected Row numbers are now tagged correctly for table messages Smart input fix for power-on-hours Power-on-hours are now reported correctly for raw values in 182h+39m+24.879s format Previously, those values resulted in the field containing the time in seconds Removal of deprecated plugins inputs.aerospike inputs.sflow outputs.amon Removal of deprecated plugin options inputs.kafka_consumer removal of connection_strategy inputs.openstack removal of server_diagnostics inputs.procstat removal of cmdline_tag, pid_tag, and supervisor_unit inputs.tail removal of from_beginning Use the telegraf config migrate command to migrate your configuration Elasticsearch query input plugin migration to official library Migration to official and maintained libraries Additional support for Elasticsearch v7, v8 and v9 Downloads Head to our Downloads page to get the latest Telegraf release. If you have issues or questions, please join our InfluxDB Community Slack or post them in our InfluxDB GitHub Repo or Community Site, and w

[Next page](<https://devfeed.tech/topics/elasticsearch.md?cursor=WyIyMDI2LTA5LTE1VDAwOjAwOjAwKzAwOjAwIiwgIjhkMjQwYTliLTk0NjEtNGU2Ni04MDFiLWM3YWE1NDViNGY3MyJd>)