What’s New in the Elasticsearch 9.x Documentation?

1. Documentation URL Changed

In the 8.x era the official docs were hosted under elastic.co/guide (e.g., https://www.elastic.co/guide/en/elasticsearch/reference/8.19/). Starting with 9.x they have been migrated to elastic.co/docs (e.g., https://www.elastic.co/docs/9.x). Older versions (≤8.19) remain on the guide path.

2. No Longer Version‑Segmented Documentation

Previously each minor version (8.0, 8.1, 8.2, …) had its own separate set of docs. In 9.x a single documentation set covers all 9.0, 9.1, 9.2, etc., with availability badges indicating which features were added or changed in each sub‑version.

The new approach lets you see at a glance which features belong to 9.1, 9.2, etc., eliminating the need to jump between multiple version‑specific pages.

3. Documentation Organization Logic Changed

Earlier the docs were grouped by product (Elasticsearch Guide, Kibana Guide, Logstash Guide). The new structure groups content by the problem you want to solve – search, observability, security, or data lifecycle – and provides direct links for each scenario.

Elasticsearch Guide → Search and RAG applications

Kibana Guide → Observability

Logstash Guide → Threat detection and response

Data management → Manage your data throughout its lifecycle

4. Release Notes Separated

In 8.x the release notes were embedded in the Installation and Upgrade Guide. In 9.x they have been moved to a dedicated location at elastic.co/docs/release-notes, consolidating Elasticsearch, Kibana, Security, and Observability notes in one place.

5. API Documentation Path Includes Version

Old API URLs were of the form elastic.co/docs/api/doc/elasticsearch/operation/…. The new URLs insert the major version, e.g., elastic.co/docs/api/doc/elasticsearch/v9/operation/…, allowing multiple major‑version APIs to coexist without confusion.

6. What’s New in 9.x?

New navigation for client libraries (Java, Python, .Net) and query languages (ES|QL, KQL) with dedicated entry points. A dedicated “Versioning and Availability” guide explains version control and feature availability.

7. Author’s Recommendations

Immediately update your bookmarks from elastic.co/guide to elastic.co/docs.

Adopt the new “solution‑first” search approach instead of thinking “I need the Elasticsearch docs”.

Pay attention to the inline version badges to verify feature availability for your version.

If you still run an 8.x project, the old guide path still works, but plan migration according to your business needs.

8. One‑Sentence Summary

Elastic has transformed the documentation from product manuals into solution‑oriented guides, making it faster to find relevant information and boosting development efficiency for 9.x users.