From c70c2d5b341a910ceca41dc3ce082ae4c08cf65c Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:16:18 +0000 Subject: [PATCH 01/35] Move Elasticsearch solution files to new directory MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Move ES solution-specific files from /solutions/search/ to /solutions/elasticsearch-solution-project/: - Agent Builder and subdirectory - Playground files (from rag/ to top level) - Search Applications - MCP - AI Assistant - Query Rules UI - Synonyms UI pages - Get started directory These UI affordances are exclusive to the Elasticsearch solution/project type. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../agent-builder/_snippets/spaces-api-note.md | 0 .../agent-builder/a2a-server.md | 0 .../agent-builder/agent-builder-agents.md | 0 .../agent-builder/chat.md | 0 .../agent-builder/get-started.md | 0 .../images/agent-builder-agent-selector.png | Bin .../images/agent-builder-chat-UI-get-started.png | Bin .../images/agent-builder-chat-history.png | Bin .../images/agent-builder-chat-input.png | Bin .../agent-builder/images/chat-and-clone-buttons.png | Bin .../agent-builder/images/chat-edit-clone-delete.png | Bin .../images/copy-mcp-server-url-button.png | Bin .../agent-builder/images/create-esql-tool-query.png | Bin .../agent-builder/images/new-agent-button.png | Bin .../agent-builder/images/new-tool-button.png | Bin .../agent-builder/images/save-and-chat-buttons.png | Bin .../agent-builder/images/test-icon.png | Bin .../images/tool-save-save-and-test-buttons.png | Bin .../agent-builder/images/tools-overview.png | Bin .../agent-builder/kibana-api.md | 0 .../agent-builder/limitations-known-issues.md | 0 .../agent-builder/mcp-server.md | 0 .../agent-builder/models.md | 0 .../agent-builder/permissions.md | 0 .../agent-builder/programmatic-access.md | 0 .../agent-builder/tools.md | 0 .../agent-builder/tools/esql-tools.md | 0 .../agent-builder/tools/index-search-tools.md | 0 .../ai-assistant.md | 0 .../elastic-agent-builder.md | 0 .../full-text/create-update-synonyms-api-example.md | 0 .../full-text/search-with-synonyms.md | 0 .../get-started.md | 0 .../get-started/index-basics.md | 0 .../get-started/keyword-search-python.md | 0 .../get-started/quickstarts.md | 6 +++--- .../get-started/semantic-search.md | 0 .../mcp.md | 0 .../playground-context.md | 0 .../playground-query.md | 0 .../playground-troubleshooting.md | 0 .../playground.md | 0 .../query-rules-ui.md | 0 .../search-applications.md | 0 .../search-applications/search-application-api.md | 0 .../search-application-client.md | 0 .../search-application-security.md | 0 47 files changed, 3 insertions(+), 3 deletions(-) rename solutions/{search => elasticsearch-solution-project}/agent-builder/_snippets/spaces-api-note.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/a2a-server.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/agent-builder-agents.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/chat.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/get-started.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/agent-builder-agent-selector.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/agent-builder-chat-UI-get-started.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/agent-builder-chat-history.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/agent-builder-chat-input.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/chat-and-clone-buttons.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/chat-edit-clone-delete.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/copy-mcp-server-url-button.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/create-esql-tool-query.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/new-agent-button.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/new-tool-button.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/save-and-chat-buttons.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/test-icon.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/tool-save-save-and-test-buttons.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/images/tools-overview.png (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/kibana-api.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/limitations-known-issues.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/mcp-server.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/models.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/permissions.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/programmatic-access.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/tools.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/tools/esql-tools.md (100%) rename solutions/{search => elasticsearch-solution-project}/agent-builder/tools/index-search-tools.md (100%) rename solutions/{search => elasticsearch-solution-project}/ai-assistant.md (100%) rename solutions/{search => elasticsearch-solution-project}/elastic-agent-builder.md (100%) rename solutions/{search => elasticsearch-solution-project}/full-text/create-update-synonyms-api-example.md (100%) rename solutions/{search => elasticsearch-solution-project}/full-text/search-with-synonyms.md (100%) rename solutions/{search => elasticsearch-solution-project}/get-started.md (100%) rename solutions/{search => elasticsearch-solution-project}/get-started/index-basics.md (100%) rename solutions/{search => elasticsearch-solution-project}/get-started/keyword-search-python.md (100%) rename solutions/{search => elasticsearch-solution-project}/get-started/quickstarts.md (82%) rename solutions/{search => elasticsearch-solution-project}/get-started/semantic-search.md (100%) rename solutions/{search => elasticsearch-solution-project}/mcp.md (100%) rename solutions/{search/rag => elasticsearch-solution-project}/playground-context.md (100%) rename solutions/{search/rag => elasticsearch-solution-project}/playground-query.md (100%) rename solutions/{search/rag => elasticsearch-solution-project}/playground-troubleshooting.md (100%) rename solutions/{search/rag => elasticsearch-solution-project}/playground.md (100%) rename solutions/{search => elasticsearch-solution-project}/query-rules-ui.md (100%) rename solutions/{search => elasticsearch-solution-project}/search-applications.md (100%) rename solutions/{search => elasticsearch-solution-project}/search-applications/search-application-api.md (100%) rename solutions/{search => elasticsearch-solution-project}/search-applications/search-application-client.md (100%) rename solutions/{search => elasticsearch-solution-project}/search-applications/search-application-security.md (100%) diff --git a/solutions/search/agent-builder/_snippets/spaces-api-note.md b/solutions/elasticsearch-solution-project/agent-builder/_snippets/spaces-api-note.md similarity index 100% rename from solutions/search/agent-builder/_snippets/spaces-api-note.md rename to solutions/elasticsearch-solution-project/agent-builder/_snippets/spaces-api-note.md diff --git a/solutions/search/agent-builder/a2a-server.md b/solutions/elasticsearch-solution-project/agent-builder/a2a-server.md similarity index 100% rename from solutions/search/agent-builder/a2a-server.md rename to solutions/elasticsearch-solution-project/agent-builder/a2a-server.md diff --git a/solutions/search/agent-builder/agent-builder-agents.md b/solutions/elasticsearch-solution-project/agent-builder/agent-builder-agents.md similarity index 100% rename from solutions/search/agent-builder/agent-builder-agents.md rename to solutions/elasticsearch-solution-project/agent-builder/agent-builder-agents.md diff --git a/solutions/search/agent-builder/chat.md b/solutions/elasticsearch-solution-project/agent-builder/chat.md similarity index 100% rename from solutions/search/agent-builder/chat.md rename to solutions/elasticsearch-solution-project/agent-builder/chat.md diff --git a/solutions/search/agent-builder/get-started.md b/solutions/elasticsearch-solution-project/agent-builder/get-started.md similarity index 100% rename from solutions/search/agent-builder/get-started.md rename to solutions/elasticsearch-solution-project/agent-builder/get-started.md diff --git a/solutions/search/agent-builder/images/agent-builder-agent-selector.png b/solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-agent-selector.png similarity index 100% rename from solutions/search/agent-builder/images/agent-builder-agent-selector.png rename to solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-agent-selector.png diff --git a/solutions/search/agent-builder/images/agent-builder-chat-UI-get-started.png b/solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-chat-UI-get-started.png similarity index 100% rename from solutions/search/agent-builder/images/agent-builder-chat-UI-get-started.png rename to solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-chat-UI-get-started.png diff --git a/solutions/search/agent-builder/images/agent-builder-chat-history.png b/solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-chat-history.png similarity index 100% rename from solutions/search/agent-builder/images/agent-builder-chat-history.png rename to solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-chat-history.png diff --git a/solutions/search/agent-builder/images/agent-builder-chat-input.png b/solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-chat-input.png similarity index 100% rename from solutions/search/agent-builder/images/agent-builder-chat-input.png rename to solutions/elasticsearch-solution-project/agent-builder/images/agent-builder-chat-input.png diff --git a/solutions/search/agent-builder/images/chat-and-clone-buttons.png b/solutions/elasticsearch-solution-project/agent-builder/images/chat-and-clone-buttons.png similarity index 100% rename from solutions/search/agent-builder/images/chat-and-clone-buttons.png rename to solutions/elasticsearch-solution-project/agent-builder/images/chat-and-clone-buttons.png diff --git a/solutions/search/agent-builder/images/chat-edit-clone-delete.png b/solutions/elasticsearch-solution-project/agent-builder/images/chat-edit-clone-delete.png similarity index 100% rename from solutions/search/agent-builder/images/chat-edit-clone-delete.png rename to solutions/elasticsearch-solution-project/agent-builder/images/chat-edit-clone-delete.png diff --git a/solutions/search/agent-builder/images/copy-mcp-server-url-button.png b/solutions/elasticsearch-solution-project/agent-builder/images/copy-mcp-server-url-button.png similarity index 100% rename from solutions/search/agent-builder/images/copy-mcp-server-url-button.png rename to solutions/elasticsearch-solution-project/agent-builder/images/copy-mcp-server-url-button.png diff --git a/solutions/search/agent-builder/images/create-esql-tool-query.png b/solutions/elasticsearch-solution-project/agent-builder/images/create-esql-tool-query.png similarity index 100% rename from solutions/search/agent-builder/images/create-esql-tool-query.png rename to solutions/elasticsearch-solution-project/agent-builder/images/create-esql-tool-query.png diff --git a/solutions/search/agent-builder/images/new-agent-button.png b/solutions/elasticsearch-solution-project/agent-builder/images/new-agent-button.png similarity index 100% rename from solutions/search/agent-builder/images/new-agent-button.png rename to solutions/elasticsearch-solution-project/agent-builder/images/new-agent-button.png diff --git a/solutions/search/agent-builder/images/new-tool-button.png b/solutions/elasticsearch-solution-project/agent-builder/images/new-tool-button.png similarity index 100% rename from solutions/search/agent-builder/images/new-tool-button.png rename to solutions/elasticsearch-solution-project/agent-builder/images/new-tool-button.png diff --git a/solutions/search/agent-builder/images/save-and-chat-buttons.png b/solutions/elasticsearch-solution-project/agent-builder/images/save-and-chat-buttons.png similarity index 100% rename from solutions/search/agent-builder/images/save-and-chat-buttons.png rename to solutions/elasticsearch-solution-project/agent-builder/images/save-and-chat-buttons.png diff --git a/solutions/search/agent-builder/images/test-icon.png b/solutions/elasticsearch-solution-project/agent-builder/images/test-icon.png similarity index 100% rename from solutions/search/agent-builder/images/test-icon.png rename to solutions/elasticsearch-solution-project/agent-builder/images/test-icon.png diff --git a/solutions/search/agent-builder/images/tool-save-save-and-test-buttons.png b/solutions/elasticsearch-solution-project/agent-builder/images/tool-save-save-and-test-buttons.png similarity index 100% rename from solutions/search/agent-builder/images/tool-save-save-and-test-buttons.png rename to solutions/elasticsearch-solution-project/agent-builder/images/tool-save-save-and-test-buttons.png diff --git a/solutions/search/agent-builder/images/tools-overview.png b/solutions/elasticsearch-solution-project/agent-builder/images/tools-overview.png similarity index 100% rename from solutions/search/agent-builder/images/tools-overview.png rename to solutions/elasticsearch-solution-project/agent-builder/images/tools-overview.png diff --git a/solutions/search/agent-builder/kibana-api.md b/solutions/elasticsearch-solution-project/agent-builder/kibana-api.md similarity index 100% rename from solutions/search/agent-builder/kibana-api.md rename to solutions/elasticsearch-solution-project/agent-builder/kibana-api.md diff --git a/solutions/search/agent-builder/limitations-known-issues.md b/solutions/elasticsearch-solution-project/agent-builder/limitations-known-issues.md similarity index 100% rename from solutions/search/agent-builder/limitations-known-issues.md rename to solutions/elasticsearch-solution-project/agent-builder/limitations-known-issues.md diff --git a/solutions/search/agent-builder/mcp-server.md b/solutions/elasticsearch-solution-project/agent-builder/mcp-server.md similarity index 100% rename from solutions/search/agent-builder/mcp-server.md rename to solutions/elasticsearch-solution-project/agent-builder/mcp-server.md diff --git a/solutions/search/agent-builder/models.md b/solutions/elasticsearch-solution-project/agent-builder/models.md similarity index 100% rename from solutions/search/agent-builder/models.md rename to solutions/elasticsearch-solution-project/agent-builder/models.md diff --git a/solutions/search/agent-builder/permissions.md b/solutions/elasticsearch-solution-project/agent-builder/permissions.md similarity index 100% rename from solutions/search/agent-builder/permissions.md rename to solutions/elasticsearch-solution-project/agent-builder/permissions.md diff --git a/solutions/search/agent-builder/programmatic-access.md b/solutions/elasticsearch-solution-project/agent-builder/programmatic-access.md similarity index 100% rename from solutions/search/agent-builder/programmatic-access.md rename to solutions/elasticsearch-solution-project/agent-builder/programmatic-access.md diff --git a/solutions/search/agent-builder/tools.md b/solutions/elasticsearch-solution-project/agent-builder/tools.md similarity index 100% rename from solutions/search/agent-builder/tools.md rename to solutions/elasticsearch-solution-project/agent-builder/tools.md diff --git a/solutions/search/agent-builder/tools/esql-tools.md b/solutions/elasticsearch-solution-project/agent-builder/tools/esql-tools.md similarity index 100% rename from solutions/search/agent-builder/tools/esql-tools.md rename to solutions/elasticsearch-solution-project/agent-builder/tools/esql-tools.md diff --git a/solutions/search/agent-builder/tools/index-search-tools.md b/solutions/elasticsearch-solution-project/agent-builder/tools/index-search-tools.md similarity index 100% rename from solutions/search/agent-builder/tools/index-search-tools.md rename to solutions/elasticsearch-solution-project/agent-builder/tools/index-search-tools.md diff --git a/solutions/search/ai-assistant.md b/solutions/elasticsearch-solution-project/ai-assistant.md similarity index 100% rename from solutions/search/ai-assistant.md rename to solutions/elasticsearch-solution-project/ai-assistant.md diff --git a/solutions/search/elastic-agent-builder.md b/solutions/elasticsearch-solution-project/elastic-agent-builder.md similarity index 100% rename from solutions/search/elastic-agent-builder.md rename to solutions/elasticsearch-solution-project/elastic-agent-builder.md diff --git a/solutions/search/full-text/create-update-synonyms-api-example.md b/solutions/elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md similarity index 100% rename from solutions/search/full-text/create-update-synonyms-api-example.md rename to solutions/elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md diff --git a/solutions/search/full-text/search-with-synonyms.md b/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md similarity index 100% rename from solutions/search/full-text/search-with-synonyms.md rename to solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md diff --git a/solutions/search/get-started.md b/solutions/elasticsearch-solution-project/get-started.md similarity index 100% rename from solutions/search/get-started.md rename to solutions/elasticsearch-solution-project/get-started.md diff --git a/solutions/search/get-started/index-basics.md b/solutions/elasticsearch-solution-project/get-started/index-basics.md similarity index 100% rename from solutions/search/get-started/index-basics.md rename to solutions/elasticsearch-solution-project/get-started/index-basics.md diff --git a/solutions/search/get-started/keyword-search-python.md b/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md similarity index 100% rename from solutions/search/get-started/keyword-search-python.md rename to solutions/elasticsearch-solution-project/get-started/keyword-search-python.md diff --git a/solutions/search/get-started/quickstarts.md b/solutions/elasticsearch-solution-project/get-started/quickstarts.md similarity index 82% rename from solutions/search/get-started/quickstarts.md rename to solutions/elasticsearch-solution-project/get-started/quickstarts.md index 3315a38e17..98059510b5 100644 --- a/solutions/search/get-started/quickstarts.md +++ b/solutions/elasticsearch-solution-project/get-started/quickstarts.md @@ -18,9 +18,9 @@ Each quickstart provides: Follow the steps in these guides to get started quickly: -- [](/solutions/search/get-started/index-basics.md) -- [](/solutions/search/get-started/keyword-search-python.md) -- [](/solutions/search/get-started/semantic-search.md) +- [](/solutions/elasticsearch-solution-project/get-started/index-basics.md) +- [](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md) +- [](/solutions/elasticsearch-solution-project/get-started/semantic-search.md) ## Related resources diff --git a/solutions/search/get-started/semantic-search.md b/solutions/elasticsearch-solution-project/get-started/semantic-search.md similarity index 100% rename from solutions/search/get-started/semantic-search.md rename to solutions/elasticsearch-solution-project/get-started/semantic-search.md diff --git a/solutions/search/mcp.md b/solutions/elasticsearch-solution-project/mcp.md similarity index 100% rename from solutions/search/mcp.md rename to solutions/elasticsearch-solution-project/mcp.md diff --git a/solutions/search/rag/playground-context.md b/solutions/elasticsearch-solution-project/playground-context.md similarity index 100% rename from solutions/search/rag/playground-context.md rename to solutions/elasticsearch-solution-project/playground-context.md diff --git a/solutions/search/rag/playground-query.md b/solutions/elasticsearch-solution-project/playground-query.md similarity index 100% rename from solutions/search/rag/playground-query.md rename to solutions/elasticsearch-solution-project/playground-query.md diff --git a/solutions/search/rag/playground-troubleshooting.md b/solutions/elasticsearch-solution-project/playground-troubleshooting.md similarity index 100% rename from solutions/search/rag/playground-troubleshooting.md rename to solutions/elasticsearch-solution-project/playground-troubleshooting.md diff --git a/solutions/search/rag/playground.md b/solutions/elasticsearch-solution-project/playground.md similarity index 100% rename from solutions/search/rag/playground.md rename to solutions/elasticsearch-solution-project/playground.md diff --git a/solutions/search/query-rules-ui.md b/solutions/elasticsearch-solution-project/query-rules-ui.md similarity index 100% rename from solutions/search/query-rules-ui.md rename to solutions/elasticsearch-solution-project/query-rules-ui.md diff --git a/solutions/search/search-applications.md b/solutions/elasticsearch-solution-project/search-applications.md similarity index 100% rename from solutions/search/search-applications.md rename to solutions/elasticsearch-solution-project/search-applications.md diff --git a/solutions/search/search-applications/search-application-api.md b/solutions/elasticsearch-solution-project/search-applications/search-application-api.md similarity index 100% rename from solutions/search/search-applications/search-application-api.md rename to solutions/elasticsearch-solution-project/search-applications/search-application-api.md diff --git a/solutions/search/search-applications/search-application-client.md b/solutions/elasticsearch-solution-project/search-applications/search-application-client.md similarity index 100% rename from solutions/search/search-applications/search-application-client.md rename to solutions/elasticsearch-solution-project/search-applications/search-application-client.md diff --git a/solutions/search/search-applications/search-application-security.md b/solutions/elasticsearch-solution-project/search-applications/search-application-security.md similarity index 100% rename from solutions/search/search-applications/search-application-security.md rename to solutions/elasticsearch-solution-project/search-applications/search-application-security.md From ef803d93e07e848e4c12ea688fac888f64f8d767 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:16:57 +0000 Subject: [PATCH 02/35] Add Elasticsearch solution and Search use case overview pages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Create new structure separating ES solution from Search use case: - elasticsearch-solution-project.md: Overview of ES solution UI tools - elasticsearch-solution-project/get-started.md: ES solution getting started - search/get-started.md: Universal, deployment-agnostic search getting started The Elasticsearch solution provides exclusive UI affordances (Agent Builder, Playground, Search Applications UI, etc.) while the Search use case covers universal Elasticsearch primitives available across all deployments. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- solutions/elasticsearch-solution-project.md | 77 +++++++++++++++++++++ solutions/search/get-started.md | 55 +++++++++++++++ 2 files changed, 132 insertions(+) create mode 100644 solutions/elasticsearch-solution-project.md create mode 100644 solutions/search/get-started.md diff --git a/solutions/elasticsearch-solution-project.md b/solutions/elasticsearch-solution-project.md new file mode 100644 index 0000000000..af0016b2aa --- /dev/null +++ b/solutions/elasticsearch-solution-project.md @@ -0,0 +1,77 @@ +--- +mapped_pages: + - https://www.elastic.co/guide/en/serverless/current/what-is-elasticsearch-serverless.html + - https://www.elastic.co/guide/en/kibana/current/search-space.html +applies_to: + stack: + serverless: +products: + - id: elasticsearch + - id: cloud-serverless + - id: kibana +navigation_title: Elasticsearch +--- + +# {{es}} solution overview + +The {{es}} solution and serverless project type provide specialized UI tools and interfaces that help you build search applications on top of the {{es}} platform. + +These UI affordances are exclusive to the {{es}} solution (on {{ech}}) and the {{es}} serverless project type. They complement the universal search capabilities available across all {{es}} deployments. + +::::{tip} +Looking for general search capabilities that work across all {{es}} deployments? Check out the [Search use case](/solutions/search.md) documentation, which covers universal {{es}} search primitives including full-text search, vector search, semantic search, and hybrid search. +:::: + +## Features and tools + +The {{es}} solution provides the following specialized UI tools: + +### Agent Builder + +[Agent Builder](/solutions/elasticsearch-solution-project/elastic-agent-builder.md) enables you to create AI agents that can interact with your {{es}} data, execute queries, and provide intelligent responses. It provides a complete framework for building conversational AI experiences on top of your search infrastructure. + +### Playground + +[Playground](/solutions/elasticsearch-solution-project/playground.md) lets you use large language models (LLMs) to understand, explore, and analyze your {{es}} data using retrieval augmented generation (RAG), via a chat interface. Playground is also useful for testing and debugging your {{es}} queries using the [retrievers](/solutions/search/retrievers-overview.md) syntax. + +### Search Applications + +[Search Applications](/solutions/elasticsearch-solution-project/search-applications.md) provide a simplified way to manage and access your search use cases through a unified interface. They enable you to create, configure, and manage search-powered applications with built-in templates and best practices. + +### Synonyms UI + +The [Search with synonyms](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md) interface provides a dedicated UI for managing synonym sets directly within {{kib}}, making it easier to improve search relevance without editing configuration files. + +### Query Rules UI + +[Query Rules UI](/solutions/elasticsearch-solution-project/query-rules-ui.md) enables you to create and manage query rules that modify search behavior based on specific conditions, helping you deliver more relevant results for common queries. + +### AI Assistant + +The [AI Assistant](/solutions/elasticsearch-solution-project/ai-assistant.md) provides intelligent assistance and insights across the Elastic platform, helping you understand your data and workflows more effectively. + +### Model Context Protocol (MCP) + +The [Model Context Protocol (MCP)](/solutions/elasticsearch-solution-project/mcp.md) lets you connect AI agents and assistants to your {{es}} data to enable natural language interactions with your indices. + +## Get started + +Ready to start using the {{es}} solution? Refer to [Get started](/solutions/elasticsearch-solution-project/get-started.md) for setup instructions and quickstart guides. + +For a deeper understanding of search concepts and techniques, refer to the [Search use case](/solutions/search.md) documentation. + +## Related reference + +* [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) +* [Content connectors](elasticsearch://reference/search-connectors/index.md) +* [{{es}} API documentation]({{es-apis}}) +* [Search use case documentation](/solutions/search.md) + +::::{tip} +Not sure whether {{es}} on {{serverless-full}} is the right deployment choice for you? + +Check out the following resources to help you decide: + +- [What's different?](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md): Understand the differences between {{serverless-full}} and other deployment types. +- [Billing](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md): Learn about the billing model for {{es}} on {{serverless-full}}. +:::: diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md new file mode 100644 index 0000000000..55ae6f067b --- /dev/null +++ b/solutions/search/get-started.md @@ -0,0 +1,55 @@ +--- +mapped_pages: + - https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started.html +applies_to: + stack: + serverless: +products: + - id: elasticsearch + - id: cloud-serverless +--- + +# Get started with search + +This guide helps you get started with search using {{es}}, regardless of your deployment type. Whether you're using a self-managed cluster, {{ech}}, or an {{es}} serverless project, these universal search capabilities are available to you. + +::::{tip} +Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for UI tools like Agent Builder, Playground, and Search Applications that complement these universal capabilities. +:::: + +## Before you begin + +To follow along with this guide, you'll need: + +- An {{es}} cluster or serverless project. [Create a deployment](/get-started/start-building.md) if you don't have one yet. +- Connection details for your cluster. Refer to [Connection details](/solutions/search/search-connection-details.md) for more information. + +## Quickstarts + +Choose a quickstart based on your use case: + +- [**Index basics**](/solutions/search/get-started/index-basics.md): Learn how to create indices, add documents, and perform basic searches using the {{es}} APIs. +- [**Keyword search with Python**](/solutions/search/get-started/keyword-search-python.md): Build a keyword search application using the Python client. +- [**Semantic search**](/solutions/search/get-started/semantic-search.md): Implement semantic search using vector embeddings. + +## Explore search approaches + +Once you're comfortable with the basics, explore different search techniques: + +- [**Full-text search**](/solutions/search/full-text.md): Traditional text-based search with analysis and scoring. +- [**Vector search**](/solutions/search/vector.md): Similarity search using dense or sparse vectors. +- [**Semantic search**](/solutions/search/semantic-search.md): Context-aware search using machine learning models. +- [**Hybrid search**](/solutions/search/hybrid-search.md): Combine multiple search techniques for better results. + +## Next steps + +- Learn about [ingestion and data preparation](/solutions/search/ingest-for-search.md) +- Explore [querying options](/solutions/search/querying-for-search.md) including Query DSL, {{esql}}, and retrievers +- Understand [ranking and relevance](/solutions/search/ranking.md) to improve search quality +- Build [RAG (Retrieval Augmented Generation)](/solutions/search/rag.md) applications + +## Related resources + +- [{{es}} API documentation]({{es-apis}}) +- [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) +- [Query languages](/explore-analyze/query-filter/languages/index.md) From 597e532afe9a58c7b795cd118989989d8a1696e1 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:17:22 +0000 Subject: [PATCH 03/35] Update Search pages to reference Elasticsearch solution MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Update existing Search use case pages with cross-references to ES solution: - search.md: Update to "Search use case" focus, add cross-link to ES solution - search/rag.md: Update Playground references to point to ES solution location - search/apis-and-tools.md: Update generative AI tool links (Agent Builder, Playground, MCP) to new ES solution paths These updates clarify that UI tools are part of the Elasticsearch solution while universal search primitives remain in the Search use case. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- solutions/search.md | 18 +++++++++--------- solutions/search/apis-and-tools.md | 10 +++++++--- solutions/search/rag.md | 4 +++- 3 files changed, 19 insertions(+), 13 deletions(-) diff --git a/solutions/search.md b/solutions/search.md index 500e5d7a21..e4740323ea 100644 --- a/solutions/search.md +++ b/solutions/search.md @@ -1,24 +1,24 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/search-with-elasticsearch.html - - https://www.elastic.co/guide/en/serverless/current/what-is-elasticsearch-serverless.html - - https://www.elastic.co/guide/en/kibana/current/search-space.html applies_to: stack: serverless: products: - id: elasticsearch - id: cloud-serverless - - id: kibana -navigation_title: Elasticsearch +navigation_title: Search use case --- -# Elasticsearch solution overview +# Search use case -The {{es}} solution and serverless project type enable you to build your own applications on top of the {{es}} platform's scalable data store, search engine, and vector database capabilities. +Build powerful search experiences using {{es}}'s universal search capabilities. Whether you're running a self-managed cluster, {{ech}}, or an {{es}} serverless project, these search primitives are available across all deployment types. -{{es}} is a distributed datastore that can ingest, index, and manage various types of data in near real-time, making them both searchable and analyzable. -With specialized user interfaces and tools, it provides the flexibility to create, deploy, and run a wide range of applications, from search to analytics to AI-driven solutions. +{{es}} is a distributed datastore that can ingest, index, and manage various types of data in near real-time, making them both searchable and analyzable. This documentation covers the core search capabilities and techniques that work universally across all {{es}} deployments. + +::::{tip} +Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for exclusive UI tools like Agent Builder, Playground, and Search Applications that complement these universal search capabilities. +:::: ## Use cases @@ -34,7 +34,7 @@ Here are a few common real-world applications: | **Chatbots/RAG** | Enable natural conversations, provide context, maintain knowledge | Vector search, ML models, knowledge base integration | | **Geospatial search** | Process location queries, sort by proximity, filter by area | Geo-mapping, spatial indexing, distance calculations | -If you're new to {{es}} and want to try out some simple search use cases, go to [](/solutions/search/get-started.md) and [](/solutions/search/get-started/quickstarts.md). +If you're new to {{es}} and want to try out some simple search use cases, refer to [Get started with search](/solutions/search/get-started.md). ## Core concepts [search-concepts] diff --git a/solutions/search/apis-and-tools.md b/solutions/search/apis-and-tools.md index aa7ee1d26e..c9add58227 100644 --- a/solutions/search/apis-and-tools.md +++ b/solutions/search/apis-and-tools.md @@ -74,14 +74,18 @@ The accompanying [GitHub repository](https://www.github.com/elastic/elasticsearc ## Generative AI tools +The following generative AI tools are available as part of the {{es}} solution and serverless project type: + ### Agent Builder -[Agent Builder](elastic-agent-builder.md) enables you to create AI agents that can interact with your Elasticsearch data, execute queries, and provide intelligent responses. It provides a complete framework for building conversational AI experiences on top of your search infrastructure. +[Agent Builder](/solutions/elasticsearch-solution-project/elastic-agent-builder.md) enables you to create AI agents that can interact with your {{es}} data, execute queries, and provide intelligent responses. It provides a complete framework for building conversational AI experiences on top of your search infrastructure. ### Playground -[Playground](rag/playground.md) enables you to use large language models (LLMs) to understand, explore, and analyze your {{es}} data using retrieval augmented generation (RAG), via a chat interface. Playground is also very useful for testing and debugging your {{es}} queries, using the [retrievers](retrievers-overview.md) syntax with the `_search` endpoint. +[Playground](/solutions/elasticsearch-solution-project/playground.md) enables you to use large language models (LLMs) to understand, explore, and analyze your {{es}} data using retrieval augmented generation (RAG), via a chat interface. Playground is also useful for testing and debugging your {{es}} queries using the [retrievers](retrievers-overview.md) syntax with the `_search` endpoint. ### Model Context Protocol (MCP) -The [Model Context Protocol (MCP)](mcp.md) lets you connect AI agents and assistants to your {{es}} data to enable natural language interactions with your indices. \ No newline at end of file +The [Model Context Protocol (MCP)](/solutions/elasticsearch-solution-project/mcp.md) lets you connect AI agents and assistants to your {{es}} data to enable natural language interactions with your indices. + +Refer to the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for more information about these UI tools. \ No newline at end of file diff --git a/solutions/search/rag.md b/solutions/search/rag.md index c8f2c3e9bf..d07ec070a5 100644 --- a/solutions/search/rag.md +++ b/solutions/search/rag.md @@ -68,7 +68,9 @@ Start building RAG applications quickly with Playground, which seamlessly integr Playground automatically selects the best retrieval methods for your data, while providing full control over the final {{es}} queries and language model instructions. You can also download the underlying Python code to integrate with your existing applications. -Learn more in the [Playground documentation](rag/playground.md) and try the [interactive lab](https://www.elastic.co/demo-gallery/ai-playground) for hands-on experience. +::::{note} +Playground is available as part of the {{es}} solution and serverless project type. Learn more in the [Playground documentation](/solutions/elasticsearch-solution-project/playground.md) and try the [interactive lab](https://www.elastic.co/demo-gallery/ai-playground) for hands-on experience. +:::: ## Learn more [rag-elasticsearch-learn-more] From 45e407b7b5087d5c3cc9226df6abb24ebb07872c Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:17:50 +0000 Subject: [PATCH 04/35] Update ES solution get-started page with new content MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace generic ES getting started content with ES solution-specific guide that focuses on UI tools and cross-links to universal search concepts. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../get-started.md | 94 ++++++++----------- 1 file changed, 39 insertions(+), 55 deletions(-) diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index 42148a7a0c..18c19d11e0 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -1,88 +1,72 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started.html - - https://www.elastic.co/guide/en/serverless/current/elasticsearch-get-started.html + - https://www.elastic.co/guide/en/serverless/current/elasticsearch-getting-started.html applies_to: stack: serverless: - elasticsearch: all products: - id: elasticsearch - id: cloud-serverless -navigation_title: Get started -description: To try out an {{es}} project or solution, pick your deployment type, search goals, and ingestion method. + - id: kibana --- -# Get started with {{es}} +# Get started with the {{es}} solution -New to {{es}}? Start building a search experience by setting up your first deployment, refining your search goals, and adding data. +This guide helps you get started with the {{es}} solution and serverless project type, including the specialized UI tools and interfaces available exclusively in this environment. -:::{note} -If you're looking for an introduction to the {{stack}} or the {{es}} product, go to [](/get-started/index.md) or [](/manage-data/data-store.md). -::: +::::{tip} +New to {{es}} search capabilities? Start with the [Search use case documentation](/solutions/search.md) to learn about universal {{es}} search primitives like full-text search, vector search, and hybrid search that work across all deployment types. +:::: -::::::{stepper} -:::::{step} Choose your deployment type +## Before you begin -Elastic provides several self-managed and Elastic-managed options. -For simplicity and speed, try out {{es-serverless}}: +To use the {{es}} solution, you'll need: -::::{dropdown} Create an {{es-serverless}} project -:::{include} /deploy-manage/deploy/_snippets/create-serverless-project-intro.md -::: +- An {{es}} solution deployment on {{ech}} or an {{es}} serverless project +- Access to {{kib}} for using the UI tools +- Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. -Choose the {{es}} project type and provide a name. -You can optionally edit the project settings, such as the [region](/deploy-manage/deploy/elastic-cloud/regions.md). +## Quickstarts -When your project is created, you're ready to move on to the next step and to start creating indices, adding data, and performing searches. -:::: +Get hands-on experience with {{es}} using these guided tutorials: -Alternatively, create a [local development installation](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md) in Docker: +- [**Index basics**](/solutions/elasticsearch-solution-project/get-started/index-basics.md): Learn how to create indices, add documents, and perform searches. +- [**Keyword search with Python**](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md): Build a keyword search application. +- [**Semantic search**](/solutions/elasticsearch-solution-project/get-started/semantic-search.md): Implement semantic search using embeddings. -```sh -curl -fsSL https://elastic.co/start-local | sh -``` +## Explore {{es}} solution features -Check out the full list of [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) to learn more. -::::: +The {{es}} solution provides specialized UI tools to enhance your search experience: -:::::{step} Identify your search goals -Depending on your use case, you can choose multiple [search approaches](search-approaches.md), for example full-text and semantic search. -Each approach affects your options for storing and querying your data. +### Agent Builder -If you're unsure which approaches match your goals, you can try them out with sample data. For example, [](/solutions/search/get-started/semantic-search.md). +Create AI agents that interact with your {{es}} data. Refer to [Agent Builder](/solutions/elasticsearch-solution-project/elastic-agent-builder.md) to get started. -If you prefer to ingest your data first and transform or reindex it as needed later, skip to the next step. -::::: -:::::{{step}} Ingest your data +### Playground -If your goals include vector or semantic AI-powered search, create vectorized data with built-in and third-party natural language processing (NLP) models and store it in an {{es}} vector database. -The approach that requires the least configuration involves adding `semantic_text` fields when ingesting your data. -This method is described in [](/solutions/search/semantic-search/semantic-search-semantic-text.md). +Test and explore RAG (Retrieval Augmented Generation) workflows using the interactive Playground interface. Refer to [Playground](/solutions/elasticsearch-solution-project/playground.md) to learn more. -To learn about adding data for other search goals, go to [](/solutions/search/ingest-for-search.md). -For a broader overview of ingestion options, go to [](/manage-data/ingest.md). +### Search Applications -If you're not ready to add your own data, you can use [sample data](/manage-data/ingest/sample-data.md) or create small data sets when you follow the instructions in the [quickstarts](/solutions/search/get-started/quickstarts.md). +Manage and deploy search-powered applications with pre-built templates. Refer to [Search Applications](/solutions/elasticsearch-solution-project/search-applications.md) for details. -The {{es}} home page in the UI also provides workflow guides for creating indices and ready-to-use code examples for ingesting data by using REST APIs. -::::: -:::::{{step}} Build your search queries +### UI tools for search optimization -Your next steps will be to choose a method to write queries and interact with {{es}}. -You can pick a programming language [client](/reference/elasticsearch-clients/index.md) that matches your application and choose which [query languages](/solutions/search/querying-for-search.md) you will use to express your search logic. -Each decision builds on the previous ones, offering flexibility to mix and match approaches based on your needs. +- [**Search with synonyms**](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md): Manage synonym sets through the UI +- [**Query Rules UI**](/solutions/elasticsearch-solution-project/query-rules-ui.md): Create rules to modify search behavior +- [**AI Assistant**](/solutions/elasticsearch-solution-project/ai-assistant.md): Get intelligent assistance across the platform -Not sure where to start exploring? -Get an introduction to [index and search basics](/solutions/search/get-started/index-basics.md) or [build your first search query with Python](/solutions/search/get-started/keyword-search-python.md). -::::: -:::::: +## Next steps -## Related resources +- Learn about [search techniques and approaches](/solutions/search/search-approaches.md) in the Search use case documentation +- Explore [RAG concepts](/solutions/search/rag.md) to understand how Playground leverages retrieval augmented generation +- Discover [ingestion methods](/solutions/search/ingest-for-search.md) for preparing your data +- Understand [ranking strategies](/solutions/search/ranking.md) to improve search relevance -Use these resources to learn more about {{es}} or get started in a different way: +## Related resources -- [](/deploy-manage/deploy/deployment-comparison.md) -- [Get started with Query DSL search and filters](elasticsearch://reference/query-languages/query-dsl/full-text-filter-tutorial.md) -- [Get started with ES|QL queries](elasticsearch://reference/query-languages/esql/esql-getting-started.md) -- [Analyze eCommerce data with aggregations using Query DSL](/explore-analyze/query-filter/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md) +- [{{es}} solution overview](/solutions/elasticsearch-solution-project.md) +- [Search use case documentation](/solutions/search.md) +- [{{es}} API documentation]({{es-apis}}) +- [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) From 6a5fb4b73fb0ab4df690c4baff7f146cfc7cf74d Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:19:39 +0000 Subject: [PATCH 05/35] Restructure navigation into Search use case and Elasticsearch solution MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Split the solutions navigation into two distinct top-level sections: 1. Search use case - Universal Elasticsearch search primitives covering: - Get started (deployment-agnostic) - Ingest for search - Search approaches (full-text, AI, vector, semantic, hybrid, ranking) - Querying methods - RAG concepts - Site/app building - Cross-cluster search - APIs and tools 2. Elasticsearch solution - UI affordances exclusive to ES solution/project: - Get started (ES solution-specific) - Agent Builder - Playground (moved from rag/ to top level) - MCP - Search Applications - Synonyms UI - Query Rules UI - AI Assistant This separation clarifies that the Search use case contains universal features available across all deployments, while the Elasticsearch solution provides exclusive UI tools for the ES solution/project type. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- solutions/toc.yml | 84 +++++++++++++++++++++++++---------------------- 1 file changed, 45 insertions(+), 39 deletions(-) diff --git a/solutions/toc.yml b/solutions/toc.yml index 3efa563111..e8584a6a7e 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -6,11 +6,9 @@ toc: - file: search/get-started.md children: - file: search/search-connection-details.md - - file: search/get-started/quickstarts.md - children: - - file: search/get-started/index-basics.md - - file: search/get-started/keyword-search-python.md - - file: search/get-started/semantic-search.md + - file: search/get-started/index-basics.md + - file: search/get-started/keyword-search-python.md + - file: search/get-started/semantic-search.md - file: search/ingest-for-search.md children: - file: search/search-pipelines.md @@ -19,9 +17,6 @@ toc: - file: search/full-text.md children: - file: search/full-text/how-full-text-works.md - - file: search/full-text/search-with-synonyms.md - children: - - file: search/full-text/create-update-synonyms-api-example.md - file: search/full-text/text-analysis-during-search.md - file: search/full-text/search-relevance.md children: @@ -62,46 +57,57 @@ toc: - file: search/esql-for-search.md - file: search/retrievers-overview.md - file: search/search-templates.md - - file: search/elastic-agent-builder.md - children: - - file: search/agent-builder/get-started.md - - file: search/agent-builder/models.md - - file: search/agent-builder/chat.md - - file: search/agent-builder/agent-builder-agents.md - - file: search/agent-builder/tools.md - children: - - file: search/agent-builder/tools/esql-tools.md - - file: search/agent-builder/tools/index-search-tools.md - - file: search/agent-builder/programmatic-access.md - children: - - file: search/agent-builder/kibana-api.md - - file: search/agent-builder/a2a-server.md - - file: search/agent-builder/mcp-server.md - - file: search/agent-builder/permissions.md - - file: search/agent-builder/limitations-known-issues.md - file: search/rag.md - children: - - file: search/rag/playground.md - children: - - file: search/rag/playground-context.md - - file: search/rag/playground-query.md - - file: search/rag/playground-troubleshooting.md - - file: search/mcp.md - file: search/site-or-app.md children: - file: search/site-or-app/clients.md - file: search/site-or-app/search-ui.md - - file: search/search-applications.md - children: - - file: search/search-applications/search-application-api.md - - file: search/search-applications/search-application-security.md - - file: search/search-applications/search-application-client.md - file: search/cross-cluster-search.md children: - file: search/using-resolve-cluster-endpoint-before-cross-cluster-search.md - file: search/apis-and-tools.md - - file: search/ai-assistant.md - - file: search/query-rules-ui.md + - file: elasticsearch-solution-project.md + children: + - file: elasticsearch-solution-project/get-started.md + children: + - file: elasticsearch-solution-project/get-started/quickstarts.md + children: + - file: elasticsearch-solution-project/get-started/index-basics.md + - file: elasticsearch-solution-project/get-started/keyword-search-python.md + - file: elasticsearch-solution-project/get-started/semantic-search.md + - file: elasticsearch-solution-project/elastic-agent-builder.md + children: + - file: elasticsearch-solution-project/agent-builder/get-started.md + - file: elasticsearch-solution-project/agent-builder/models.md + - file: elasticsearch-solution-project/agent-builder/chat.md + - file: elasticsearch-solution-project/agent-builder/agent-builder-agents.md + - file: elasticsearch-solution-project/agent-builder/tools.md + children: + - file: elasticsearch-solution-project/agent-builder/tools/esql-tools.md + - file: elasticsearch-solution-project/agent-builder/tools/index-search-tools.md + - file: elasticsearch-solution-project/agent-builder/programmatic-access.md + children: + - file: elasticsearch-solution-project/agent-builder/kibana-api.md + - file: elasticsearch-solution-project/agent-builder/a2a-server.md + - file: elasticsearch-solution-project/agent-builder/mcp-server.md + - file: elasticsearch-solution-project/agent-builder/permissions.md + - file: elasticsearch-solution-project/agent-builder/limitations-known-issues.md + - file: elasticsearch-solution-project/playground.md + children: + - file: elasticsearch-solution-project/playground-context.md + - file: elasticsearch-solution-project/playground-query.md + - file: elasticsearch-solution-project/playground-troubleshooting.md + - file: elasticsearch-solution-project/mcp.md + - file: elasticsearch-solution-project/search-applications.md + children: + - file: elasticsearch-solution-project/search-applications/search-application-api.md + - file: elasticsearch-solution-project/search-applications/search-application-security.md + - file: elasticsearch-solution-project/search-applications/search-application-client.md + - file: elasticsearch-solution-project/full-text/search-with-synonyms.md + children: + - file: elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md + - file: elasticsearch-solution-project/ai-assistant.md + - file: elasticsearch-solution-project/query-rules-ui.md - file: observability.md children: - file: observability/get-started.md From 2efdd52a7468b60eb84e2c6e2a4e35ecdeb72821 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:24:17 +0000 Subject: [PATCH 06/35] Fix toc.yml to remove non-existent quickstart references MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove references to quickstart files under search/get-started/ that were moved to elasticsearch-solution-project/get-started/. The search/get-started.md page already contains proper markdown links to these quickstarts in their new location. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- solutions/toc.yml | 3 --- 1 file changed, 3 deletions(-) diff --git a/solutions/toc.yml b/solutions/toc.yml index e8584a6a7e..9190206766 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -6,9 +6,6 @@ toc: - file: search/get-started.md children: - file: search/search-connection-details.md - - file: search/get-started/index-basics.md - - file: search/get-started/keyword-search-python.md - - file: search/get-started/semantic-search.md - file: search/ingest-for-search.md children: - file: search/search-pipelines.md From a561b33cbfe9ca973bdd7a759fa9d66b7b6cc7e4 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:26:17 +0000 Subject: [PATCH 07/35] Fix internal references and redirects after file moves MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix search-connection-details.md reference in ES solution get-started - Update redirects.yml to point to new file locations in elasticsearch-solution-project/get-started/ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- redirects.yml | 6 +++--- solutions/elasticsearch-solution-project/get-started.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/redirects.yml b/redirects.yml index a156c6266a..f824a66dfc 100644 --- a/redirects.yml +++ b/redirects.yml @@ -326,13 +326,13 @@ redirects: 'deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md': 'deploy-manage/monitor/autoops/ec-autoops-events.md' # Related to https://github.com/elastic/docs-content/pull/2245/ - 'solutions/search/elasticsearch-basics-quickstart.md': 'solutions/search/get-started/index-basics.md' + 'solutions/search/elasticsearch-basics-quickstart.md': 'solutions/elasticsearch-solution-project/get-started/index-basics.md' # Related to https://github.com/elastic/elasticsearch/pull/133362 'solutions/search/querydsl-full-text-filter-tutorial.md': 'elasticsearch://reference/query-languages/query-dsl/full-text-filter-tutorial.md' # Related to https://github.com/elastic/docs-content/pull/2719 - 'solutions/search/api-quickstarts.md': 'solutions/search/get-started/quickstarts.md' + 'solutions/search/api-quickstarts.md': 'solutions/elasticsearch-solution-project/get-started/quickstarts.md' # Related to https://github.com/elastic/docs-content/pull/2745 'solutions/search/run-elasticsearch-locally.md': 'deploy-manage/deploy/self-managed/local-development-installation-quickstart.md' @@ -355,7 +355,7 @@ redirects: 'troubleshoot/observability/apm-agent-swift/apm-ios-agent.md': 'troubleshoot/ingest/opentelemetry/edot-sdks/ios/index.md' # Related to https://github.com/elastic/docs-content/pull/2843 - 'solutions/search/serverless-elasticsearch-get-started.md': 'solutions/search/get-started.md' + 'solutions/search/serverless-elasticsearch-get-started.md': 'solutions/elasticsearch-solution-project/get-started.md' # Related to https://github.com/elastic/docs-content/pull/3032 'manage-data/lifecycle/index-lifecycle-management/tutorial-automate-rollover.md': 'manage-data/lifecycle/index-lifecycle-management/ilm-tutorials.md' diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index 18c19d11e0..d9d61f675c 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -25,7 +25,7 @@ To use the {{es}} solution, you'll need: - An {{es}} solution deployment on {{ech}} or an {{es}} serverless project - Access to {{kib}} for using the UI tools -- Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. +- Connection details for your cluster. Refer to [Connection details](/solutions/search/search-connection-details.md) for more information. ## Quickstarts From 31d7bfe24242134f78a09ab895c02491f2486a2d Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:33:03 +0000 Subject: [PATCH 08/35] Update all internal references to moved pages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix references to quickstart files (now in elasticsearch-solution-project/get-started/) - Fix references to elastic-agent-builder (now in elasticsearch-solution-project/) - Fix references to search-with-synonyms (now in elasticsearch-solution-project/full-text/) - Update cross-references between Search use case and ES solution pages - Convert absolute URLs to relative paths 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../local-development-installation-quickstart.md | 2 +- explore-analyze/ai-features.md | 2 +- explore-analyze/query-filter.md | 2 +- release-notes/elastic-cloud-serverless/index.md | 2 +- .../elasticsearch-solution-project/agent-builder/models.md | 2 +- .../get-started/index-basics.md | 2 +- solutions/elasticsearch-solution-project/mcp.md | 2 +- solutions/search/esql-for-search.md | 2 +- solutions/search/get-started.md | 6 +++--- solutions/search/querying-for-search.md | 2 +- 10 files changed, 12 insertions(+), 12 deletions(-) diff --git a/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md b/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md index 8fd511d474..b237c799d7 100644 --- a/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md +++ b/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md @@ -49,4 +49,4 @@ For more detailed information about the `start-local` setup, refer to the [READM ## Next steps [local-dev-next-steps] -Use our [quick start guides](/solutions/search/get-started/quickstarts.md) to learn the basics of {{es}}. +Use our [quick start guides](/solutions/elasticsearch-solution-project/get-started/quickstarts.md) to learn the basics of {{es}}. diff --git a/explore-analyze/ai-features.md b/explore-analyze/ai-features.md index 1636142ac7..e20afb2b5b 100644 --- a/explore-analyze/ai-features.md +++ b/explore-analyze/ai-features.md @@ -71,7 +71,7 @@ The [{{es}}](/solutions/search.md) solution view (or project type in {{serverles ### Agent Builder -[Agent Builder](/solutions/search/elastic-agent-builder.md) enables you to create AI agents that can interact with your {{es}} data, run queries, and provide intelligent responses. It provides a complete framework for building conversational AI experiences on top of your search infrastructure. +[Agent Builder](/solutions/elasticsearch-solution-project/elastic-agent-builder.md) enables you to create AI agents that can interact with your {{es}} data, run queries, and provide intelligent responses. It provides a complete framework for building conversational AI experiences on top of your search infrastructure. ### AI assistant for {{es}} diff --git a/explore-analyze/query-filter.md b/explore-analyze/query-filter.md index b5d559247b..58a2642883 100644 --- a/explore-analyze/query-filter.md +++ b/explore-analyze/query-filter.md @@ -27,7 +27,7 @@ You’ll use a combination of an API endpoint and a query language to interact w - A number of [tools](/explore-analyze/query-filter/tools.md) are available for you to save, debug, and optimize your queries. -If you're just getting started with {{es}}, try the hands-on [](/solutions/search/get-started/index-basics.md) to learn how to add data and run basic searches using Query DSL and the `_search` endpoint. +If you're just getting started with {{es}}, try the hands-on [](/solutions/elasticsearch-solution-project/get-started/index-basics.md) to learn how to add data and run basic searches using Query DSL and the `_search` endpoint. ## Filtering diff --git a/release-notes/elastic-cloud-serverless/index.md b/release-notes/elastic-cloud-serverless/index.md index 34a097f431..eaecb5b455 100644 --- a/release-notes/elastic-cloud-serverless/index.md +++ b/release-notes/elastic-cloud-serverless/index.md @@ -386,7 +386,7 @@ Review the changes, fixes, and more to {{serverless-full}}. ### Features and enhancements [serverless-changelog-10202025-features-enhancements] -* [Agent Builder](/solutions/search/elastic-agent-builder.md) is now available in technical preview and is enabled by default on {{serverless-full}} +* [Agent Builder](/solutions/elasticsearch-solution-project/elastic-agent-builder.md) is now available in technical preview and is enabled by default on {{serverless-full}} * Lets you remove root privileges from {{fleet}} managed agents [#237790]({{kib-pull}}237790) * Adds the `xpack.fleet.experimentalFeatures` setting [#238840]({{kib-pull}}238840) * Supports expression suggestions within function parameters [#236343]({{kib-pull}}236343) diff --git a/solutions/elasticsearch-solution-project/agent-builder/models.md b/solutions/elasticsearch-solution-project/agent-builder/models.md index 874404548f..c8d5969cfa 100644 --- a/solutions/elasticsearch-solution-project/agent-builder/models.md +++ b/solutions/elasticsearch-solution-project/agent-builder/models.md @@ -69,7 +69,7 @@ The following models are not compatible with {{agent-builder}}: - **OpenAI**: GPT-5-chat -Learn more about [incompatible LLMs](/solutions/search/agent-builder/limitations-known-issues.md#incompatible-llms). +Learn more about [incompatible LLMs](/solutions/elasticsearch-solution-project/agent-builder/limitations-known-issues.md#incompatible-llms). ### Why model quality matters diff --git a/solutions/elasticsearch-solution-project/get-started/index-basics.md b/solutions/elasticsearch-solution-project/get-started/index-basics.md index 1d271869d4..92ca5f9e12 100644 --- a/solutions/elasticsearch-solution-project/get-started/index-basics.md +++ b/solutions/elasticsearch-solution-project/get-started/index-basics.md @@ -470,7 +470,7 @@ Deleting an index permanently deletes its documents, shards, and metadata. ## Next steps This quickstart introduced the basics of creating indices, adding data, and performing basic searches with {{es}}. -To try out similar steps from the {{es}} Python client, go to [](/solutions/search/get-started/keyword-search-python.md). +To try out similar steps from the {{es}} Python client, go to [](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md). The following resources will help you understand {{es}} concepts better and dive into the basics of query languages for searching data: * [Fundamentals of Elasticsearch](/manage-data/data-store.md) diff --git a/solutions/elasticsearch-solution-project/mcp.md b/solutions/elasticsearch-solution-project/mcp.md index 5be6626170..096de9365b 100644 --- a/solutions/elasticsearch-solution-project/mcp.md +++ b/solutions/elasticsearch-solution-project/mcp.md @@ -14,7 +14,7 @@ Elastic offers two MCP server options for connecting agents to your {{es}} data. stack: preview 9.2 serverless: preview ``` -Elastic 9.2.0+ and Serverless deployments provide an [Agent Builder MCP server endpoint](https://www.elastic.co/docs/solutions/search/agent-builder/mcp-server) that exposes all built-in and custom [tools](https://www.elastic.co/docs/solutions/search/agent-builder/tools) you can use to power agentic workflows. +Elastic 9.2.0+ and Serverless deployments provide an [Agent Builder MCP server endpoint](/solutions/elasticsearch-solution-project/agent-builder/mcp-server.md) that exposes all built-in and custom [tools](/solutions/elasticsearch-solution-project/agent-builder/tools.md) you can use to power agentic workflows. ## {{es}} MCP server diff --git a/solutions/search/esql-for-search.md b/solutions/search/esql-for-search.md index 35755071ee..8d23143c3b 100644 --- a/solutions/search/esql-for-search.md +++ b/solutions/search/esql-for-search.md @@ -61,7 +61,7 @@ Features are usually available on {{serverless-full}} before stack-versioned dep - Text queries where some results are more relevant than others - Finding documents similar to a search phrase - Any scenario where you want the "best" matches first -- You want to use [analyzers](elasticsearch://reference/elasticsearch/mapping-reference/analyzer.md) or [synonyms](/solutions/search/full-text/search-with-synonyms.md) +- You want to use [analyzers](elasticsearch://reference/elasticsearch/mapping-reference/analyzer.md) or [synonyms](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md) {{esql}}'s search functions address several key limitations that existed for text filtering: they work directly on multivalued fields, leverage analyzers for proper text analysis, and use optimized Lucene index structures for better performance. diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md index 55ae6f067b..7b71b34341 100644 --- a/solutions/search/get-started.md +++ b/solutions/search/get-started.md @@ -28,9 +28,9 @@ To follow along with this guide, you'll need: Choose a quickstart based on your use case: -- [**Index basics**](/solutions/search/get-started/index-basics.md): Learn how to create indices, add documents, and perform basic searches using the {{es}} APIs. -- [**Keyword search with Python**](/solutions/search/get-started/keyword-search-python.md): Build a keyword search application using the Python client. -- [**Semantic search**](/solutions/search/get-started/semantic-search.md): Implement semantic search using vector embeddings. +- [**Index basics**](/solutions/elasticsearch-solution-project/get-started/index-basics.md): Learn how to create indices, add documents, and perform basic searches using the {{es}} APIs. +- [**Keyword search with Python**](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md): Build a keyword search application using the Python client. +- [**Semantic search**](/solutions/elasticsearch-solution-project/get-started/semantic-search.md): Implement semantic search using vector embeddings. ## Explore search approaches diff --git a/solutions/search/querying-for-search.md b/solutions/search/querying-for-search.md index f16e7ec181..3254e37028 100644 --- a/solutions/search/querying-for-search.md +++ b/solutions/search/querying-for-search.md @@ -34,5 +34,5 @@ You can use the [{{es}} REST APIs](https://www.elastic.co/docs/api/doc/elasticse :::: ::::{tip} -Try our hands-on [quickstart guides](/solutions/search/get-started/quickstarts.md) to get started, or check out our [Python notebooks](https://github.com/elastic/elasticsearch-labs/tree/main/notebooks#readme). +Try our hands-on [quickstart guides](/solutions/elasticsearch-solution-project/get-started/quickstarts.md) to get started, or check out our [Python notebooks](https://github.com/elastic/elasticsearch-labs/tree/main/notebooks#readme). :::: From b67429eb066aeb44bc031e97c3c8730f7ca16ada Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:35:49 +0000 Subject: [PATCH 09/35] Update remaining references to playground, MCP, and search-applications MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Fix playground references from old rag/ path to new top-level location - Update MCP references to elasticsearch-solution-project - Update search-applications references to new location 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../differences-from-other-elasticsearch-offerings.md | 2 +- .../reference-architectures/hotfrozen-high-availability.md | 2 +- explore-analyze/ai-features.md | 4 ++-- .../machine-learning-in-kibana/inference-processing.md | 2 +- explore-analyze/query-filter/tools/playground.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 5028ada282..2d05e8e72b 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -98,7 +98,7 @@ This table compares Elasticsearch capabilities between {{ech}} deployments and S | **Repository management** | ✅ | Managed | Automatically managed by Elastic | | [**Scripted metric aggregations**](elasticsearch://reference/aggregations/search-aggregations-metrics-scripted-metric-aggregation.md) | ✅ | ❌ | Not available in Serverless
The alternative for this in Serverless is [ES|QL](elasticsearch://reference/query-languages/esql.md) | | [**`join` fields**](elasticsearch://reference/elasticsearch/mapping-reference/parent-join.md) | ✅ | ❌ | Not available in Serverless
The alternative for this in Serverless is the ES\|QL [`LOOKUP JOIN`](elasticsearch://reference/query-languages/esql/commands/lookup-join.md) command | -| [**Search applications**](/solutions/search/search-applications.md) | - UI and APIs
- Maintenance mode (beta) | - API-only
- Maintenance mode (beta) | UI not available in Serverless | +| [**Search applications**](/solutions/elasticsearch-solution-project/search-applications.md) | - UI and APIs
- Maintenance mode (beta) | - API-only
- Maintenance mode (beta) | UI not available in Serverless | | **Shard management** | User-configurable | Managed by Elastic | No manual shard allocation in Serverless | | [**Watcher**](/explore-analyze/alerts-cases/watcher.md) | ✅ | ❌ | Use **Kibana Alerts** instead, which provides rich integrations across use cases | | **Web crawler** | ❌ (Managed Elastic Crawler discontinued with Enterprise Search in 9.0) | Self-managed only | Use [**self-managed crawler**](https://github.com/elastic/crawler) | diff --git a/deploy-manage/reference-architectures/hotfrozen-high-availability.md b/deploy-manage/reference-architectures/hotfrozen-high-availability.md index f24c976a02..bdefcb1d92 100644 --- a/deploy-manage/reference-architectures/hotfrozen-high-availability.md +++ b/deploy-manage/reference-architectures/hotfrozen-high-availability.md @@ -27,7 +27,7 @@ This Hot/Frozen – High Availability architecture is intended for organizations * Have a requirement for cost effective long term data storage (many months or years). * Provide insights and alerts using logs, metrics, traces, or various event types to ensure optimal performance and quick issue resolution for applications. * Apply [machine learning anomaly detection](/explore-analyze/machine-learning/anomaly-detection.md) to help detect patterns in time series data to find root cause and resolve problems faster. -* Use an AI assistant ([Observability](/explore-analyze/ai-features/ai-assistant.md), [Security](/solutions/security/ai/ai-assistant.md), or [Playground](/solutions/search/rag/playground.md)) for investigation, incident response, reporting, query generation, or query conversion from other languages using natural language. +* Use an AI assistant ([Observability](/explore-analyze/ai-features/ai-assistant.md), [Security](/solutions/security/ai/ai-assistant.md), or [Playground](/solutions/elasticsearch-solution-project/playground.md)) for investigation, incident response, reporting, query generation, or query conversion from other languages using natural language. * Deploy an architecture model that allows for maximum flexibility between storage cost and performance. ::::{important} diff --git a/explore-analyze/ai-features.md b/explore-analyze/ai-features.md index e20afb2b5b..cd73506b82 100644 --- a/explore-analyze/ai-features.md +++ b/explore-analyze/ai-features.md @@ -79,11 +79,11 @@ The [{{es}}](/solutions/search.md) solution view (or project type in {{serverles ### Playground -[Playground](/solutions/search/rag/playground.md) enables you to use large language models (LLMs) to understand, explore, and analyze your {{es}} data using retrieval augmented generation (RAG), via a chat interface. Playground is also very useful for testing and debugging your {{es}} queries, using the [retrievers](/solutions/search/retrievers-overview.md) syntax with the `_search` endpoint. +[Playground](/solutions/elasticsearch-solution-project/playground.md) enables you to use large language models (LLMs) to understand, explore, and analyze your {{es}} data using retrieval augmented generation (RAG), via a chat interface. Playground is also very useful for testing and debugging your {{es}} queries, using the [retrievers](/solutions/search/retrievers-overview.md) syntax with the `_search` endpoint. ### Model context protocol -The [Model Context Protocol (MCP)](/solutions/search/mcp.md) lets you connect AI agents and assistants to your {{es}} data to enable natural language interactions with your indices. +The [Model Context Protocol (MCP)](/solutions/elasticsearch-solution-project/mcp.md) lets you connect AI agents and assistants to your {{es}} data to enable natural language interactions with your indices. ## AI-powered features in {{observability}} diff --git a/explore-analyze/machine-learning/machine-learning-in-kibana/inference-processing.md b/explore-analyze/machine-learning/machine-learning-in-kibana/inference-processing.md index 51ac0e20ca..dbba4e7285 100644 --- a/explore-analyze/machine-learning/machine-learning-in-kibana/inference-processing.md +++ b/explore-analyze/machine-learning/machine-learning-in-kibana/inference-processing.md @@ -25,7 +25,7 @@ This feature is not available at all Elastic subscription levels. Refer to the E ### ELSER text expansion [ingest-pipeline-search-inference-elser] -Using Elastic’s [ELSER machine learning model](../nlp/ml-nlp-elser.md) you can easily incorporate text expansion for your queries. This works by using ELSER to provide semantic enrichments to your documents upon ingestion, combined with the power of [Elastic Search Application templates](../../../solutions/search/search-applications.md) to provide automated text expansion at query time. +Using Elastic's [ELSER machine learning model](../nlp/ml-nlp-elser.md) you can easily incorporate text expansion for your queries. This works by using ELSER to provide semantic enrichments to your documents upon ingestion, combined with the power of [Elastic Search Application templates](/solutions/elasticsearch-solution-project/search-applications.md) to provide automated text expansion at query time. ### Named entity recognition (NER) [ingest-pipeline-search-inference-ner] diff --git a/explore-analyze/query-filter/tools/playground.md b/explore-analyze/query-filter/tools/playground.md index 8dedbcc4cd..c86468593b 100644 --- a/explore-analyze/query-filter/tools/playground.md +++ b/explore-analyze/query-filter/tools/playground.md @@ -16,6 +16,6 @@ Use the Search Playground to test and edit {{es}} queries visually in the UI. Th Find Playground in the {{es-serverless}} UI under **{{es}} > Build > Playground**. ::::{note} -ℹ️ For more details, check the full [Playground documentation](../../../solutions/search/rag/playground.md). +ℹ️ For more details, check the full [Playground documentation](/solutions/elasticsearch-solution-project/playground.md). :::: From 460e69c783279d777fa77450363c0b3b7138eea6 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:36:22 +0000 Subject: [PATCH 10/35] Fix final search-with-synonyms reference in ece-ha.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- deploy-manage/deploy/cloud-enterprise/ece-ha.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-ha.md b/deploy-manage/deploy/cloud-enterprise/ece-ha.md index ba5b7c3cba..0e3419052e 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-ha.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-ha.md @@ -53,7 +53,7 @@ Backing up Zookeeper data directory is also recommended. Refer to [rebuilding a ## External resources accessibility -If you’re using a [private Docker registry server](ece-install-offline-with-registry.md) or hosting any [custom bundles and plugins](../../../solutions/search/full-text/search-with-synonyms.md) on a web server, make sure these resources are accessible from all ECE allocators, so they can continue to be accessed in the event of a network partition or zone outage. +If you're using a [private Docker registry server](ece-install-offline-with-registry.md) or hosting any [custom bundles and plugins](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md) on a web server, make sure these resources are accessible from all ECE allocators, so they can continue to be accessed in the event of a network partition or zone outage. ## Other recommendations From c94e778de7a9c68480b54424ae7037dd70e2feb0 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:41:30 +0000 Subject: [PATCH 11/35] Move search-connection-details to Elasticsearch solution MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Connection details are UI-specific and belong in the ES solution section, not the universal Search use case section. Updated all references throughout the documentation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- reference/elasticsearch-clients/index.md | 2 +- .../agent-builder/get-started.md | 2 +- .../elasticsearch-solution-project/agent-builder/kibana-api.md | 2 +- .../elasticsearch-solution-project/agent-builder/mcp-server.md | 2 +- solutions/elasticsearch-solution-project/get-started.md | 2 +- .../search-connection-details.md | 0 .../opentelemetry/quickstart/self-managed/docker.md | 2 +- .../opentelemetry/quickstart/self-managed/hosts_vms.md | 2 +- .../get-started/opentelemetry/quickstart/self-managed/k8s.md | 2 +- solutions/search/get-started.md | 2 +- solutions/search/ingest-for-search.md | 2 +- solutions/search/site-or-app/clients.md | 2 +- solutions/toc.yml | 3 +-- 13 files changed, 12 insertions(+), 13 deletions(-) rename solutions/{search => elasticsearch-solution-project}/search-connection-details.md (100%) diff --git a/reference/elasticsearch-clients/index.md b/reference/elasticsearch-clients/index.md index 79b3ed32c1..723259f0ea 100644 --- a/reference/elasticsearch-clients/index.md +++ b/reference/elasticsearch-clients/index.md @@ -22,5 +22,5 @@ products: - [Rust](elasticsearch-rs://reference/index.md) ::::{tip} -Learn how to [connect to your {{es}} endpoint](/solutions/search/search-connection-details.md). +Learn how to [connect to your {{es}} endpoint](/solutions/elasticsearch-solution-project/search-connection-details.md). :::: diff --git a/solutions/elasticsearch-solution-project/agent-builder/get-started.md b/solutions/elasticsearch-solution-project/agent-builder/get-started.md index 3e5c393661..07decf6bac 100644 --- a/solutions/elasticsearch-solution-project/agent-builder/get-started.md +++ b/solutions/elasticsearch-solution-project/agent-builder/get-started.md @@ -68,7 +68,7 @@ For a broader overview of ingestion options, go to [](/manage-data/ingest.md). :::{tip} If you're not ready to add your own data, you can: - Use the Elastic [sample data](/manage-data/ingest/sample-data.md). -- Generate synthetic financial data using [this Python tool](https://github.com/jeffvestal/synthetic-financial-data?tab=readme-ov-file#synthetic-financial-data-generator-). (This requires your [{{es}} URL and an API key](/solutions/search/search-connection-details.md)). +- Generate synthetic financial data using [this Python tool](https://github.com/jeffvestal/synthetic-financial-data?tab=readme-ov-file#synthetic-financial-data-generator-). (This requires your [{{es}} URL and an API key](/solutions/elasticsearch-solution-project/search-connection-details.md)). % TODO: we can link to a an agent builder tutorial if we add one in the docs ::: diff --git a/solutions/elasticsearch-solution-project/agent-builder/kibana-api.md b/solutions/elasticsearch-solution-project/agent-builder/kibana-api.md index ddfe4ef52e..a666fe5f03 100644 --- a/solutions/elasticsearch-solution-project/agent-builder/kibana-api.md +++ b/solutions/elasticsearch-solution-project/agent-builder/kibana-api.md @@ -37,7 +37,7 @@ curl -X GET "https://${KIBANA_URL}/api/agent_builder/tools" \ ``` :::{tip} To generate API keys, search for `API keys` in the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md). -[Learn more](https://www.elastic.co/docs/solutions/search/search-connection-details). +[Learn more](/solutions/elasticsearch-solution-project/search-connection-details.md). ::: ### Working with Spaces diff --git a/solutions/elasticsearch-solution-project/agent-builder/mcp-server.md b/solutions/elasticsearch-solution-project/agent-builder/mcp-server.md index fbe9011e0f..ef623faa7c 100644 --- a/solutions/elasticsearch-solution-project/agent-builder/mcp-server.md +++ b/solutions/elasticsearch-solution-project/agent-builder/mcp-server.md @@ -63,7 +63,7 @@ export KIBANA_URL="your-kibana-url" export API_KEY="your-api-key" ``` -For information on generating API keys, refer to [API keys](https://www.elastic.co/docs/solutions/search/search-connection-details). +For information on generating API keys, refer to [API keys](/solutions/elasticsearch-solution-project/search-connection-details.md). Tools execute with the scope assigned to the API key. Make sure your API key has the appropriate permissions to only access the indices and data that you want to expose through the MCP server. To learn more, refer to [](#api-key-application-privileges). ::: diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index d9d61f675c..18c19d11e0 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -25,7 +25,7 @@ To use the {{es}} solution, you'll need: - An {{es}} solution deployment on {{ech}} or an {{es}} serverless project - Access to {{kib}} for using the UI tools -- Connection details for your cluster. Refer to [Connection details](/solutions/search/search-connection-details.md) for more information. +- Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. ## Quickstarts diff --git a/solutions/search/search-connection-details.md b/solutions/elasticsearch-solution-project/search-connection-details.md similarity index 100% rename from solutions/search/search-connection-details.md rename to solutions/elasticsearch-solution-project/search-connection-details.md diff --git a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/docker.md b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/docker.md index 0185139693..ef38e630fb 100644 --- a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/docker.md +++ b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/docker.md @@ -35,7 +35,7 @@ Create the `otel-collector-config.yml` file with your EDOT Collector configurati ::::{step} Retrieve your settings -Retrieve your [{{es}} endpoint](/solutions/search/search-connection-details.md) and [API key](/deploy-manage/api-keys/elasticsearch-api-keys.md). +Retrieve your [{{es}} endpoint](/solutions/elasticsearch-solution-project/search-connection-details.md) and [API key](/deploy-manage/api-keys/elasticsearch-api-keys.md). :::: ::::{step} Create the .env file diff --git a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/hosts_vms.md b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/hosts_vms.md index 28e5158fa1..e6f8f97b6d 100644 --- a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/hosts_vms.md +++ b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/hosts_vms.md @@ -35,7 +35,7 @@ Follow these steps to deploy the EDOT Collector and EDOT OTel SDKs. :::::{step} Configure the EDOT Collector -Retrieve your [{{es}} endpoint](/solutions/search/search-connection-details.md) and [API key](/deploy-manage/api-keys/elasticsearch-api-keys.md) and replace `` and `` before applying the following command. +Retrieve your [{{es}} endpoint](/solutions/elasticsearch-solution-project/search-connection-details.md) and [API key](/deploy-manage/api-keys/elasticsearch-api-keys.md) and replace `` and `` before applying the following command. ::::{tab-set} diff --git a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/k8s.md b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/k8s.md index 76b4c04205..784135e518 100644 --- a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/k8s.md +++ b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/k8s.md @@ -41,7 +41,7 @@ helm repo add open-telemetry 'https://open-telemetry.github.io/opentelemetry-hel ::::{step} Set up credentials -Retrieve your [{{es}} endpoint](/solutions/search/search-connection-details.md) and [API key](/deploy-manage/api-keys/elasticsearch-api-keys.md) and replace both in the following command to create a namespace and a secret with your credentials. +Retrieve your [{{es}} endpoint](/solutions/elasticsearch-solution-project/search-connection-details.md) and [API key](/deploy-manage/api-keys/elasticsearch-api-keys.md) and replace both in the following command to create a namespace and a secret with your credentials. ```bash kubectl create namespace opentelemetry-operator-system diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md index 7b71b34341..5c7a211f6f 100644 --- a/solutions/search/get-started.md +++ b/solutions/search/get-started.md @@ -22,7 +22,7 @@ Using the {{es}} solution or serverless project type? Check out the [{{es}} solu To follow along with this guide, you'll need: - An {{es}} cluster or serverless project. [Create a deployment](/get-started/start-building.md) if you don't have one yet. -- Connection details for your cluster. Refer to [Connection details](/solutions/search/search-connection-details.md) for more information. +- Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. ## Quickstarts diff --git a/solutions/search/ingest-for-search.md b/solutions/search/ingest-for-search.md index 46e7a1eda7..0ccec585af 100644 --- a/solutions/search/ingest-for-search.md +++ b/solutions/search/ingest-for-search.md @@ -39,7 +39,7 @@ If you just want to do a quick test, you can load [sample data](/manage-data/ing You can use the [`_bulk` API]({{es-apis}}group/endpoint-document) to add data to your {{es}} indices, using any HTTP client, including the [{{es}} client libraries](/solutions/search/site-or-app/clients.md). ::::{tip} -To connect to an {{es-serverless}} project, you must [find the connection details](/solutions/search/search-connection-details.md). +To connect to an {{es-serverless}} project, you must [find the connection details](/solutions/elasticsearch-solution-project/search-connection-details.md). :::: While the {{es}} APIs can be used for any data type, Elastic provides specialized tools that optimize ingestion for specific use cases. diff --git a/solutions/search/site-or-app/clients.md b/solutions/search/site-or-app/clients.md index 89631e077d..3f79309806 100644 --- a/solutions/search/site-or-app/clients.md +++ b/solutions/search/site-or-app/clients.md @@ -32,5 +32,5 @@ In addition to official clients, the Elastic community has contributed libraries - [Community-contributed clients](elasticsearch://reference/community-contributed/index.md) ::::{tip} -Learn how to [connect to your {{es}} endpoint](/solutions/search/search-connection-details.md). +Learn how to [connect to your {{es}} endpoint](/solutions/elasticsearch-solution-project/search-connection-details.md). :::: \ No newline at end of file diff --git a/solutions/toc.yml b/solutions/toc.yml index 9190206766..b1174777f6 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -4,8 +4,6 @@ toc: - file: search.md children: - file: search/get-started.md - children: - - file: search/search-connection-details.md - file: search/ingest-for-search.md children: - file: search/search-pipelines.md @@ -67,6 +65,7 @@ toc: children: - file: elasticsearch-solution-project/get-started.md children: + - file: elasticsearch-solution-project/search-connection-details.md - file: elasticsearch-solution-project/get-started/quickstarts.md children: - file: elasticsearch-solution-project/get-started/index-basics.md From 168f2d9b1e9e33eab7b66418b2638124d362307e Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Mon, 8 Dec 2025 15:53:58 +0000 Subject: [PATCH 12/35] Improve Search use case landing page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Remove marketing language, establish concrete scope immediately - Replace vague use cases table with specific application types - Remove duplicate links (Key primitives now plain text) - Expand RAG documentation references to include querying, retrievers, ranking - Remove serverless deployment tip (doesn't belong in universal search primitives) - Add direct links to relevant documentation sections 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- solutions/search.md | 39 ++++++++++++--------------------------- 1 file changed, 12 insertions(+), 27 deletions(-) diff --git a/solutions/search.md b/solutions/search.md index e4740323ea..c2b424cb6d 100644 --- a/solutions/search.md +++ b/solutions/search.md @@ -12,29 +12,24 @@ navigation_title: Search use case # Search use case -Build powerful search experiences using {{es}}'s universal search capabilities. Whether you're running a self-managed cluster, {{ech}}, or an {{es}} serverless project, these search primitives are available across all deployment types. +This section documents {{es}} search primitives. These capabilities that are available across all Elastic deployments. -{{es}} is a distributed datastore that can ingest, index, and manage various types of data in near real-time, making them both searchable and analyzable. This documentation covers the core search capabilities and techniques that work universally across all {{es}} deployments. +Use this section to understand search techniques, query methods, ranking strategies, and data ingestion for search applications. ::::{tip} -Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for exclusive UI tools like Agent Builder, Playground, and Search Applications that complement these universal search capabilities. +Using the {{es}} solution or serverless project type? The {{es}} solution documentation covers exclusive UI tools (Agent Builder, Playground, Search Applications) that complement these search primitives. Refer to [](/solutions/elasticsearch-solution-project.md) for more details. :::: -## Use cases +## What you can build -Here are a few common real-world applications: - -| Use case | Business goals | Technical requirements | -| ------------------------------------ | ------------------------------------------------------------------ | ------------------------------------------------------------- | -| **Vector search/hybrid search** | Run nearest neighbour search, combine with text for hybrid results | Dense embeddings, sparse embeddings, combined with text/BM25 | -| **Ecommerce/product catalog search** | Provide fast, relevant, and up-to-date results, faceted navigation | Inventory sync, user behavior tracking, results caching | -| **Workplace/knowledge base search** | Search across range of data sources, enforcing permissions | Third-party connectors, document-level security, role mapping | -| **Website search** | Deliver relevant, up-to-date results | Web crawling, incremental indexing, query caching | -| **Customer support search** | Surface relevant solutions, manage access controls, track metrics | Knowledge graph, role-based access, analytics | -| **Chatbots/RAG** | Enable natural conversations, provide context, maintain knowledge | Vector search, ML models, knowledge base integration | -| **Geospatial search** | Process location queries, sort by proximity, filter by area | Geo-mapping, spatial indexing, distance calculations | - -If you're new to {{es}} and want to try out some simple search use cases, refer to [Get started with search](/solutions/search/get-started.md). +| Application type | Search technique | Key primitives | Documentation | +|-----------------|------------------|----------------|---------------| +| **Website/documentation search** | Text matching with relevance scoring | Full-text search, analyzers, scoring functions | [Full-text search](/solutions/search/full-text.md), [Ranking](/solutions/search/ranking.md) | +| **Ecommerce product catalogs** | Text + filters + facets | Hybrid search, aggregations, boosting | [Hybrid search](/solutions/search/hybrid-search.md), [Ranking](/solutions/search/ranking.md) | +| **Semantic/similarity search** | Embedding-based retrieval | Vector search, dense/sparse vectors, kNN | [Vector search](/solutions/search/vector.md), [Semantic search](/solutions/search/semantic-search.md) | +| **RAG applications** | Retrieval for LLM context | Retrievers, embedding models, ranking, query methods | [RAG](/solutions/search/rag.md), [Querying](/solutions/search/querying-for-search.md), [Retrievers](/solutions/search/retrievers-overview.md), [Semantic search](/solutions/search/semantic-search.md), [Ranking](/solutions/search/ranking.md) | +| **Geospatial applications** | Location-based queries | Geo-point, geo-shape fields, distance sorting | [Geospatial search](elasticsearch://reference/elasticsearch/mapping-reference/geo-point.md) | +| **Federated search** | Querying multiple clusters | Remote cluster connections, distributed queries | [Cross-cluster search](/solutions/search/cross-cluster-search.md) | ## Core concepts [search-concepts] @@ -45,14 +40,4 @@ To dive more deeply into the building blocks of {{es}} clusters, including nodes ## Related reference * [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) -* [Content connectors](elasticsearch://reference/search-connectors/index.md) * [{{es}} API documentation]({{es-apis}}) - -::::{tip} -Not sure whether {{es}} on {{serverless-full}} is the right deployment choice for you? - -Check out the following resources to help you decide: - -- [What’s different?](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md): Understand the differences between {{serverless-full}} and other deployment types. -- [Billing](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md): Learn about the billing model for {{es}} on {{serverless-full}}. -:::: From 490f92fefa5031a4a89ee556b9324ccff6b473d9 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Tue, 9 Dec 2025 11:02:14 +0000 Subject: [PATCH 13/35] Move synonyms documentation to Search use case MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Synonyms are search primitives available across all deployments, not exclusive to ES solution. Only the Synonyms UI is ES-solution-specific. - Move search-with-synonyms.md and create-update-synonyms-api-example.md from elasticsearch-solution-project/full-text/ to search/full-text/ - Update toc.yml to include synonyms under search/full-text - Update references in ece-ha.md - Add redirects for moved pages 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../deploy/cloud-enterprise/ece-ha.md | 2 +- redirects.yml | 3 ++ solutions/elasticsearch-solution-project.md | 32 ++++++++----------- .../get-started.md | 2 +- .../get-started/quickstarts.md | 2 +- solutions/observability.md | 4 +-- solutions/search/esql-for-search.md | 2 +- .../create-update-synonyms-api-example.md | 0 .../full-text/search-with-synonyms.md | 0 solutions/search/get-started.md | 6 ++-- solutions/security.md | 4 +-- solutions/toc.yml | 16 +++++----- 12 files changed, 36 insertions(+), 37 deletions(-) rename solutions/{elasticsearch-solution-project => search}/full-text/create-update-synonyms-api-example.md (100%) rename solutions/{elasticsearch-solution-project => search}/full-text/search-with-synonyms.md (100%) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-ha.md b/deploy-manage/deploy/cloud-enterprise/ece-ha.md index 0e3419052e..32d12aed77 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-ha.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-ha.md @@ -53,7 +53,7 @@ Backing up Zookeeper data directory is also recommended. Refer to [rebuilding a ## External resources accessibility -If you're using a [private Docker registry server](ece-install-offline-with-registry.md) or hosting any [custom bundles and plugins](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md) on a web server, make sure these resources are accessible from all ECE allocators, so they can continue to be accessed in the event of a network partition or zone outage. +If you're using a [private Docker registry server](ece-install-offline-with-registry.md) or hosting any [custom bundles and plugins](/solutions/search/full-text/search-with-synonyms.md) on a web server, make sure these resources are accessible from all ECE allocators, so they can continue to be accessed in the event of a network partition or zone outage. ## Other recommendations diff --git a/redirects.yml b/redirects.yml index f824a66dfc..47fdd1fbc3 100644 --- a/redirects.yml +++ b/redirects.yml @@ -1,4 +1,7 @@ redirects: + # Search primitives moved from ES solution to Search use case + 'solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md': 'solutions/search/full-text/search-with-synonyms.md' + 'solutions/elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md': 'solutions/search/full-text/create-update-synonyms-api-example.md' 'deploy-manage/security/secure-http-communications.md': '!deploy-manage/security/secure-cluster-communications.md' 'deploy-manage/security/manually-configure-security-in-self-managed-cluster.md': '!deploy-manage/security/self-setup.md' 'deploy-manage/security/security-certificates-keys.md': '!deploy-manage/security/self-auto-setup.md' diff --git a/solutions/elasticsearch-solution-project.md b/solutions/elasticsearch-solution-project.md index af0016b2aa..ae89456992 100644 --- a/solutions/elasticsearch-solution-project.md +++ b/solutions/elasticsearch-solution-project.md @@ -9,19 +9,24 @@ products: - id: elasticsearch - id: cloud-serverless - id: kibana -navigation_title: Elasticsearch +navigation_title: Elasticsearch solution --- -# {{es}} solution overview - -The {{es}} solution and serverless project type provide specialized UI tools and interfaces that help you build search applications on top of the {{es}} platform. - -These UI affordances are exclusive to the {{es}} solution (on {{ech}}) and the {{es}} serverless project type. They complement the universal search capabilities available across all {{es}} deployments. +# {{es}} solution & project type overview ::::{tip} -Looking for general search capabilities that work across all {{es}} deployments? Check out the [Search use case](/solutions/search.md) documentation, which covers universal {{es}} search primitives including full-text search, vector search, semantic search, and hybrid search. +Not sure which deployment type is right for you? Use the following resources to help you decide: + +- Read the Elastic [deployment types overview](/deploy-manage/deploy.md) +- Compare [serverless and {{ech}}](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md) + - Compare pricing models between [Elastic Cloud](/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md) and [Serverless](/deploy-manage/cloud-organization/billing/serverless-project-billing-dimensions.md) :::: + +The {{es}} solution and serverless project type provide specialized UI tools and interfaces that help you build search applications on top of the {{es}} platform. + +These UI affordances are exclusive to the {{es}} **solution** (on non-serverless deployments) and the {{es}} serverless **project type**. They complement the core [search primitives]((/solutions/search.md)) available across all Elastic deployments. + ## Features and tools The {{es}} solution provides the following specialized UI tools: @@ -40,7 +45,7 @@ The {{es}} solution provides the following specialized UI tools: ### Synonyms UI -The [Search with synonyms](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md) interface provides a dedicated UI for managing synonym sets directly within {{kib}}, making it easier to improve search relevance without editing configuration files. +The [Search with synonyms](/solutions/search/full-text/search-with-synonyms.md) interface provides a dedicated UI for managing synonym sets directly within {{kib}}, making it easier to improve search relevance without editing configuration files. ### Query Rules UI @@ -65,13 +70,4 @@ For a deeper understanding of search concepts and techniques, refer to the [Sear * [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) * [Content connectors](elasticsearch://reference/search-connectors/index.md) * [{{es}} API documentation]({{es-apis}}) -* [Search use case documentation](/solutions/search.md) - -::::{tip} -Not sure whether {{es}} on {{serverless-full}} is the right deployment choice for you? - -Check out the following resources to help you decide: - -- [What's different?](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md): Understand the differences between {{serverless-full}} and other deployment types. -- [Billing](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md): Learn about the billing model for {{es}} on {{serverless-full}}. -:::: +* [Search use case documentation](/solutions/search.md) \ No newline at end of file diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index 18c19d11e0..7759470e7a 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -53,7 +53,7 @@ Manage and deploy search-powered applications with pre-built templates. Refer to ### UI tools for search optimization -- [**Search with synonyms**](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md): Manage synonym sets through the UI +- [**Search with synonyms**](/solutions/search/full-text/search-with-synonyms.md): Manage synonym sets through the UI - [**Query Rules UI**](/solutions/elasticsearch-solution-project/query-rules-ui.md): Create rules to modify search behavior - [**AI Assistant**](/solutions/elasticsearch-solution-project/ai-assistant.md): Get intelligent assistance across the platform diff --git a/solutions/elasticsearch-solution-project/get-started/quickstarts.md b/solutions/elasticsearch-solution-project/get-started/quickstarts.md index 98059510b5..51d327a946 100644 --- a/solutions/elasticsearch-solution-project/get-started/quickstarts.md +++ b/solutions/elasticsearch-solution-project/get-started/quickstarts.md @@ -8,7 +8,7 @@ products: - id: elasticsearch --- -# {{es}} quickstarts +# Quickstarts Quickstarts reduce your time-to-value by offering a fast path to learn about search strategies. Each quickstart provides: diff --git a/solutions/observability.md b/solutions/observability.md index 01ca4f18f5..dc7262af10 100644 --- a/solutions/observability.md +++ b/solutions/observability.md @@ -1,5 +1,5 @@ --- -navigation_title: Observability +navigation_title: Observability solution mapped_pages: - https://www.elastic.co/guide/en/serverless/current/what-is-observability-serverless.html - https://www.elastic.co/guide/en/observability/current/index.html @@ -14,7 +14,7 @@ products: - id: edot-collector --- -# Elastic Observability overview +# Elastic Observability solution & project type overview :::{include} ../get-started/_snippets/observability-overview.md ::: diff --git a/solutions/search/esql-for-search.md b/solutions/search/esql-for-search.md index 8d23143c3b..35755071ee 100644 --- a/solutions/search/esql-for-search.md +++ b/solutions/search/esql-for-search.md @@ -61,7 +61,7 @@ Features are usually available on {{serverless-full}} before stack-versioned dep - Text queries where some results are more relevant than others - Finding documents similar to a search phrase - Any scenario where you want the "best" matches first -- You want to use [analyzers](elasticsearch://reference/elasticsearch/mapping-reference/analyzer.md) or [synonyms](/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md) +- You want to use [analyzers](elasticsearch://reference/elasticsearch/mapping-reference/analyzer.md) or [synonyms](/solutions/search/full-text/search-with-synonyms.md) {{esql}}'s search functions address several key limitations that existed for text filtering: they work directly on multivalued fields, leverage analyzers for proper text analysis, and use optimized Lucene index structures for better performance. diff --git a/solutions/elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md b/solutions/search/full-text/create-update-synonyms-api-example.md similarity index 100% rename from solutions/elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md rename to solutions/search/full-text/create-update-synonyms-api-example.md diff --git a/solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md b/solutions/search/full-text/search-with-synonyms.md similarity index 100% rename from solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md rename to solutions/search/full-text/search-with-synonyms.md diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md index 5c7a211f6f..0fe91dbbde 100644 --- a/solutions/search/get-started.md +++ b/solutions/search/get-started.md @@ -9,12 +9,12 @@ products: - id: cloud-serverless --- -# Get started with search +# Get started with search primitives -This guide helps you get started with search using {{es}}, regardless of your deployment type. Whether you're using a self-managed cluster, {{ech}}, or an {{es}} serverless project, these universal search capabilities are available to you. +This guide helps you get started with search use cases using {{es}}, regardless of your deployment type. Whether you're using a self-managed cluster, {{ech}}, or an {{es}} serverless project, these core search primitives are available to you. ::::{tip} -Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for UI tools like Agent Builder, Playground, and Search Applications that complement these universal capabilities. +Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for UI tools like Agent Builder, Playground, and Search Applications that complement these core search primitives. :::: ## Before you begin diff --git a/solutions/security.md b/solutions/security.md index d4a1dd6f0a..24c8152740 100644 --- a/solutions/security.md +++ b/solutions/security.md @@ -1,5 +1,5 @@ --- -navigation_title: Security +navigation_title: Security solution mapped_pages: - https://www.elastic.co/guide/en/security/current/index.html - https://www.elastic.co/guide/en/security/current/es-overview.html @@ -16,7 +16,7 @@ products: description: Elastic Security combines threat detection analytics, cloud native security, and endpoint protection capabilities in a single solution. --- -# {{elastic-sec}} overview [es-overview] +# {{elastic-sec}} solution & project type overview [es-overview] :::{include} ../get-started/_snippets/security-overview.md ::: diff --git a/solutions/toc.yml b/solutions/toc.yml index b1174777f6..010b4e7939 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -18,6 +18,9 @@ toc: - file: search/full-text/search-relevance/mixing-exact-search-with-stemming.md - file: search/full-text/search-relevance/consistent-scoring.md - file: search/full-text/search-relevance/static-scoring-signals.md + - file: search/full-text/search-with-synonyms.md + children: + - file: search/full-text/create-update-synonyms-api-example.md - file: search/ai-search/ai-search.md children: - file: search/vector.md @@ -66,11 +69,11 @@ toc: - file: elasticsearch-solution-project/get-started.md children: - file: elasticsearch-solution-project/search-connection-details.md - - file: elasticsearch-solution-project/get-started/quickstarts.md - children: - - file: elasticsearch-solution-project/get-started/index-basics.md - - file: elasticsearch-solution-project/get-started/keyword-search-python.md - - file: elasticsearch-solution-project/get-started/semantic-search.md + - file: elasticsearch-solution-project/get-started/quickstarts.md + children: + - file: elasticsearch-solution-project/get-started/index-basics.md + - file: elasticsearch-solution-project/get-started/keyword-search-python.md + - file: elasticsearch-solution-project/get-started/semantic-search.md - file: elasticsearch-solution-project/elastic-agent-builder.md children: - file: elasticsearch-solution-project/agent-builder/get-started.md @@ -99,9 +102,6 @@ toc: - file: elasticsearch-solution-project/search-applications/search-application-api.md - file: elasticsearch-solution-project/search-applications/search-application-security.md - file: elasticsearch-solution-project/search-applications/search-application-client.md - - file: elasticsearch-solution-project/full-text/search-with-synonyms.md - children: - - file: elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md - file: elasticsearch-solution-project/ai-assistant.md - file: elasticsearch-solution-project/query-rules-ui.md - file: observability.md From ae00cdf3d38600d606cabed4f87848810f257780 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Tue, 9 Dec 2025 13:03:05 +0000 Subject: [PATCH 14/35] Add redirects for ES solution pages moved from Search MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit External repositories (kibana, elasticsearch, beats) still reference the old paths under solutions/search/. Add redirects for: - agent-builder pages - search-applications pages - query-rules-ui - search-connection-details 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- redirects.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/redirects.yml b/redirects.yml index 47fdd1fbc3..13fbe02a4b 100644 --- a/redirects.yml +++ b/redirects.yml @@ -2,6 +2,13 @@ redirects: # Search primitives moved from ES solution to Search use case 'solutions/elasticsearch-solution-project/full-text/search-with-synonyms.md': 'solutions/search/full-text/search-with-synonyms.md' 'solutions/elasticsearch-solution-project/full-text/create-update-synonyms-api-example.md': 'solutions/search/full-text/create-update-synonyms-api-example.md' + # ES solution pages moved from Search to ES solution + 'solutions/search/agent-builder/get-started.md': 'solutions/elasticsearch-solution-project/agent-builder/get-started.md' + 'solutions/search/elastic-agent-builder.md': 'solutions/elasticsearch-solution-project/elastic-agent-builder.md' + 'solutions/search/query-rules-ui.md': 'solutions/elasticsearch-solution-project/query-rules-ui.md' + 'solutions/search/search-applications.md': 'solutions/elasticsearch-solution-project/search-applications.md' + 'solutions/search/search-applications/search-application-client.md': 'solutions/elasticsearch-solution-project/search-applications/search-application-client.md' + 'solutions/search/search-connection-details.md': 'solutions/elasticsearch-solution-project/search-connection-details.md' 'deploy-manage/security/secure-http-communications.md': '!deploy-manage/security/secure-cluster-communications.md' 'deploy-manage/security/manually-configure-security-in-self-managed-cluster.md': '!deploy-manage/security/self-setup.md' 'deploy-manage/security/security-certificates-keys.md': '!deploy-manage/security/self-auto-setup.md' From cb7669a43193e839d70c3c2605e6c95f453f77f1 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Tue, 9 Dec 2025 13:10:19 +0000 Subject: [PATCH 15/35] Fix broken links with absolute paths MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use absolute paths throughout to make links resilient to future file moves: - Update search-templates.md references to use /solutions/search/ - Update querying-for-search.md references - Update knn.md references - Fix playground.md references (LLM guide, connectors) - Fix retrievers-overview.md playground reference - Fix search primitives link in elasticsearch-solution-project.md - Fix search-applications.md link in site-or-app.md - Fix deployment options and query languages links in get-started.md - Remove non-existent anchor reference in agent-builder/get-started.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- solutions/elasticsearch-solution-project.md | 2 +- .../agent-builder/get-started.md | 2 +- .../elasticsearch-solution-project/playground-query.md | 2 +- solutions/elasticsearch-solution-project/playground.md | 4 ++-- .../elasticsearch-solution-project/search-applications.md | 2 +- .../search-applications/search-application-api.md | 6 +++--- solutions/search/get-started.md | 4 ++-- solutions/search/retrievers-overview.md | 2 +- solutions/search/site-or-app.md | 2 +- 9 files changed, 13 insertions(+), 13 deletions(-) diff --git a/solutions/elasticsearch-solution-project.md b/solutions/elasticsearch-solution-project.md index ae89456992..a2364d802c 100644 --- a/solutions/elasticsearch-solution-project.md +++ b/solutions/elasticsearch-solution-project.md @@ -25,7 +25,7 @@ Not sure which deployment type is right for you? Use the following resources to The {{es}} solution and serverless project type provide specialized UI tools and interfaces that help you build search applications on top of the {{es}} platform. -These UI affordances are exclusive to the {{es}} **solution** (on non-serverless deployments) and the {{es}} serverless **project type**. They complement the core [search primitives]((/solutions/search.md)) available across all Elastic deployments. +These UI affordances are exclusive to the {{es}} **solution** (on non-serverless deployments) and the {{es}} serverless **project type**. They complement the core [search primitives](/solutions/search.md) available across all Elastic deployments. ## Features and tools diff --git a/solutions/elasticsearch-solution-project/agent-builder/get-started.md b/solutions/elasticsearch-solution-project/agent-builder/get-started.md index 07decf6bac..c575c69e49 100644 --- a/solutions/elasticsearch-solution-project/agent-builder/get-started.md +++ b/solutions/elasticsearch-solution-project/agent-builder/get-started.md @@ -15,7 +15,7 @@ Learn how to get started by enabling the {{agent-builder}} features and begin ch ::::::{stepper} ::::{step} Set up an Elastic deployment -If you don't already have an Elastic deployment, refer to [Select your deployment type](/solutions/search/get-started.md#choose-your-deployment-type). +If you don't already have an Elastic deployment, refer to [Get started with search](/solutions/search/get-started.md). :::{note} For {{ech}} deployments, make sure you are using the solution navigation instead of classic navigation. diff --git a/solutions/elasticsearch-solution-project/playground-query.md b/solutions/elasticsearch-solution-project/playground-query.md index 0c0f4e09ab..7b444e6a26 100644 --- a/solutions/elasticsearch-solution-project/playground-query.md +++ b/solutions/elasticsearch-solution-project/playground-query.md @@ -40,7 +40,7 @@ Remember that the next step in the workflow is to send the retrieved documents t [Troubleshooting](playground-troubleshooting.md) provides tips on how to diagnose and fix relevance issues. ::::{note} -Playground uses the [`retriever`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search#operation-search-body-application-json-retriever) syntax for {{es}} queries. Retrievers make it easier to compose and test different retrieval strategies in your search pipelines. Refer to [documentation](../querying-for-search.md) for a high level overview of retrievers. +Playground uses the [`retriever`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search#operation-search-body-application-json-retriever) syntax for {{es}} queries. Retrievers make it easier to compose and test different retrieval strategies in your search pipelines. Refer to [documentation](/solutions/search/querying-for-search.md) for a high level overview of retrievers. :::: diff --git a/solutions/elasticsearch-solution-project/playground.md b/solutions/elasticsearch-solution-project/playground.md index 1110510ec2..333f7a140f 100644 --- a/solutions/elasticsearch-solution-project/playground.md +++ b/solutions/elasticsearch-solution-project/playground.md @@ -102,7 +102,7 @@ To use Playground, you’ll need the following: You can also use locally hosted LLMs that are compatible with the OpenAI SDK. Once you’ve set up your LLM, you can connect to it using the OpenAI connector. Refer to the following for examples: -* [Using LM Studio](../../security/ai/connect-to-own-local-llm.md) +* [Using LM Studio](/solutions/security/ai/connect-to-own-local-llm.md) * [LocalAI with `docker-compose`](https://www.elastic.co/search-labs/blog/localai-for-text-embeddings) :::: @@ -116,7 +116,7 @@ You can also use locally hosted LLMs that are compatible with the OpenAI SDK. On ### Connect to LLM provider [playground-getting-started-connect] -To get started with Playground, you need to create a [connector](../../../deploy-manage/manage-connectors.md) for your LLM provider. By default, an Elastic Managed LLM is connected. You can also connect to [locally hosted LLMs](playground.md#playground-local-llms) which are compatible with the OpenAI API, by using the OpenAI connector. +To get started with Playground, you need to create a [connector](/deploy-manage/manage-connectors.md) for your LLM provider. By default, an Elastic Managed LLM is connected. You can also connect to [locally hosted LLMs](playground.md#playground-local-llms) which are compatible with the OpenAI API, by using the OpenAI connector. To connect to an LLM provider, use the following steps on the Playground landing page: diff --git a/solutions/elasticsearch-solution-project/search-applications.md b/solutions/elasticsearch-solution-project/search-applications.md index 426363cbb4..39f0348773 100644 --- a/solutions/elasticsearch-solution-project/search-applications.md +++ b/solutions/elasticsearch-solution-project/search-applications.md @@ -48,7 +48,7 @@ Managing search applications requires the `manage_search_application` cluster pr The {{es}} [Query DSL](../../explore-analyze/query-filter/languages/querydsl.md) is powerful and flexible, but it comes with a steep learning curve. Complex queries are verbose and hard to understand for non-experts. We’ve designed search applications to be easier to search over, but with the flexibility of working with an {{es}} index. -Search Applications use [search templates](search-templates.md) to simplify the process of building queries. Templates are defined when creating a search application, and can be customized according to your needs. Read [Search API and templates](search-applications/search-application-api.md) for the details. +Search Applications use [search templates](/solutions/search/search-templates.md) to simplify the process of building queries. Templates are defined when creating a search application, and can be customized according to your needs. Read [Search API and templates](search-applications/search-application-api.md) for the details. ## Get started [search-application-overview-get-started] diff --git a/solutions/elasticsearch-solution-project/search-applications/search-application-api.md b/solutions/elasticsearch-solution-project/search-applications/search-application-api.md index 932a7ff3bb..4b8cfb91ef 100644 --- a/solutions/elasticsearch-solution-project/search-applications/search-application-api.md +++ b/solutions/elasticsearch-solution-project/search-applications/search-application-api.md @@ -14,7 +14,7 @@ products: # Search API and templates [search-application-api] -Your [search applications](../search-applications.md) use [search templates](../search-templates.md) to perform searches. Templates help reduce complexity by exposing only template parameters, while using the full power of {{es}}'s query DSL to formulate queries. Templates may be set when creating or updating a search application, and can be customized. This template can be edited or updated at any time using the [Put Search Application API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search-application-put) API call. +Your [search applications](../search-applications.md) use [search templates](/solutions/search/search-templates.md) to perform searches. Templates help reduce complexity by exposing only template parameters, while using the full power of {{es}}'s query DSL to formulate queries. Templates may be set when creating or updating a search application, and can be customized. This template can be edited or updated at any time using the [Put Search Application API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search-application-put) API call. In a nutshell, you create search templates with parameters instead of specific hardcoded search values. At search time, you pass in the actual values for these parameters, enabling customized searches without rewriting the entire query structure. Search Application templates: @@ -27,7 +27,7 @@ This document provides information and sample templates to get you started using ::::{tip} Search templates use the [Mustache](https://mustache.github.io/) templating language. Mustache variables are typically enclosed in double curly brackets like this: `{{my-var}}`. -Learn more by reading about [search templates](../search-templates.md). +Learn more by reading about [search templates](/solutions/search/search-templates.md). :::: @@ -603,7 +603,7 @@ POST _application/search_application/my_search_application/_search ### kNN search [search-applications-knn-template] -This example supports [k-nearest neighbor (kNN) search](../vector/knn.md). +This example supports [k-nearest neighbor (kNN) search](/solutions/search/vector/knn.md). A template supporting exact kNN search will look like the following example: diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md index 0fe91dbbde..c8fa5b827a 100644 --- a/solutions/search/get-started.md +++ b/solutions/search/get-started.md @@ -21,7 +21,7 @@ Using the {{es}} solution or serverless project type? Check out the [{{es}} solu To follow along with this guide, you'll need: -- An {{es}} cluster or serverless project. [Create a deployment](/get-started/start-building.md) if you don't have one yet. +- An {{es}} cluster or serverless project. [Create a deployment](/get-started/deployment-options.md) if you don't have one yet. - Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. ## Quickstarts @@ -52,4 +52,4 @@ Once you're comfortable with the basics, explore different search techniques: - [{{es}} API documentation]({{es-apis}}) - [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) -- [Query languages](/explore-analyze/query-filter/languages/index.md) +- [Query languages](/explore-analyze/query-filter/languages.md) diff --git a/solutions/search/retrievers-overview.md b/solutions/search/retrievers-overview.md index 061b17c38f..c82a0c6dc0 100644 --- a/solutions/search/retrievers-overview.md +++ b/solutions/search/retrievers-overview.md @@ -139,7 +139,7 @@ The Search Playground builds Elasticsearch queries using the retriever abstracti You can use the Playground to experiment with different retriever configurations and see how they affect search results. -Refer to the [Playground documentation](rag/playground.md) for more information. +Refer to the [Playground documentation](/solutions/elasticsearch-solution-project/playground.md) for more information. ## Reference docs and examples [retrievers-overview-api-reference] diff --git a/solutions/search/site-or-app.md b/solutions/search/site-or-app.md index 24e99ceaf9..cacdb2441b 100644 --- a/solutions/search/site-or-app.md +++ b/solutions/search/site-or-app.md @@ -11,4 +11,4 @@ The following tools are available to help you add search to your site or app: - [Clients](site-or-app/clients.md): Use programming language clients to integrate {{es}} with your application. - [Search UI](site-or-app/search-ui.md): Use the Search UI library to build a user interface for your search application. -- [Search Applications](search-applications.md): Use Search Applications to simplify the process of building search experiences, by leveraging [search templates](search-templates.md). \ No newline at end of file +- [Search Applications](/solutions/elasticsearch-solution-project/search-applications.md): Use Search Applications to simplify the process of building search experiences, by leveraging [search templates](/solutions/search/search-templates.md). \ No newline at end of file From 369a369487ef09f7d1bc15261ebd692a025c6ced Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 11:33:11 +0000 Subject: [PATCH 16/35] Restore stepper format to Elasticsearch solution get-started page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reverted to stepper layout to align with other solution pages and maintain the golden path onboarding flow (deployment → data → search). Incorporated new content about solution-specific features while preserving core journey. Changes: - Restored 6-step stepper format with deployment, quickstarts, goals, data, queries, and features - Moved quickstarts to optional step 2 for early hands-on experience - Added "Explore solution features" as final step (Agent Builder, Query Rules UI, synonyms) - Preserved original version as original-get-started.md for reference - Updated metadata to match original (navigation_title, description, applies_to) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../get-started.md | 104 +++++++++++------- .../original-get-started.md | 88 +++++++++++++++ 2 files changed, 155 insertions(+), 37 deletions(-) create mode 100644 solutions/elasticsearch-solution-project/original-get-started.md diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index 7759470e7a..08321842f2 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -5,68 +5,98 @@ mapped_pages: applies_to: stack: serverless: + elasticsearch: all products: - id: elasticsearch - id: cloud-serverless - - id: kibana +navigation_title: Get started +description: To try out an {{es}} project or solution, pick your deployment type, search goals, and ingestion method. --- -# Get started with the {{es}} solution +# Get started with the {{es}} solution/project type -This guide helps you get started with the {{es}} solution and serverless project type, including the specialized UI tools and interfaces available exclusively in this environment. +New to {{es}}? Start building a search experience by setting up your first deployment, refining your search goals, and adding data. -::::{tip} -New to {{es}} search capabilities? Start with the [Search use case documentation](/solutions/search.md) to learn about universal {{es}} search primitives like full-text search, vector search, and hybrid search that work across all deployment types. -:::: +:::{note} +If you're looking for an introduction to the {{stack}} or the {{es}} product, go to [](/get-started/index.md) or [](/manage-data/data-store.md). +::: -## Before you begin +::::::{stepper} +:::::{step} Choose your deployment type -To use the {{es}} solution, you'll need: +Elastic provides several self-managed and Elastic-managed options. +For simplicity and speed, try out {{es-serverless}}: -- An {{es}} solution deployment on {{ech}} or an {{es}} serverless project -- Access to {{kib}} for using the UI tools -- Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. +::::{dropdown} Create an {{es-serverless}} project +:::{include} /deploy-manage/deploy/_snippets/create-serverless-project-intro.md +::: -## Quickstarts +Choose the {{es}} project type and provide a name. +You can optionally edit the project settings, such as the [region](/deploy-manage/deploy/elastic-cloud/regions.md). -Get hands-on experience with {{es}} using these guided tutorials: +When your project is created, you're ready to move on to the next step and to start creating indices, adding data, and performing searches. +:::: -- [**Index basics**](/solutions/elasticsearch-solution-project/get-started/index-basics.md): Learn how to create indices, add documents, and perform searches. -- [**Keyword search with Python**](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md): Build a keyword search application. -- [**Semantic search**](/solutions/elasticsearch-solution-project/get-started/semantic-search.md): Implement semantic search using embeddings. +Alternatively, create a [local development installation](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md) in Docker: -## Explore {{es}} solution features +```sh +curl -fsSL https://elastic.co/start-local | sh +``` -The {{es}} solution provides specialized UI tools to enhance your search experience: +Check out the full list of [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) to learn more. +::::: -### Agent Builder +:::::{step} (Optional) Try out a quickstart -Create AI agents that interact with your {{es}} data. Refer to [Agent Builder](/solutions/elasticsearch-solution-project/elastic-agent-builder.md) to get started. +Get hands-on experience with {{es}} using guided tutorials that walk you through common search scenarios: -### Playground +- [**Index and search basics**](/solutions/elasticsearch-solution-project/get-started/index-basics.md): Learn how to create indices, add documents, and perform searches +- [**Keyword search with Python**](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md): Build your first search query with Python +- [**Semantic search**](/solutions/elasticsearch-solution-project/get-started/semantic-search.md): Implement semantic search using embeddings +::::: -Test and explore RAG (Retrieval Augmented Generation) workflows using the interactive Playground interface. Refer to [Playground](/solutions/elasticsearch-solution-project/playground.md) to learn more. +:::::{step} Identify your search goals +Depending on your use case, you can choose multiple [search approaches](/solutions/search/search-approaches.md), for example full-text and semantic search. +Each approach affects your options for storing and querying your data. -### Search Applications +If you're unsure which approaches match your goals, you can try them out with sample data. For example, [](/solutions/elasticsearch-solution-project/get-started/semantic-search.md). -Manage and deploy search-powered applications with pre-built templates. Refer to [Search Applications](/solutions/elasticsearch-solution-project/search-applications.md) for details. +If you prefer to ingest your data first and transform or reindex it as needed later, skip to the next step. +::::: +:::::{step} Ingest your data -### UI tools for search optimization +If your goals include vector or semantic AI-powered search, create vectorized data with built-in and third-party natural language processing (NLP) models and store it in an {{es}} vector database. +The approach that requires the least configuration involves adding `semantic_text` fields when ingesting your data. +This method is described in [](/solutions/search/semantic-search/semantic-search-semantic-text.md). -- [**Search with synonyms**](/solutions/search/full-text/search-with-synonyms.md): Manage synonym sets through the UI -- [**Query Rules UI**](/solutions/elasticsearch-solution-project/query-rules-ui.md): Create rules to modify search behavior -- [**AI Assistant**](/solutions/elasticsearch-solution-project/ai-assistant.md): Get intelligent assistance across the platform +To learn about adding data for other search goals, go to [](/solutions/search/ingest-for-search.md). +For a broader overview of ingestion options, go to [](/manage-data/ingest.md). + +If you're not ready to add your own data, you can use [sample data](/manage-data/ingest/sample-data.md) or create small data sets when you follow the instructions in the [quickstarts](/solutions/elasticsearch-solution-project/get-started/quickstarts.md). + +The {{es}} home page in the UI also provides workflow guides for creating indices and ready-to-use code examples for ingesting data by using REST APIs. +::::: +:::::{step} Build your search queries -## Next steps +Your next steps will be to choose a method to write queries and interact with {{es}}. +You can pick a programming language [client](/reference/elasticsearch-clients/index.md) that matches your application and choose which [query languages](/solutions/search/querying-for-search.md) you will use to express your search logic. +Each decision builds on the previous ones, offering flexibility to mix and match approaches based on your needs. +::::: -- Learn about [search techniques and approaches](/solutions/search/search-approaches.md) in the Search use case documentation -- Explore [RAG concepts](/solutions/search/rag.md) to understand how Playground leverages retrieval augmented generation -- Discover [ingestion methods](/solutions/search/ingest-for-search.md) for preparing your data -- Understand [ranking strategies](/solutions/search/ranking.md) to improve search relevance +:::::{step} Explore solution features + +The {{es}} solution provides specialized UI tools to enhance your search experience: + +- [**Agent Builder**](/solutions/elasticsearch-solution-project/elastic-agent-builder.md): Create AI agents that interact with your {{es}} data +- [**Query Rules UI**](/solutions/elasticsearch-solution-project/query-rules-ui.md): Create rules to modify search behavior +- [**Search with synonyms**](/solutions/search/full-text/search-with-synonyms.md): Manage synonym sets through the UI +::::: ## Related resources -- [{{es}} solution overview](/solutions/elasticsearch-solution-project.md) -- [Search use case documentation](/solutions/search.md) -- [{{es}} API documentation]({{es-apis}}) -- [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) +Use these resources to learn more about {{es}} or get started in a different way: + +- [](/deploy-manage/deploy/deployment-comparison.md) +- [Get started with Query DSL search and filters](elasticsearch://reference/query-languages/query-dsl/full-text-filter-tutorial.md) +- [Get started with ES|QL queries](elasticsearch://reference/query-languages/esql/esql-getting-started.md) +- [Analyze eCommerce data with aggregations using Query DSL](/explore-analyze/query-filter/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md) diff --git a/solutions/elasticsearch-solution-project/original-get-started.md b/solutions/elasticsearch-solution-project/original-get-started.md new file mode 100644 index 0000000000..42148a7a0c --- /dev/null +++ b/solutions/elasticsearch-solution-project/original-get-started.md @@ -0,0 +1,88 @@ +--- +mapped_pages: + - https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started.html + - https://www.elastic.co/guide/en/serverless/current/elasticsearch-get-started.html +applies_to: + stack: + serverless: + elasticsearch: all +products: + - id: elasticsearch + - id: cloud-serverless +navigation_title: Get started +description: To try out an {{es}} project or solution, pick your deployment type, search goals, and ingestion method. +--- + +# Get started with {{es}} + +New to {{es}}? Start building a search experience by setting up your first deployment, refining your search goals, and adding data. + +:::{note} +If you're looking for an introduction to the {{stack}} or the {{es}} product, go to [](/get-started/index.md) or [](/manage-data/data-store.md). +::: + +::::::{stepper} +:::::{step} Choose your deployment type + +Elastic provides several self-managed and Elastic-managed options. +For simplicity and speed, try out {{es-serverless}}: + +::::{dropdown} Create an {{es-serverless}} project +:::{include} /deploy-manage/deploy/_snippets/create-serverless-project-intro.md +::: + +Choose the {{es}} project type and provide a name. +You can optionally edit the project settings, such as the [region](/deploy-manage/deploy/elastic-cloud/regions.md). + +When your project is created, you're ready to move on to the next step and to start creating indices, adding data, and performing searches. +:::: + +Alternatively, create a [local development installation](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md) in Docker: + +```sh +curl -fsSL https://elastic.co/start-local | sh +``` + +Check out the full list of [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) to learn more. +::::: + +:::::{step} Identify your search goals +Depending on your use case, you can choose multiple [search approaches](search-approaches.md), for example full-text and semantic search. +Each approach affects your options for storing and querying your data. + +If you're unsure which approaches match your goals, you can try them out with sample data. For example, [](/solutions/search/get-started/semantic-search.md). + +If you prefer to ingest your data first and transform or reindex it as needed later, skip to the next step. +::::: +:::::{{step}} Ingest your data + +If your goals include vector or semantic AI-powered search, create vectorized data with built-in and third-party natural language processing (NLP) models and store it in an {{es}} vector database. +The approach that requires the least configuration involves adding `semantic_text` fields when ingesting your data. +This method is described in [](/solutions/search/semantic-search/semantic-search-semantic-text.md). + +To learn about adding data for other search goals, go to [](/solutions/search/ingest-for-search.md). +For a broader overview of ingestion options, go to [](/manage-data/ingest.md). + +If you're not ready to add your own data, you can use [sample data](/manage-data/ingest/sample-data.md) or create small data sets when you follow the instructions in the [quickstarts](/solutions/search/get-started/quickstarts.md). + +The {{es}} home page in the UI also provides workflow guides for creating indices and ready-to-use code examples for ingesting data by using REST APIs. +::::: +:::::{{step}} Build your search queries + +Your next steps will be to choose a method to write queries and interact with {{es}}. +You can pick a programming language [client](/reference/elasticsearch-clients/index.md) that matches your application and choose which [query languages](/solutions/search/querying-for-search.md) you will use to express your search logic. +Each decision builds on the previous ones, offering flexibility to mix and match approaches based on your needs. + +Not sure where to start exploring? +Get an introduction to [index and search basics](/solutions/search/get-started/index-basics.md) or [build your first search query with Python](/solutions/search/get-started/keyword-search-python.md). +::::: +:::::: + +## Related resources + +Use these resources to learn more about {{es}} or get started in a different way: + +- [](/deploy-manage/deploy/deployment-comparison.md) +- [Get started with Query DSL search and filters](elasticsearch://reference/query-languages/query-dsl/full-text-filter-tutorial.md) +- [Get started with ES|QL queries](elasticsearch://reference/query-languages/esql/esql-getting-started.md) +- [Analyze eCommerce data with aggregations using Query DSL](/explore-analyze/query-filter/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md) From 0a97210318bbe7275fef628229c971629cda7be4 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 11:37:26 +0000 Subject: [PATCH 17/35] delete temp file --- .../original-get-started.md | 88 ------------------- 1 file changed, 88 deletions(-) delete mode 100644 solutions/elasticsearch-solution-project/original-get-started.md diff --git a/solutions/elasticsearch-solution-project/original-get-started.md b/solutions/elasticsearch-solution-project/original-get-started.md deleted file mode 100644 index 42148a7a0c..0000000000 --- a/solutions/elasticsearch-solution-project/original-get-started.md +++ /dev/null @@ -1,88 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started.html - - https://www.elastic.co/guide/en/serverless/current/elasticsearch-get-started.html -applies_to: - stack: - serverless: - elasticsearch: all -products: - - id: elasticsearch - - id: cloud-serverless -navigation_title: Get started -description: To try out an {{es}} project or solution, pick your deployment type, search goals, and ingestion method. ---- - -# Get started with {{es}} - -New to {{es}}? Start building a search experience by setting up your first deployment, refining your search goals, and adding data. - -:::{note} -If you're looking for an introduction to the {{stack}} or the {{es}} product, go to [](/get-started/index.md) or [](/manage-data/data-store.md). -::: - -::::::{stepper} -:::::{step} Choose your deployment type - -Elastic provides several self-managed and Elastic-managed options. -For simplicity and speed, try out {{es-serverless}}: - -::::{dropdown} Create an {{es-serverless}} project -:::{include} /deploy-manage/deploy/_snippets/create-serverless-project-intro.md -::: - -Choose the {{es}} project type and provide a name. -You can optionally edit the project settings, such as the [region](/deploy-manage/deploy/elastic-cloud/regions.md). - -When your project is created, you're ready to move on to the next step and to start creating indices, adding data, and performing searches. -:::: - -Alternatively, create a [local development installation](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md) in Docker: - -```sh -curl -fsSL https://elastic.co/start-local | sh -``` - -Check out the full list of [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) to learn more. -::::: - -:::::{step} Identify your search goals -Depending on your use case, you can choose multiple [search approaches](search-approaches.md), for example full-text and semantic search. -Each approach affects your options for storing and querying your data. - -If you're unsure which approaches match your goals, you can try them out with sample data. For example, [](/solutions/search/get-started/semantic-search.md). - -If you prefer to ingest your data first and transform or reindex it as needed later, skip to the next step. -::::: -:::::{{step}} Ingest your data - -If your goals include vector or semantic AI-powered search, create vectorized data with built-in and third-party natural language processing (NLP) models and store it in an {{es}} vector database. -The approach that requires the least configuration involves adding `semantic_text` fields when ingesting your data. -This method is described in [](/solutions/search/semantic-search/semantic-search-semantic-text.md). - -To learn about adding data for other search goals, go to [](/solutions/search/ingest-for-search.md). -For a broader overview of ingestion options, go to [](/manage-data/ingest.md). - -If you're not ready to add your own data, you can use [sample data](/manage-data/ingest/sample-data.md) or create small data sets when you follow the instructions in the [quickstarts](/solutions/search/get-started/quickstarts.md). - -The {{es}} home page in the UI also provides workflow guides for creating indices and ready-to-use code examples for ingesting data by using REST APIs. -::::: -:::::{{step}} Build your search queries - -Your next steps will be to choose a method to write queries and interact with {{es}}. -You can pick a programming language [client](/reference/elasticsearch-clients/index.md) that matches your application and choose which [query languages](/solutions/search/querying-for-search.md) you will use to express your search logic. -Each decision builds on the previous ones, offering flexibility to mix and match approaches based on your needs. - -Not sure where to start exploring? -Get an introduction to [index and search basics](/solutions/search/get-started/index-basics.md) or [build your first search query with Python](/solutions/search/get-started/keyword-search-python.md). -::::: -:::::: - -## Related resources - -Use these resources to learn more about {{es}} or get started in a different way: - -- [](/deploy-manage/deploy/deployment-comparison.md) -- [Get started with Query DSL search and filters](elasticsearch://reference/query-languages/query-dsl/full-text-filter-tutorial.md) -- [Get started with ES|QL queries](elasticsearch://reference/query-languages/esql/esql-getting-started.md) -- [Analyze eCommerce data with aggregations using Query DSL](/explore-analyze/query-filter/aggregations/tutorial-analyze-ecommerce-data-with-aggregations-using-query-dsl.md) From 1b59a932ac74dc28c59dad9d1fc4b2ceffd3cca2 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 11:43:52 +0000 Subject: [PATCH 18/35] tweak verbiage --- solutions/elasticsearch-solution-project/get-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index 08321842f2..bd4d0fec3d 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -85,7 +85,7 @@ Each decision builds on the previous ones, offering flexibility to mix and match :::::{step} Explore solution features -The {{es}} solution provides specialized UI tools to enhance your search experience: +The {{es}} solution provides additional UI tools on top of the core {{es}} capabilities, to help you build search applications: - [**Agent Builder**](/solutions/elasticsearch-solution-project/elastic-agent-builder.md): Create AI agents that interact with your {{es}} data - [**Query Rules UI**](/solutions/elasticsearch-solution-project/query-rules-ui.md): Create rules to modify search behavior From 0e687bf6d3138a15a0ac4bc318be2442ea13ac15 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 12:38:41 +0000 Subject: [PATCH 19/35] refactor the solutions-use-cases landing page --- solutions/index.md | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/solutions/index.md b/solutions/index.md index fe72e53786..f2a0347866 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -17,23 +17,22 @@ description: Learn about Elastic solutions for search, observability, and securi New to Elastic? Refer to [Elastic Fundamentals](/get-started/index.md) to understand the {{stack}}, its components, and your deployment options. ::: -Users reach for Elastic products, features, and tools for three main use cases: observability, security, and search. +Elastic helps you build applications for three main use cases: search, observability, and security. You can use platform-level capabilities through APIs, pre-built solutions with integrated UIs, or combine both approaches. -These use cases are supported by ready-to-use implementations that help you get started quickly: +The documentation is organized to distinguish between platform-level search capabilities available to all deployments and solution-specific features and workflows. -- As integrated solutions on [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) and [self-managed](/deploy-manage/deploy/self-managed.md) deployments -- As project types on [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md) +## Search use case -While these solutions and project types provide pre-built components for common use cases, you can also build custom implementations using Elastic's features, APIs, and tools. This documentation guides you through: +The [Search use case](/solutions/search.md) documents core {{es}} search capabilities. These capabilities work identically across all Elastic [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) and are accessed through {{es}} APIs and client libraries. You can build custom implementations using Elastic's APIs and features without using solutions. -1. Evaluating if an Elastic solution fits your needs. -2. Getting started with your chosen solution. -3. Implementing specific features and capabilities. +## Solutions and project types -Learn more in the following sections: +Solutions and project types provide pre-built UI tools and workflows for specific use cases. Rather than building everything through APIs, solutions give you prebuilt interfaces for common workflows and sensible defaults. -| Solution | Use case | -| --- | --- | -| [Elasticsearch](search.md) | Build search experiences, or implement custom use cases with {{es}} -| [Observability](observability.md) | Monitor and troubleshoot applications and infrastructure with {{product.observability}} -| [Security](security.md) | Protect applications and infrastructure with {{elastic-sec}} +On {{ech}} and self-managed deployments, solutions are configured in your deployment settings. On {{serverless-full}}, you select a project type when creating your project. + +| Solution/Project | Description | Get started | +| --- | --- | --- | +| **Elasticsearch** | UI tools for building search applications | [Elasticsearch solution](/solutions/elasticsearch-solution-project.md) | +| **Observability** | Monitor and troubleshoot applications and infrastructure | [Observability solution](/solutions/observability.md) | +| **Security** | Protect applications and infrastructure from threats | [Security solution](/solutions/security.md) | From 1be8f3f656bb354c586176cb74db874d1e076e5d Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 12:59:14 +0000 Subject: [PATCH 20/35] less repetition --- solutions/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/index.md b/solutions/index.md index f2a0347866..9b97886cfe 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -27,7 +27,7 @@ The [Search use case](/solutions/search.md) documents core {{es}} search capabil ## Solutions and project types -Solutions and project types provide pre-built UI tools and workflows for specific use cases. Rather than building everything through APIs, solutions give you prebuilt interfaces for common workflows and sensible defaults. +Solutions and project types provide pre-built UI tools and workflows with sensible defaults for specific use cases. On {{ech}} and self-managed deployments, solutions are configured in your deployment settings. On {{serverless-full}}, you select a project type when creating your project. From 817c0b2d9800823aec1f4c16f7963d83b795bb01 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:11:07 +0000 Subject: [PATCH 21/35] tighten up --- solutions/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/solutions/index.md b/solutions/index.md index 9b97886cfe..62c905c262 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -19,17 +19,17 @@ New to Elastic? Refer to [Elastic Fundamentals](/get-started/index.md) to unders Elastic helps you build applications for three main use cases: search, observability, and security. You can use platform-level capabilities through APIs, pre-built solutions with integrated UIs, or combine both approaches. -The documentation is organized to distinguish between platform-level search capabilities available to all deployments and solution-specific features and workflows. - ## Search use case The [Search use case](/solutions/search.md) documents core {{es}} search capabilities. These capabilities work identically across all Elastic [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) and are accessed through {{es}} APIs and client libraries. You can build custom implementations using Elastic's APIs and features without using solutions. ## Solutions and project types -Solutions and project types provide pre-built UI tools and workflows with sensible defaults for specific use cases. +Solutions and project types provide pre-built UI tools and workflows with sensible defaults for specific use cases, which build on top of the core platform capabilities. These help you get started quickly with common implementations and can be customized to meet your specific needs. + +On {{serverless-full}}, you select a project type when creating your project. -On {{ech}} and self-managed deployments, solutions are configured in your deployment settings. On {{serverless-full}}, you select a project type when creating your project. +On non-serverless deployments, solutions are configured in your deployment settings. | Solution/Project | Description | Get started | | --- | --- | --- | From ae1a36180a8506ce01b0be19318c9253fc0f2c8a Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:13:02 +0000 Subject: [PATCH 22/35] de-emphasize search applications --- solutions/elasticsearch-solution-project.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/solutions/elasticsearch-solution-project.md b/solutions/elasticsearch-solution-project.md index a2364d802c..b7892b9c3c 100644 --- a/solutions/elasticsearch-solution-project.md +++ b/solutions/elasticsearch-solution-project.md @@ -39,10 +39,6 @@ The {{es}} solution provides the following specialized UI tools: [Playground](/solutions/elasticsearch-solution-project/playground.md) lets you use large language models (LLMs) to understand, explore, and analyze your {{es}} data using retrieval augmented generation (RAG), via a chat interface. Playground is also useful for testing and debugging your {{es}} queries using the [retrievers](/solutions/search/retrievers-overview.md) syntax. -### Search Applications - -[Search Applications](/solutions/elasticsearch-solution-project/search-applications.md) provide a simplified way to manage and access your search use cases through a unified interface. They enable you to create, configure, and manage search-powered applications with built-in templates and best practices. - ### Synonyms UI The [Search with synonyms](/solutions/search/full-text/search-with-synonyms.md) interface provides a dedicated UI for managing synonym sets directly within {{kib}}, making it easier to improve search relevance without editing configuration files. From 471b25401a2b160c107b27447d774fd9bf45c032 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:18:25 +0000 Subject: [PATCH 23/35] clarify verbiage --- solutions/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/solutions/index.md b/solutions/index.md index 62c905c262..ea6db63eac 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -25,7 +25,9 @@ The [Search use case](/solutions/search.md) documents core {{es}} search capabil ## Solutions and project types -Solutions and project types provide pre-built UI tools and workflows with sensible defaults for specific use cases, which build on top of the core platform capabilities. These help you get started quickly with common implementations and can be customized to meet your specific needs. +Solutions are available as a fully managed Serverless project, a managed service on Elastic Cloud Hosted, or a self-managed deployment. + +Solutions provide pre-built UI tools and workflows with sensible defaults for specific use cases, which build on top of the core platform capabilities. These help you get started quickly with common implementations and can be customized to meet your specific needs. On {{serverless-full}}, you select a project type when creating your project. From 752a53e7ca5562b6a357385457447f0b5676a528 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:21:26 +0000 Subject: [PATCH 24/35] better words --- solutions/search.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/search.md b/solutions/search.md index c2b424cb6d..0aa0ddb4ae 100644 --- a/solutions/search.md +++ b/solutions/search.md @@ -17,7 +17,7 @@ This section documents {{es}} search primitives. These capabilities that are ava Use this section to understand search techniques, query methods, ranking strategies, and data ingestion for search applications. ::::{tip} -Using the {{es}} solution or serverless project type? The {{es}} solution documentation covers exclusive UI tools (Agent Builder, Playground, Search Applications) that complement these search primitives. Refer to [](/solutions/elasticsearch-solution-project.md) for more details. +Using the {{es}} solution or serverless project type? The {{es}} solution documentation covers additional UI tools that complement these search primitives. Refer to [](/solutions/elasticsearch-solution-project.md) for more details. :::: ## What you can build From 3893f33c0a5d8b2978cad0f8a14a30451fd951c8 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:36:07 +0000 Subject: [PATCH 25/35] rework use case landing page --- solutions/search.md | 32 ++++++++++++++++++++++++-------- 1 file changed, 24 insertions(+), 8 deletions(-) diff --git a/solutions/search.md b/solutions/search.md index 0aa0ddb4ae..fbda938aa1 100644 --- a/solutions/search.md +++ b/solutions/search.md @@ -22,14 +22,30 @@ Using the {{es}} solution or serverless project type? The {{es}} solution docume ## What you can build -| Application type | Search technique | Key primitives | Documentation | -|-----------------|------------------|----------------|---------------| -| **Website/documentation search** | Text matching with relevance scoring | Full-text search, analyzers, scoring functions | [Full-text search](/solutions/search/full-text.md), [Ranking](/solutions/search/ranking.md) | -| **Ecommerce product catalogs** | Text + filters + facets | Hybrid search, aggregations, boosting | [Hybrid search](/solutions/search/hybrid-search.md), [Ranking](/solutions/search/ranking.md) | -| **Semantic/similarity search** | Embedding-based retrieval | Vector search, dense/sparse vectors, kNN | [Vector search](/solutions/search/vector.md), [Semantic search](/solutions/search/semantic-search.md) | -| **RAG applications** | Retrieval for LLM context | Retrievers, embedding models, ranking, query methods | [RAG](/solutions/search/rag.md), [Querying](/solutions/search/querying-for-search.md), [Retrievers](/solutions/search/retrievers-overview.md), [Semantic search](/solutions/search/semantic-search.md), [Ranking](/solutions/search/ranking.md) | -| **Geospatial applications** | Location-based queries | Geo-point, geo-shape fields, distance sorting | [Geospatial search](elasticsearch://reference/elasticsearch/mapping-reference/geo-point.md) | -| **Federated search** | Querying multiple clusters | Remote cluster connections, distributed queries | [Cross-cluster search](/solutions/search/cross-cluster-search.md) | +Use {{es}} search primitives to build search applications including: + +- Website and documentation search +- Ecommerce product catalogs +- Content recommendation systems +- RAG (Retrieval Augmented Generation) systems +- Geospatial search applications +- Question answering systems +- Custom observability or cybersecurity search tools +- Much more! + +## Topics + +The following topics are covered in this section: + +| Topic | Description | +|-------|-------------| +| [**Get started**](/solutions/search/get-started.md) | Create deployments, connect to {{es}}, and run your first searches | +| [**Ingest data**](/solutions/search/ingest-for-search.md) | Options for getting data into {{es}} | +| [**Search approaches**](/solutions/search/search-approaches.md) | Compare full-text, vector, semantic, and hybrid search techniques | +| [**Build your queries**](/solutions/search/querying-for-search.md) | Implement your search approaches using specific query languages | +| [**Ranking and reranking**](/solutions/search/ranking.md) | Control result ordering and relevance | +| [**RAG**](/solutions/search/rag.md) | Learn about tools for retrieval augmented generation with {{es}}| +| [**Building applications**](/solutions/search/site-or-app.md) | Integrate {{es}} into your websites or applications | ## Core concepts [search-concepts] From 58db21a705ed29e77b657011e58b21e145a94d5d Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 13:39:05 +0000 Subject: [PATCH 26/35] update related links --- solutions/elasticsearch-solution-project.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/solutions/elasticsearch-solution-project.md b/solutions/elasticsearch-solution-project.md index b7892b9c3c..a811b8c771 100644 --- a/solutions/elasticsearch-solution-project.md +++ b/solutions/elasticsearch-solution-project.md @@ -63,7 +63,6 @@ For a deeper understanding of search concepts and techniques, refer to the [Sear ## Related reference +* [Search use case documentation](/solutions/search.md) * [{{es}} reference documentation](elasticsearch://reference/elasticsearch/index.md) -* [Content connectors](elasticsearch://reference/search-connectors/index.md) * [{{es}} API documentation]({{es-apis}}) -* [Search use case documentation](/solutions/search.md) \ No newline at end of file From 45f2b6228208e9595fafdeec7ff845171537de5f Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 14:24:45 +0000 Subject: [PATCH 27/35] reword --- solutions/index.md | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/solutions/index.md b/solutions/index.md index ea6db63eac..72f88fc567 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -17,24 +17,25 @@ description: Learn about Elastic solutions for search, observability, and securi New to Elastic? Refer to [Elastic Fundamentals](/get-started/index.md) to understand the {{stack}}, its components, and your deployment options. ::: -Elastic helps you build applications for three main use cases: search, observability, and security. You can use platform-level capabilities through APIs, pre-built solutions with integrated UIs, or combine both approaches. +Elastic helps you build applications for three main use cases: search, observability, and security. You can work directly with platform capabilities through APIs, use pre-built solutions with integrated UIs, or combine both approaches. -## Search use case +This section is organized into two parts: -The [Search use case](/solutions/search.md) documents core {{es}} search capabilities. These capabilities work identically across all Elastic [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type) and are accessed through {{es}} APIs and client libraries. You can build custom implementations using Elastic's APIs and features without using solutions. +- [**Search use case**](#search-use-case): Core {{es}} features accessed through APIs and client libraries, available across all [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type). Use these when you need programmatic control or the flexibility to build custom applications. +- [**Solutions and project types**](#solutions-and-project-types): Pre-built UI tools and workflows for specific use cases, available on {{serverless-full}} as project types or on other deployments as solutions. Use these to get started quickly with pre-configured workflows, sensible defaults, and tailored UI affordances. -## Solutions and project types +## Search use case -Solutions are available as a fully managed Serverless project, a managed service on Elastic Cloud Hosted, or a self-managed deployment. +The [Search use case](/solutions/search.md) documents core {{es}} search capabilities available across all Elastic [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type). -Solutions provide pre-built UI tools and workflows with sensible defaults for specific use cases, which build on top of the core platform capabilities. These help you get started quickly with common implementations and can be customized to meet your specific needs. +## Solutions and project types -On {{serverless-full}}, you select a project type when creating your project. +Solutions provide integrated UI tools and workflows with sensible defaults, in addition to core platform capabilities. They help you get started quickly with common use cases. -On non-serverless deployments, solutions are configured in your deployment settings. +On {{serverless-full}}, select a project type when creating a project. On {{ech}} or self-managed deployments, configure solutions in deployment settings. -| Solution/Project | Description | Get started | -| --- | --- | --- | -| **Elasticsearch** | UI tools for building search applications | [Elasticsearch solution](/solutions/elasticsearch-solution-project.md) | -| **Observability** | Monitor and troubleshoot applications and infrastructure | [Observability solution](/solutions/observability.md) | -| **Security** | Protect applications and infrastructure from threats | [Security solution](/solutions/security.md) | +| Solution/Project | Description | +| --- | --- | +| [**Elasticsearch**](/solutions/elasticsearch-solution-project.md) | UI tools for building search applications: Agent Builder, Playground, Search Applications, Query Rules | +| [**Observability**](/solutions/observability.md) | Monitor and troubleshoot applications and infrastructure | +| [**Security**](/solutions/security.md) | Protect applications and infrastructure from threats | From 60583fc837dc2e8932bd51cec576d7b4459289fd Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 14:38:07 +0000 Subject: [PATCH 28/35] restore better wording --- solutions/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/solutions/index.md b/solutions/index.md index 72f88fc567..fc11c215a1 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -32,7 +32,9 @@ The [Search use case](/solutions/search.md) documents core {{es}} search capabil Solutions provide integrated UI tools and workflows with sensible defaults, in addition to core platform capabilities. They help you get started quickly with common use cases. -On {{serverless-full}}, select a project type when creating a project. On {{ech}} or self-managed deployments, configure solutions in deployment settings. +Solutions are available as a fully managed {{serverless-short}} project, a managed service on {{ech}}, or a self-managed deployment: +- On {{serverless-full}}, you select a project type when creating your project. +- On non-serverless deployments, solution views are configured per [space](/deploy-manage/manage-spaces.md). | Solution/Project | Description | | --- | --- | From be72056ee4bdc5757a53caf3da3ca2bdfe7f0c67 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 10 Dec 2025 14:43:56 +0000 Subject: [PATCH 29/35] fix table --- solutions/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/index.md b/solutions/index.md index fc11c215a1..0be1c217e6 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -38,6 +38,6 @@ Solutions are available as a fully managed {{serverless-short}} project, a manag | Solution/Project | Description | | --- | --- | -| [**Elasticsearch**](/solutions/elasticsearch-solution-project.md) | UI tools for building search applications: Agent Builder, Playground, Search Applications, Query Rules | +| [**Elasticsearch**](/solutions/elasticsearch-solution-project.md) | UI tools for building search applications | | [**Observability**](/solutions/observability.md) | Monitor and troubleshoot applications and infrastructure | | [**Security**](/solutions/security.md) | Protect applications and infrastructure from threats | From 337360f5dded76e237def24a59d1eaad2e67ca00 Mon Sep 17 00:00:00 2001 From: Liam Thompson Date: Thu, 11 Dec 2025 12:10:23 +0000 Subject: [PATCH 30/35] Apply suggestions Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- solutions/elasticsearch-solution-project/playground-query.md | 2 +- solutions/search.md | 4 ++-- solutions/search/get-started.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/solutions/elasticsearch-solution-project/playground-query.md b/solutions/elasticsearch-solution-project/playground-query.md index 7b444e6a26..801277c2ff 100644 --- a/solutions/elasticsearch-solution-project/playground-query.md +++ b/solutions/elasticsearch-solution-project/playground-query.md @@ -40,7 +40,7 @@ Remember that the next step in the workflow is to send the retrieved documents t [Troubleshooting](playground-troubleshooting.md) provides tips on how to diagnose and fix relevance issues. ::::{note} -Playground uses the [`retriever`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search#operation-search-body-application-json-retriever) syntax for {{es}} queries. Retrievers make it easier to compose and test different retrieval strategies in your search pipelines. Refer to [documentation](/solutions/search/querying-for-search.md) for a high level overview of retrievers. +Playground uses the [`retriever`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-search#operation-search-body-application-json-retriever) syntax for {{es}} queries. Retrievers make it easier to compose and test different retrieval strategies in your search pipelines. Refer to [](/solutions/search/querying-for-search.md) for a high level overview of retrievers. :::: diff --git a/solutions/search.md b/solutions/search.md index fbda938aa1..e667af7b6d 100644 --- a/solutions/search.md +++ b/solutions/search.md @@ -12,7 +12,7 @@ navigation_title: Search use case # Search use case -This section documents {{es}} search primitives. These capabilities that are available across all Elastic deployments. +This section documents {{es}} search primitives. These capabilities are available across all Elastic deployments. Use this section to understand search techniques, query methods, ranking strategies, and data ingestion for search applications. @@ -41,7 +41,7 @@ The following topics are covered in this section: |-------|-------------| | [**Get started**](/solutions/search/get-started.md) | Create deployments, connect to {{es}}, and run your first searches | | [**Ingest data**](/solutions/search/ingest-for-search.md) | Options for getting data into {{es}} | -| [**Search approaches**](/solutions/search/search-approaches.md) | Compare full-text, vector, semantic, and hybrid search techniques | +| [**Search approaches**](/solutions/search/search-approaches.md) | Compare search techniques available in {{es}}, including full-text, vector, semantic, and hybrid search | | [**Build your queries**](/solutions/search/querying-for-search.md) | Implement your search approaches using specific query languages | | [**Ranking and reranking**](/solutions/search/ranking.md) | Control result ordering and relevance | | [**RAG**](/solutions/search/rag.md) | Learn about tools for retrieval augmented generation with {{es}}| diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md index c8fa5b827a..0dbf480bf5 100644 --- a/solutions/search/get-started.md +++ b/solutions/search/get-started.md @@ -9,7 +9,7 @@ products: - id: cloud-serverless --- -# Get started with search primitives +# Get started with search This guide helps you get started with search use cases using {{es}}, regardless of your deployment type. Whether you're using a self-managed cluster, {{ech}}, or an {{es}} serverless project, these core search primitives are available to you. @@ -21,7 +21,7 @@ Using the {{es}} solution or serverless project type? Check out the [{{es}} solu To follow along with this guide, you'll need: -- An {{es}} cluster or serverless project. [Create a deployment](/get-started/deployment-options.md) if you don't have one yet. +- An {{es}} cluster, or any type of serverless project. [Create a deployment or project](/get-started/deployment-options.md) if you don't have one yet. - Connection details for your cluster. Refer to [Connection details](/solutions/elasticsearch-solution-project/search-connection-details.md) for more information. ## Quickstarts From 9c7baf034b2bcadb0609869eedb8ec3b024254f5 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 17 Dec 2025 13:53:42 +0100 Subject: [PATCH 31/35] Move quickstart guides from Elasticsearch solution to search use case MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Move quickstart files from solutions/elasticsearch-solution-project/get-started/ to solutions/search/get-started/ as they document core search capabilities available across all deployment types, not just ES solution features. - Move index-basics.md, keyword-search-python.md, semantic-search.md, quickstarts.md - Update TOC to reflect new location - Update redirects for moved files - Update internal links in related files 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 --- .../local-development-installation-quickstart.md | 2 +- explore-analyze/query-filter.md | 2 +- redirects.yml | 4 ++-- .../elasticsearch-solution-project/get-started.md | 10 +++++----- .../get-started/index-basics.md | 0 .../get-started/keyword-search-python.md | 0 .../get-started/quickstarts.md | 6 +++--- .../get-started/semantic-search.md | 0 solutions/search/querying-for-search.md | 2 +- solutions/toc.yml | 11 ++++++----- 10 files changed, 19 insertions(+), 18 deletions(-) rename solutions/{elasticsearch-solution-project => search}/get-started/index-basics.md (100%) rename solutions/{elasticsearch-solution-project => search}/get-started/keyword-search-python.md (100%) rename solutions/{elasticsearch-solution-project => search}/get-started/quickstarts.md (82%) rename solutions/{elasticsearch-solution-project => search}/get-started/semantic-search.md (100%) diff --git a/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md b/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md index b237c799d7..8fd511d474 100644 --- a/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md +++ b/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md @@ -49,4 +49,4 @@ For more detailed information about the `start-local` setup, refer to the [READM ## Next steps [local-dev-next-steps] -Use our [quick start guides](/solutions/elasticsearch-solution-project/get-started/quickstarts.md) to learn the basics of {{es}}. +Use our [quick start guides](/solutions/search/get-started/quickstarts.md) to learn the basics of {{es}}. diff --git a/explore-analyze/query-filter.md b/explore-analyze/query-filter.md index 58a2642883..b5d559247b 100644 --- a/explore-analyze/query-filter.md +++ b/explore-analyze/query-filter.md @@ -27,7 +27,7 @@ You’ll use a combination of an API endpoint and a query language to interact w - A number of [tools](/explore-analyze/query-filter/tools.md) are available for you to save, debug, and optimize your queries. -If you're just getting started with {{es}}, try the hands-on [](/solutions/elasticsearch-solution-project/get-started/index-basics.md) to learn how to add data and run basic searches using Query DSL and the `_search` endpoint. +If you're just getting started with {{es}}, try the hands-on [](/solutions/search/get-started/index-basics.md) to learn how to add data and run basic searches using Query DSL and the `_search` endpoint. ## Filtering diff --git a/redirects.yml b/redirects.yml index f753fd4624..d4eaac673d 100644 --- a/redirects.yml +++ b/redirects.yml @@ -336,13 +336,13 @@ redirects: 'deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md': 'deploy-manage/monitor/autoops/ec-autoops-events.md' # Related to https://github.com/elastic/docs-content/pull/2245/ - 'solutions/search/elasticsearch-basics-quickstart.md': 'solutions/elasticsearch-solution-project/get-started/index-basics.md' + 'solutions/search/elasticsearch-basics-quickstart.md': 'solutions/search/get-started/index-basics.md' # Related to https://github.com/elastic/elasticsearch/pull/133362 'solutions/search/querydsl-full-text-filter-tutorial.md': 'elasticsearch://reference/query-languages/query-dsl/full-text-filter-tutorial.md' # Related to https://github.com/elastic/docs-content/pull/2719 - 'solutions/search/api-quickstarts.md': 'solutions/elasticsearch-solution-project/get-started/quickstarts.md' + 'solutions/search/api-quickstarts.md': 'solutions/search/get-started/quickstarts.md' # Related to https://github.com/elastic/docs-content/pull/2745 'solutions/search/run-elasticsearch-locally.md': 'deploy-manage/deploy/self-managed/local-development-installation-quickstart.md' diff --git a/solutions/elasticsearch-solution-project/get-started.md b/solutions/elasticsearch-solution-project/get-started.md index bd4d0fec3d..d3fcf11594 100644 --- a/solutions/elasticsearch-solution-project/get-started.md +++ b/solutions/elasticsearch-solution-project/get-started.md @@ -50,16 +50,16 @@ Check out the full list of [deployment types](/deploy-manage/deploy.md#choosing- Get hands-on experience with {{es}} using guided tutorials that walk you through common search scenarios: -- [**Index and search basics**](/solutions/elasticsearch-solution-project/get-started/index-basics.md): Learn how to create indices, add documents, and perform searches -- [**Keyword search with Python**](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md): Build your first search query with Python -- [**Semantic search**](/solutions/elasticsearch-solution-project/get-started/semantic-search.md): Implement semantic search using embeddings +- [**Index and search basics**](/solutions/search/get-started/index-basics.md): Learn how to create indices, add documents, and perform searches +- [**Keyword search with Python**](/solutions/search/get-started/keyword-search-python.md): Build your first search query with Python +- [**Semantic search**](/solutions/search/get-started/semantic-search.md): Implement semantic search using embeddings ::::: :::::{step} Identify your search goals Depending on your use case, you can choose multiple [search approaches](/solutions/search/search-approaches.md), for example full-text and semantic search. Each approach affects your options for storing and querying your data. -If you're unsure which approaches match your goals, you can try them out with sample data. For example, [](/solutions/elasticsearch-solution-project/get-started/semantic-search.md). +If you're unsure which approaches match your goals, you can try them out with sample data. For example, [](/solutions/search/get-started/semantic-search.md). If you prefer to ingest your data first and transform or reindex it as needed later, skip to the next step. ::::: @@ -72,7 +72,7 @@ This method is described in [](/solutions/search/semantic-search/semantic-search To learn about adding data for other search goals, go to [](/solutions/search/ingest-for-search.md). For a broader overview of ingestion options, go to [](/manage-data/ingest.md). -If you're not ready to add your own data, you can use [sample data](/manage-data/ingest/sample-data.md) or create small data sets when you follow the instructions in the [quickstarts](/solutions/elasticsearch-solution-project/get-started/quickstarts.md). +If you're not ready to add your own data, you can use [sample data](/manage-data/ingest/sample-data.md) or create small data sets when you follow the instructions in the [quickstarts](/solutions/search/get-started/quickstarts.md). The {{es}} home page in the UI also provides workflow guides for creating indices and ready-to-use code examples for ingesting data by using REST APIs. ::::: diff --git a/solutions/elasticsearch-solution-project/get-started/index-basics.md b/solutions/search/get-started/index-basics.md similarity index 100% rename from solutions/elasticsearch-solution-project/get-started/index-basics.md rename to solutions/search/get-started/index-basics.md diff --git a/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md b/solutions/search/get-started/keyword-search-python.md similarity index 100% rename from solutions/elasticsearch-solution-project/get-started/keyword-search-python.md rename to solutions/search/get-started/keyword-search-python.md diff --git a/solutions/elasticsearch-solution-project/get-started/quickstarts.md b/solutions/search/get-started/quickstarts.md similarity index 82% rename from solutions/elasticsearch-solution-project/get-started/quickstarts.md rename to solutions/search/get-started/quickstarts.md index 51d327a946..9ae2a9a9c2 100644 --- a/solutions/elasticsearch-solution-project/get-started/quickstarts.md +++ b/solutions/search/get-started/quickstarts.md @@ -18,9 +18,9 @@ Each quickstart provides: Follow the steps in these guides to get started quickly: -- [](/solutions/elasticsearch-solution-project/get-started/index-basics.md) -- [](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md) -- [](/solutions/elasticsearch-solution-project/get-started/semantic-search.md) +- [](/solutions/search/get-started/index-basics.md) +- [](/solutions/search/get-started/keyword-search-python.md) +- [](/solutions/search/get-started/semantic-search.md) ## Related resources diff --git a/solutions/elasticsearch-solution-project/get-started/semantic-search.md b/solutions/search/get-started/semantic-search.md similarity index 100% rename from solutions/elasticsearch-solution-project/get-started/semantic-search.md rename to solutions/search/get-started/semantic-search.md diff --git a/solutions/search/querying-for-search.md b/solutions/search/querying-for-search.md index 3254e37028..f16e7ec181 100644 --- a/solutions/search/querying-for-search.md +++ b/solutions/search/querying-for-search.md @@ -34,5 +34,5 @@ You can use the [{{es}} REST APIs](https://www.elastic.co/docs/api/doc/elasticse :::: ::::{tip} -Try our hands-on [quickstart guides](/solutions/elasticsearch-solution-project/get-started/quickstarts.md) to get started, or check out our [Python notebooks](https://github.com/elastic/elasticsearch-labs/tree/main/notebooks#readme). +Try our hands-on [quickstart guides](/solutions/search/get-started/quickstarts.md) to get started, or check out our [Python notebooks](https://github.com/elastic/elasticsearch-labs/tree/main/notebooks#readme). :::: diff --git a/solutions/toc.yml b/solutions/toc.yml index 489c3be2d1..4236999bc9 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -4,6 +4,12 @@ toc: - file: search.md children: - file: search/get-started.md + children: + - file: search/get-started/quickstarts.md + children: + - file: search/get-started/index-basics.md + - file: search/get-started/keyword-search-python.md + - file: search/get-started/semantic-search.md - file: search/ingest-for-search.md children: - file: search/search-pipelines.md @@ -69,11 +75,6 @@ toc: - file: elasticsearch-solution-project/get-started.md children: - file: elasticsearch-solution-project/search-connection-details.md - - file: elasticsearch-solution-project/get-started/quickstarts.md - children: - - file: elasticsearch-solution-project/get-started/index-basics.md - - file: elasticsearch-solution-project/get-started/keyword-search-python.md - - file: elasticsearch-solution-project/get-started/semantic-search.md - file: elasticsearch-solution-project/elastic-agent-builder.md children: - file: elasticsearch-solution-project/agent-builder/get-started.md From f640f541ccb5fd9288ca61fb9412f89541fc6b9f Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 17 Dec 2025 13:54:12 +0100 Subject: [PATCH 32/35] Rewrite solutions overview pages with path-based framing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace "primitives" terminology with "capabilities" and restructure solutions/index.md to use path-based navigation instead of structural organization. Consolidate redundant sections into a single table showing use cases and available options. Key changes: - solutions/index.md: Consolidated "Choose your path" table explaining search capabilities vs ES solution - solutions/search.md: Replaced "primitives" with "capabilities", clarified availability across all deployment types - solutions/search/get-started.md: Updated terminology and added clarity about solution-agnostic nature Addresses reviewer feedback about differentiating search use case from Elasticsearch solution and making the section organization clearer. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 --- solutions/index.md | 31 +++++++++++-------------------- solutions/search.md | 12 ++++++------ solutions/search/get-started.md | 10 +++++----- 3 files changed, 22 insertions(+), 31 deletions(-) diff --git a/solutions/index.md b/solutions/index.md index 0be1c217e6..3650f65bce 100644 --- a/solutions/index.md +++ b/solutions/index.md @@ -17,27 +17,18 @@ description: Learn about Elastic solutions for search, observability, and securi New to Elastic? Refer to [Elastic Fundamentals](/get-started/index.md) to understand the {{stack}}, its components, and your deployment options. ::: -Elastic helps you build applications for three main use cases: search, observability, and security. You can work directly with platform capabilities through APIs, use pre-built solutions with integrated UIs, or combine both approaches. +Elastic helps you build applications for three main use cases: search, observability, and security. -This section is organized into two parts: +## Choose your path -- [**Search use case**](#search-use-case): Core {{es}} features accessed through APIs and client libraries, available across all [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type). Use these when you need programmatic control or the flexibility to build custom applications. -- [**Solutions and project types**](#solutions-and-project-types): Pre-built UI tools and workflows for specific use cases, available on {{serverless-full}} as project types or on other deployments as solutions. Use these to get started quickly with pre-configured workflows, sensible defaults, and tailored UI affordances. +| Your use case | What to use | Description | +| --- | --- | --- | +| Building search applications | 1. [Core search capabilities](/solutions/search.md)

2. [Elasticsearch solution](/solutions/elasticsearch-solution-project.md) | - Core {{es}} search features available across all deployment types, solutions, and project types

- Additional UI tools that complement the core search features | +| Monitoring applications or infrastructure | [Observability solution](/solutions/observability.md) | Monitor and troubleshoot with logs, metrics, and traces | +| Protecting against threats | [Security solution](/solutions/security.md) | Detect and respond to security threats | -## Search use case +::::{tip} +If you're not sure which solution to use, the {{es}} solution is a good starting point for general-purpose search use cases. +:::: -The [Search use case](/solutions/search.md) documents core {{es}} search capabilities available across all Elastic [deployment types](/deploy-manage/deploy.md#choosing-your-deployment-type). - -## Solutions and project types - -Solutions provide integrated UI tools and workflows with sensible defaults, in addition to core platform capabilities. They help you get started quickly with common use cases. - -Solutions are available as a fully managed {{serverless-short}} project, a managed service on {{ech}}, or a self-managed deployment: -- On {{serverless-full}}, you select a project type when creating your project. -- On non-serverless deployments, solution views are configured per [space](/deploy-manage/manage-spaces.md). - -| Solution/Project | Description | -| --- | --- | -| [**Elasticsearch**](/solutions/elasticsearch-solution-project.md) | UI tools for building search applications | -| [**Observability**](/solutions/observability.md) | Monitor and troubleshoot applications and infrastructure | -| [**Security**](/solutions/security.md) | Protect applications and infrastructure from threats | +**About solutions and project types:** Solutions are available as project types on {{serverless-full}} (select one when creating a project) or as solution views on {{ech}} and self-managed deployments (select a default solution view when creating a deployment, or configure per [space](/deploy-manage/manage-spaces.md)). diff --git a/solutions/search.md b/solutions/search.md index e667af7b6d..10aa680826 100644 --- a/solutions/search.md +++ b/solutions/search.md @@ -12,17 +12,17 @@ navigation_title: Search use case # Search use case -This section documents {{es}} search primitives. These capabilities are available across all Elastic deployments. +This section documents core {{es}} search capabilities. These capabilities are available across all Elastic deployments, solutions, and project types. Use this section to understand search techniques, query methods, ranking strategies, and data ingestion for search applications. ::::{tip} -Using the {{es}} solution or serverless project type? The {{es}} solution documentation covers additional UI tools that complement these search primitives. Refer to [](/solutions/elasticsearch-solution-project.md) for more details. +Using the {{es}} solution or serverless project type? The [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) covers additional UI tools available if you are using the solution or project type. :::: ## What you can build -Use {{es}} search primitives to build search applications including: +Use {{es}} search capabilities to build search applications including: - Website and documentation search - Ecommerce product catalogs @@ -33,14 +33,14 @@ Use {{es}} search primitives to build search applications including: - Custom observability or cybersecurity search tools - Much more! -## Topics +## Search use case documentation -The following topics are covered in this section: +The following subjects are covered in this section: | Topic | Description | |-------|-------------| | [**Get started**](/solutions/search/get-started.md) | Create deployments, connect to {{es}}, and run your first searches | -| [**Ingest data**](/solutions/search/ingest-for-search.md) | Options for getting data into {{es}} | +| [**Ingest data**](/solutions/search/ingest-for-search.md) | Learn about options for getting data into {{es}} for search use cases | | [**Search approaches**](/solutions/search/search-approaches.md) | Compare search techniques available in {{es}}, including full-text, vector, semantic, and hybrid search | | [**Build your queries**](/solutions/search/querying-for-search.md) | Implement your search approaches using specific query languages | | [**Ranking and reranking**](/solutions/search/ranking.md) | Control result ordering and relevance | diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md index 0dbf480bf5..a73b6e215f 100644 --- a/solutions/search/get-started.md +++ b/solutions/search/get-started.md @@ -11,10 +11,10 @@ products: # Get started with search -This guide helps you get started with search use cases using {{es}}, regardless of your deployment type. Whether you're using a self-managed cluster, {{ech}}, or an {{es}} serverless project, these core search primitives are available to you. +This guide helps you get started with search use cases using {{es}}, regardless of your deployment type, solution, or project type. Whether you're using a self-managed cluster, {{ech}}, or any type of serverless project, these core search capabilities are available to you. ::::{tip} -Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for UI tools like Agent Builder, Playground, and Search Applications that complement these core search primitives. +Using the {{es}} solution or serverless project type? Check out the [{{es}} solution documentation](/solutions/elasticsearch-solution-project.md) for UI tools like Agent Builder, Playground, and Search Applications that complement these core search capabilities. :::: ## Before you begin @@ -28,9 +28,9 @@ To follow along with this guide, you'll need: Choose a quickstart based on your use case: -- [**Index basics**](/solutions/elasticsearch-solution-project/get-started/index-basics.md): Learn how to create indices, add documents, and perform basic searches using the {{es}} APIs. -- [**Keyword search with Python**](/solutions/elasticsearch-solution-project/get-started/keyword-search-python.md): Build a keyword search application using the Python client. -- [**Semantic search**](/solutions/elasticsearch-solution-project/get-started/semantic-search.md): Implement semantic search using vector embeddings. +- [**Index basics**](/solutions/search/get-started/index-basics.md): Learn how to create indices, add documents, and perform basic searches using the {{es}} APIs. +- [**Keyword search with Python**](/solutions/search/get-started/keyword-search-python.md): Build a keyword search application using the Python client. +- [**Semantic search**](/solutions/search/get-started/semantic-search.md): Implement semantic search using vector embeddings. ## Explore search approaches From 2c98ea4156f04e10e313df26f86aebd2a493c0a3 Mon Sep 17 00:00:00 2001 From: Liam Thompson <32779855+leemthompo@users.noreply.github.com> Date: Wed, 17 Dec 2025 13:57:40 +0100 Subject: [PATCH 33/35] update rag page --- get-started/introduction.md | 4 ++- solutions/elasticsearch-solution-project.md | 22 ++++++++-------- .../agent-builder/get-started.md | 4 +-- .../agent-builder/mcp-server.md | 2 +- solutions/observability.md | 2 +- solutions/search/rag.md | 25 ++++++++++++------- 6 files changed, 33 insertions(+), 26 deletions(-) diff --git a/get-started/introduction.md b/get-started/introduction.md index 26fc8d969a..98c573f730 100644 --- a/get-started/introduction.md +++ b/get-started/introduction.md @@ -17,7 +17,7 @@ Whether you're building a search experience, monitoring your infrastructure, or | Your need | Recommended solution | Best for | |-----------|-------------------|----------| -| Build powerful, scalable searches to quickly search, analyze, and visualize large amounts of data for real-time insights| [{{es}}](/solutions/search.md)
• [Get started](/solutions/search/get-started.md)| Developers, architects, data engineers | +| Build powerful, scalable searches to quickly search, analyze, and visualize large amounts of data for real-time insights| [{{es}}](/solutions/search.md)[^search-note]
• [Get started](/solutions/search/get-started.md)| Developers, architects, data engineers | | Observe and monitor system health and performance, or send telemetry data | [Elastic {{observability}}](/solutions/observability.md)
• [Get started](/solutions/observability/get-started.md) | DevOps, SREs, IT operations | | Monitor data for anomalous activity, detect, prevent, and respond to security incidents | [{{elastic-sec}}](/solutions/security.md)
• [Get started](/solutions/security/get-started.md)| SOC teams, security analysts, IT security admins | @@ -29,6 +29,8 @@ Each of our solutions is available as a fully managed {{serverless-short}} proje If you're new to Elastic, you can find quickstarts and introductory steps for each solution within [](/solutions/index.md). +[^search-note]: The core [{{es}} search capabilities](/solutions/search.md) are available across all deployment types, solutions, and project types through APIs and client libraries. The [{{es}} solution](/solutions/elasticsearch-solution-project.md) adds UI tools on top of these capabilities to help you build search applications faster. +