Elastic, the company behind Elasticsearch and the Elastic Stack, announced the general availability of version 7.0 of the Elastic Stack.
This release delivers several foundational changes including big improvements to query speed and relevance with the introduction of new query types in Elasticsearch, a fully revamped cluster coordination framework that hardens resiliency, and a completely redesigned Kibana interface that simplifies the user experience and navigation. Elastic Stack 7.0 is immediately available for download, or users can spin up fully managed deployments on the Elasticsearch Service on Elastic Cloud.
Kibana 7.0 delivers on a fresh user interface that embraces a lighter, cleaner, and more minimalist design aesthetic. The goal of the redesign is to put the content and data at the center of the user experience. The new design builds on months of engineering and design effort on the new Elastic UI framework, a set of consistent and reusable UI components that were first introduced in version 6.2. The result is a more uniform and consistent user experience across all touch points in Kibana. As another benefit of these changes, Kibana dashboards now have a responsive design, which is the first step in dramatically improving usability on mobile devices.
Kibana 7.0 also delivers on a much-requested feature: dark mode for all of Kibana. Previously, dark mode was limited to Kibana dashboards. By extending dark mode to all of Kibana, Elastic users that deploy Kibana in low-light environments, such as NOCs and SOCs, can enjoy an enhanced visual experience, with better contrast and improved readability of text.
Relevance and speed are the cornerstones of most search experiences. And Elasticsearch 7.0 introduces several foundational features that improve both.
- Faster top k queries: In many search use cases, quickly seeing the top k (say 20) results on a query matters much more to the user than the exact hit count (i.e., total number of results matching the query). For example, if someone is searching for a product on an e-commerce website, they are much more interested in the 10 most relevant results than the other 120,897 results that matched their search query. Elasticsearch 7.0 (and Lucene 8.0) implements a new algorithm (Block-Max WAND) that provides a huge speed boost when retrieving top hits.
- Intervals queries: Some search use cases, such as legal and patent search, introduce the need to find records in which words or phrases are within a certain distance from each other. Intervals queries in Elasticsearch 7.0 introduce a brand new way of structuring such queries and are significantly simpler to use and define compared to the previous methods (span queries). Intervals queries are also much more resilient to edge cases compared to span queries.
- Function score 2.0: Custom scoring is the bread and butter of advanced search use cases, where one wants finer control over relevancy and results ranking. Elasticsearch has provided the ability to do this since its early days. 7.0 introduces the next generation of function score capability, providing a simpler, modular, and more flexible way to generate a ranking score per record. The new modular structure allows users to mix and match a set of arithmetic and distance functions to construct arbitrary function score calculations, giving them more control over how results are scored and ranked.
Scale and resiliency have been central themes in Elasticsearch since the very beginning. The cluster coordination layer, called Zen Discovery, has been a key component of that resilient design. With Elasticsearch 7.0, Elastic has completely rebuilt this cluster coordination layer to be faster, safer, and easier to use. 7.0 also includes a number of changes that reduce the likelihood of human error and provide clearer choices when recovering from catastrophic failures. The ground-up rebuild of the cluster coordination layer was a huge accomplishment — it’s not easy to improve reliability, performance, and user experience all at once, especially in such a central component. Most importantly, the new cluster coordination layer provides strong building blocks for the future of Elasticsearch, ensuring that Elastic can build functionality for even more advanced use cases to come.
Another improvement to resiliency in 7.0 is the introduction of the real memory circuit breaker, which much more accurately detects unserviceable requests made to a node and prevents them from making an individual node unstable. This change significantly improves the overall node and cluster reliability.
Smoother Zoom in Elastic Maps with Geotile Grid
Geo is an integral part of most search experiences, and it has been an area of constant engineering investment for Elastic. Elastic added support for ingesting and querying geo data in very early versions of Elasticsearch, and then recently moved geo_point and geo_shapes to Bkd-backed storage structures, with significant storage and query performance improvements (in some cases by 25x). On the visual exploration end, the introduction of Elastic Maps in version 6.7 provided a dramatically improved way to visually map, explore, and query location data.
With 7.0, the evolution of the geo story in the Elastic Stack continues with the addition of a new geotile_grid aggregation in Elasticsearch to handle (geo) map tiles in a way that allows a user to zoom in and out on the map without altering the shape of the result data. Elastic Maps in 7.0 is already using this new aggregation. Prior to this change, the fringes of the shape could slightly change with the change in the zoom level because the rectangular tiles would change orientation at different zoom levels. This level of accuracy is important, whether the user is protecting a network from attackers, investigating slow application response times in specific locations, or tracking a relative hiking the Pacific Crest Trail.
Whether it’s infrastructure metrics, system audit logs, network traffic, or a rover on Mars, time series data is central to how many people use the Elastic Stack. The ability to precisely order and correlate events across multiple systems and services is key. Until now, Elasticsearch only stored timestamps with millisecond precision. 7.0 adds a few zeroes, bringing this to nanosecond precision, which gives users with high-frequency data collection needs the precision required to accurately store and sequence this data. The change was made possible by migrating from the historical JODA library to the official Java time API in JDK 8.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...