Skip to main content

Elastic Brings Real-Time Graph Analytics to the Elastic Stack

Elastic unveiled Graph, a new extension for Elasticsearch and Kibana that allows anyone to uncover, understand, and explore the relationships that live in their data.

By combining the speed and relevance-ranking of search with graph exploration, Graph opens up a whole host of new use-cases with the Elastic Stack.

"We built Graph to help you ask new types of questions about the data you store in Elasticsearch," said Steve Kearns, Sr. Director of Product Management at Elastic. "By looking at the relationships in your data through the lens of relevance, it becomes easy to answer questions that previously would involve multiple systems, batch jobs or machine learning."

When you store data in Elasticsearch — products, users, documents, logs — this data often contains references or properties that represent connections between objects, entities, people, or machines. The best way to explore these connections is to see them, which Graph provides via a Kibana plugin. Like everything at Elastic, this UI is built on a simple, but powerful API that leverages Elastic’s experience in relevance ranking to surface the most meaningful connections that live in your data. This approach to graph exploration opens a wide range of new use-cases for the Elastic Stack, without requiring new index formats, by allowing users to query their existing data in new ways.

Graph makes it easy to answer complex questions and address use-cases such as behavioral analysis, fraud, cybersecurity, drug discovery, personalized medicine, and to build personalized recommendations based on continuous real-time data. Graph automatically identifies the most important connections, separating the signal from the noise by employing relevance ranking specific to each query. Because it is built on Elasticsearch, Graph benefits from high scalability and near-real-time data availability, enabling answers that evolve as your data changes.

When data is added to Elasticsearch, the indexing process tracks and counts the values in each field of the document, updates global frequencies, and prepares the data for a wide range of queries. These statistics are used to perform relevance ranking for search and efficiently summarize the data in Elasticsearch aggregations. With Graph, the Elastic Stack uses these statistics in new ways — first to identify relationships within and across sets of documents, and then to prioritize the most relevant relationships for the given query.

In contrast, traditional graph techniques are based on a simple count of the frequency of a given relationship. This approach has the drawback that elements with the most connections — the Shawshank Redemption in movie recommendation data or Starbucks in credit card purchase data — are returned as the most important. With Graph in Elasticsearch, relevance is calculated by correlating the significance of each relationship in comparison to global averages, bringing back the important results, and avoiding frequent connections.

"Graph is an excellent example of the limitless possibilities within our products and how we strive to make it as easy as possible for our users to leverage the power of the Elastic Stack," said Shay Banon, Co-Founder and CTO of Elastic. "I am proud to see our company continue to innovate, and I can’t wait to see the new ways in which our customers will adopt Graph to solve really challenging problems and use cases."

The Latest

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

Elastic Brings Real-Time Graph Analytics to the Elastic Stack

Elastic unveiled Graph, a new extension for Elasticsearch and Kibana that allows anyone to uncover, understand, and explore the relationships that live in their data.

By combining the speed and relevance-ranking of search with graph exploration, Graph opens up a whole host of new use-cases with the Elastic Stack.

"We built Graph to help you ask new types of questions about the data you store in Elasticsearch," said Steve Kearns, Sr. Director of Product Management at Elastic. "By looking at the relationships in your data through the lens of relevance, it becomes easy to answer questions that previously would involve multiple systems, batch jobs or machine learning."

When you store data in Elasticsearch — products, users, documents, logs — this data often contains references or properties that represent connections between objects, entities, people, or machines. The best way to explore these connections is to see them, which Graph provides via a Kibana plugin. Like everything at Elastic, this UI is built on a simple, but powerful API that leverages Elastic’s experience in relevance ranking to surface the most meaningful connections that live in your data. This approach to graph exploration opens a wide range of new use-cases for the Elastic Stack, without requiring new index formats, by allowing users to query their existing data in new ways.

Graph makes it easy to answer complex questions and address use-cases such as behavioral analysis, fraud, cybersecurity, drug discovery, personalized medicine, and to build personalized recommendations based on continuous real-time data. Graph automatically identifies the most important connections, separating the signal from the noise by employing relevance ranking specific to each query. Because it is built on Elasticsearch, Graph benefits from high scalability and near-real-time data availability, enabling answers that evolve as your data changes.

When data is added to Elasticsearch, the indexing process tracks and counts the values in each field of the document, updates global frequencies, and prepares the data for a wide range of queries. These statistics are used to perform relevance ranking for search and efficiently summarize the data in Elasticsearch aggregations. With Graph, the Elastic Stack uses these statistics in new ways — first to identify relationships within and across sets of documents, and then to prioritize the most relevant relationships for the given query.

In contrast, traditional graph techniques are based on a simple count of the frequency of a given relationship. This approach has the drawback that elements with the most connections — the Shawshank Redemption in movie recommendation data or Starbucks in credit card purchase data — are returned as the most important. With Graph in Elasticsearch, relevance is calculated by correlating the significance of each relationship in comparison to global averages, bringing back the important results, and avoiding frequent connections.

"Graph is an excellent example of the limitless possibilities within our products and how we strive to make it as easy as possible for our users to leverage the power of the Elastic Stack," said Shay Banon, Co-Founder and CTO of Elastic. "I am proud to see our company continue to innovate, and I can’t wait to see the new ways in which our customers will adopt Graph to solve really challenging problems and use cases."

The Latest

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.