Merge branch 'main' into obs-ai-assistant-add-gpt-5-chat-ratings

Author: viduni94

deploy-manage/deploy/elastic-cloud/create-an-organization.md

@@ -41,9 +41,9 @@ A deployment lets you explore Elastic solutions for Search, Observability, and S
 
 For more information, check the [{{ech}} documentation](cloud-hosted.md).
 
-**One serverless project**
+**Three {{serverless-short}} project**
 
-Serverless projects package {{stack}} features by type of solution:
+{{serverless-short}} projects package {{stack}} features by type of solution:
 
 * [{{es}}](../../../solutions/search.md)
 * [Observability](../../../solutions/observability.md)
@@ -56,7 +56,7 @@ For more information, check the [{{serverless-short}} documentation](serverless.
 
 ### Trial limitations [general-sign-up-trial-what-limits-are-in-place-during-a-trial]
 
-During the free 14 day trial, Elastic provides access to one hosted deployment and one serverless project. If all you want to do is try out Elastic, the trial includes more than enough to get you started. During the trial period, some limitations apply.
+During the free 14 day trial, Elastic provides access to one hosted deployment and three {{serverless-short}} projects. If all you want to do is try out Elastic, the trial includes more than enough to get you started. During the trial period, some limitations apply.
 
 **Hosted deployments**
 
@@ -70,10 +70,10 @@ For more information, check the [{{ech}} documentation](cloud-hosted.md).
 
 **Serverless projects**
 
-* You can have one active serverless project at a time.
+* You can have three active {{serverless-short}} projects at a time.
 * Search Power is limited to 100. This setting only exists in {{es-serverless}} projects
 * Search Boost Window is limited to 7 days. This setting only exists in {{es-serverless}} projects
-* Scaling is limited for serverless projects in trials. Failures might occur if the workload requires memory or compute beyond what the above search power and search boost window setting limits can provide.
+* Scaling is limited for {{serverless-short}} projects in trials. Failures might occur if the workload requires memory or compute beyond what the above search power and search boost window setting limits can provide.
 * We monitor token usage per account for the Elastic Managed LLM. If an account uses over one million tokens in 24 hours, we will inform you and then disable access to the LLM. This is in accordance with our fair use policy for trials. 
 
 **Remove limitations**
@@ -95,7 +95,7 @@ Start by checking out some common approaches for [moving data into {{ecloud}}](/
 
 ### Maintain access to your trial projects and data [general-sign-up-trial-what-happens-at-the-end-of-the-trial]
 
-When your trial expires, the deployment and project that you created during the trial period are suspended until you subscribe to [{{ecloud}}](/deploy-manage/cloud-organization/billing/add-billing-details.md). When you subscribe, you are able to resume your deployment and serverless project, and regain access to the ingested data. After your trial expires, you have 30 days to subscribe. After 30 days, your deployment, serverless project, and ingested data are permanently deleted.
+When your trial expires, the deployment and projects that you created during the trial period are suspended until you subscribe to [{{ecloud}}](/deploy-manage/cloud-organization/billing/add-billing-details.md). When you subscribe, you are able to resume your deployment and {{serverless-short}} projects, and regain access to the ingested data. After your trial expires, you have 30 days to subscribe. After 30 days, your deployment, {{serverless-short}} projects, and ingested data are permanently deleted.
 
 If you’re interested in learning more ways to subscribe to {{ecloud}}, don’t hesitate to [contact us](https://www.elastic.co/contact).
 

deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md

@@ -5,11 +5,8 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/field-level-security.html
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/field-and-document-access-control.html
 applies_to:
-  deployment:
-    ece:
-    eck:
-    ess:
-    self:
+  stack: all
+  serverless: all
 products:
   - id: elasticsearch
 ---

explore-analyze/alerts-cases.md

@@ -36,5 +36,8 @@ If you have a planned outage, maintenance windows prevent rules from generating
 By combining these tools, Elasticsearch and Kibana enable incident response workflows, helping teams to detect, investigate, and resolve issues efficiently.
 
 ## Watcher
+```{applies_to}
+serverless: unavailable
+```
 
 You can use Watcher for alerting and monitoring specific conditions in your data. It enables you to define rules and take automated actions when certain criteria are met. Watcher is a powerful alerting tool for custom use cases and more complex alerting logic. It allows advanced scripting using Painless to define complex conditions and transformations.

release-notes/elastic-cloud-serverless/index.md

@@ -9,6 +9,64 @@ products:
 # {{serverless-full}} changelog [elastic-cloud-serverless-changelog]
 Review the changes, fixes, and more to {{serverless-full}}.
 
+## November 3, 2025 [serverless-changelog-11032025]
+
+### Features and enhancements [serverless-changelog-11032025-features-enhancements]
+
+* Moves the **Lens** visualization toolbar from the workspace section to the configuration panel [#239879]({{kib-pull}}239879)
+* Adds support for rolling back integrations to previous versions [#240761]({{kib-pull}}240761)
+* Adds support for subqueries in the {{esql}} abstract syntax tree (AST) [#241227]({{kib-pull}}241227)
+* Adds subquery support for the walker and visitor in the {{esql}} AST [#241451]({{kib-pull}}241451)
+* Adds support for expressions in `LOOKUP JOIN` autocomplete [#240735]({{kib-pull}}240735)
+* Adds support for multi-value variables in `MV_CONTAINS` [#239266]({{kib-pull}}239266)
+* Adds client-side validation for `LOOKUP JOIN ON` expressions [#240930]({{kib-pull}}240930)
+* Improves the {{esql}} suggestions logic to provide more semantically intelligent suggestions [#241081]({{kib-pull}}241081)
+* Adds an `isStream` parameter to the `chat/complete` endpoint to support non-streaming responses in the Observability AI Assistant [#240819]({{kib-pull}}240819)
+* Makes the `opamp_polling_interval` and `sampling_rate` agent configuration variables available to EDOT Node.js [#241048]({{kib-pull}}241048)
+* Adds a free-text popup for the `runscript` argument to provide user input to the selected script [#239436]({{kib-pull}}239436)
+* Adds the deployment name to the breadcrumbs in {{ech}} [#238078]({{kib-pull}}238078)
+* Adds a **Give feedback** button to the Anomaly Explorer and Single Metric Viewer [#239883]({{kib-pull}}239883)
+* Adds a new `temperature` parameter to the AI Connector configuration schema [#239626]({{kib-pull}}239626)
+* Makes the Update spaces APIs public [#241109]({{kib-pull}}241109)
+* Adds support for the `convert` processor in stream data processing [#240023]({{kib-pull}}240023)
+* Improves message feedback in collapsed Processors/Conditions sections [#240778]({{kib-pull}}240778)
+* Optimizes workflow output in Agent Builder tools by removing workflow execution details from tool calls, reducing LLM token consumption and improving agent performance and reliability [#241040]({{kib-pull}}241040)
+
+### Fixes [serverless-changelog-11032025-fixes]
+
+* Fixes layout issues for Markdown embeddables in small panels [#240806]({{kib-pull}}240806)
+* Fixes an issue where labels in the **Create index** flow did not automatically render with the default vector tile scaling after saving or applying styling changes [#240728]({{kib-pull}}240728)
+* Fixes `template_path` asset selection for certain integration packages [#240750]({{kib-pull}}240750)
+* Omits system properties when syncing ingest pipelines [#241096]({{kib-pull}}241096)
+* Fixes autocomplete for time series sources after a comma [#241402]({{kib-pull}}241402)
+* Fixes a bottom gap that appeared while loading data in some cases [#238879]({{kib-pull}}238879)
+* Hides non-trace services in service maps [#240104]({{kib-pull}}240104)
+* Fixes an issue where the `kibana` tool failed when running {{kib}} behind a proxy [#236653]({{kib-pull}}236653)
+* Fixes overlapping components in the Observability AI Assistant flyout on small screens [#241026]({{kib-pull}}241026)
+* Aligns the **Members** link in the side navigation across all solutions [#240992]({{kib-pull}}240992)
+* Updates Metrics experience API routes to delegate authorization to {{es}} [#241195]({{kib-pull}}241195)
+* Copies alert states to the payload [#240411]({{kib-pull}}240411)
+* Adds missing fields to transaction data [#241336]({{kib-pull}}241336)
+* Simplifies metrics profile resolution by removing index pattern and time series validation [#241047]({{kib-pull}}241047)
+* Allows partial matches on rule names when searching installed rules [#237496]({{kib-pull}}237496)
+* Fixes a regression in threshold rule logic where threshold rules with no `group by` fields defined would no longer generate alerts [#241022]({{kib-pull}}241022)
+* Fixes an issue where the alert details flyout on the **Risk contributions** tab did not display data in some cases [#241153]({{kib-pull}}241153)
+* Fixes a table pagination issue on the Intelligence page [#241108]({{kib-pull}}241108)
+* Fixes an issue with the **Regenerate** button in the Security Assistant [#241240]({{kib-pull}}241240)
+* Fixes an issue where the Security AI Assistant's Index Entry form was showing incorrect field suggestions, missing searchable fields that exist as multi-fields or nested properties in {{es}} mappings [#239453]({{kib-pull}}239453)
+* Fixes an issue where agent-based integrations failed to produce data [#241390]({{kib-pull}}241390)
+* Fixes an infinite loop bug related to bootstrapping list resources [#241052]({{kib-pull}}241052)
+* Reduces re-renders on resize and items change [#239888]({{kib-pull}}239888)
+* Fixes index names causing an incompatible cluster error when product docs are installed with multiple inference IDs [#240506]({{kib-pull}}240506)
+* Ensures all authentication fields are displayed correctly [#240913]({{kib-pull}}240913)
+* Ensures the `max_tokens` parameter is passed as expected by the service [#241188]({{kib-pull}}241188)
+* Updates the inference creation endpoint to ensure the `max_tokens` parameter is passed as expected when creating an Anthropic Connector [#241212]({{kib-pull}}241212)
+* Removes the default fallback region for the Bedrock Connector [#241157]({{kib-pull}}241157)
+* Fixes wrapping issues in the Streams UI [#240883]({{kib-pull}}240883)
+* Speeds up field simulation in Streams [#241313]({{kib-pull}}241313)
+* Updates action response codes [#240420]({{kib-pull}}240420)
+* Fixes an infinite loop bug in the **Investigation guide** editor [#240472]({{kib-pull}}240472)
+
 ## October 27, 2025 [serverless-changelog-10272025]
 
 ### Features and enhancements [elastic-security-10272025-features-enhancements]

solutions/search/agent-builder/kibana-api.md

@@ -677,38 +677,15 @@ curl -X DELETE "https://${KIBANA_URL}/api/agent_builder/conversations/{conversat
 
 ::::
 
-### MCP server API
+### Get A2A agent card configuration
 
-Refer to [](mcp-server.md) for more information.
-
-Communicate with the MCP server using JSON-RPC 2.0.
-
-```bash
-curl -X POST "https://${KIBANA_URL}/api/agent_builder/mcp" \
-    -H "Authorization: ApiKey ${API_KEY}" \
-    -H "Content-Type: application/json" \
-    -H "Accept: application/json" \
-    -H "kbn-xsrf: true" \
-    -d '{
-        "jsonrpc": "2.0",
-        "id": 1,
-        "method": "tools/list"
-    }'
-```
-If you're using Spaces, you need to prefix `/api/agent_builder` with `/s/<space_name>`. Refer to [Working with Spaces](#working-with-spaces).
-
-:::{note}
-This endpoint uses the JSON-RPC protocol. The MCP server is used by AI clients like Claude Desktop, Cursor, and VS Code extensions to access your Elastic tools. Use this {{kib}} API endpoint for testing MCP connectivity or debugging protocol communication. This endpoint requires JSON-RPC formatting and does not work from the Dev Tools Console.
+:::{important}
+You shouldn't use the REST APIs to interact with the A2A endpoint, apart from getting the A2A agent card configuration.
+Refer to [](a2a-server.md) for more information about using the A2A protocol. 
 :::
 
-### A2A protocol
-
-Refer to [](a2a-server.md) for more information.
-
 **Example:** Get A2A agent card configuration
 
-This example uses the [get A2A agent card API](https://www.elastic.co/docs/api/doc/kibana/operation/operation-get-agent-builder-a2a-agentid-json).
-
 ::::{tab-set}
 :group: api-examples
 
@@ -732,47 +709,6 @@ curl -X GET "https://${KIBANA_URL}/api/agent_builder/a2a/{agentId}.json" \
 ::::
 
 
-% TODO: Execute A2A agent task section - commented out until ready
-% Execute A2A agent task
-% ::::{tab-set}
-% :group: api-examples
-% 
-% :::{tab-item} Console
-% :sync: console
-% :::{note}
-% This endpoint uses the JSON-RPC protocol, which cannot be executed in the Dev Tools Console.
-% Use curl or another HTTP client.
-% :::
-% 
-% :::{tab-item} curl
-% :sync: curl
-% ```bash
-% curl -X POST "https://${KIBANA_URL}/api/agent_builder/a2a/{agentId}" \
-%      -H "Authorization: ApiKey ${API_KEY}" \
-%      -H "kbn-xsrf: true" \
-%      -H "Content-Type: application/json" \
-%      -d '{
-%        "jsonrpc": "2.0",
-%        "method": "complete",
-%        "params": {
-%          "messages": [
-%            {
-%              "role": "user",
-%              "content": "Hello from A2A protocol"
-%            }
-%          ]
-%        },
-%        "id": "task-123"
-%      }'
-% ```
-% :::
-% 
-% ::::
-
-
-
-
-
 ## API reference
 
-For the full API documentation, refer to the [{{kib}} API reference](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-agent-builder).
+For the full API documentation, refer to the [{{kib}} API reference](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-agent-builder).

solutions/search/apis-and-tools.md

@@ -74,14 +74,14 @@ The accompanying [GitHub repository](https://www.github.com/elastic/elasticsearc
 
 ## Generative AI tools
 
-### Playground
+### Agent Builder
 
-Use [Playground](rag/playground.md) to combine your {{es}} data with the power of large language models (LLMs) for retrieval augmented generation (RAG), using 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.
+[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.
 
-### {{es}} Model Context Protocol (MCP) server
+### Playground
 
-Connect to your Elasticsearch data directly from any MCP Client (like Claude Desktop) using the Model Context Protocol (MCP).
+[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.
 
-This server enables connecting agents to your Elasticsearch data and allows you to interact with your Elasticsearch indices through natural language conversations.
+### Model Context Protocol (MCP)
 
-Learn more in the [elastic/mcp-server-elasticsearch](https://github.com/elastic/mcp-server-elasticsearch?tab=readme-ov-file#elasticsearch-mcp-server) GitHub repository.
+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.

solutions/search/search-approaches.md

@@ -7,15 +7,16 @@ applies_to:
 
 To deliver relevant search results, you need to choose the right search approach for your data and use case.
 
+## Overview of search techniques
+
 The following table provides an overview of the fundamental search techniques available in {{es}}:
 
 | Name | Description | Notes |
 |------|-------------|--------|
 | [**Full-text search**](full-text.md) | Traditional lexical search with analyzers and relevance tuning | Essential foundation for keyword matching, works out of the box |
-| [**Vector search**](vector.md) | Similarity search using numerical vectors | Requires extra setup/resources, ideal for finding similar documents |
-| [**Semantic search**](semantic-search.md) | Meaning-based search using natural language understanding | Requires ML models and vector infrastructure |
-| [**Hybrid search**](hybrid-semantic-text.md) | Combines lexical and vector/semantic approaches | Best balance for both keyword precision and semantic relevance |
-| [**Re-ranking**](ranking/semantic-reranking.md) | Post-processing results to improve relevance | Optional ML-based enhancement for fine-tuned relevance |
+| [**AI-powered search**](ai-search/ai-search.md) | Machine learning-based search using natural language understanding | Includes [vector search](vector.md) and [semantic search](semantic-search.md) approaches |
+| [**Hybrid search**](hybrid-search.md) | Combines lexical and vector/semantic approaches | Best balance for both keyword precision and semantic relevance |
+| [**Ranking and reranking**](ranking.md) | Post-processing results to improve relevance | Optional ML-based enhancement for fine-tuned relevance |
 | [**Geospatial search**](/explore-analyze/geospatial-analysis.md) | Location-based search and spatial relationships | For maps, distance calculations, and shape queries |
 
 :::::{tip}