Merge branch 'add-elastic-new-intro-section' of github.com:elastic/docs-content into add-elastic-new-intro-section

jmikell821 · jmikell821 · commit a0cc0e9e516d · 2025-09-08T18:49:21.000-04:00
diff --git a/cloud-account/multifactor-authentication.md b/cloud-account/multifactor-authentication.md
@@ -21,7 +21,11 @@ Multifactor authentication (MFA) is **mandatory** when you log in to {{ecloud}}
 You can no longer configure SMS as a multifactor authentication method. 
 ::::
 
-Elastic recommends that you enable multiple methods so that you can still access your account if you lose access to one method.
+::::{important} 
+
+For enhanced security, we recommend you configure at least two different authentication methods. This redundancy ensures that losing access to one method doesn't impair access to your {{ecloud}} account.
+
+::::
 
 If you use only a Google or Microsoft account to log in, then you can’t configure MFA in {{ecloud}}. You can check and manage your multifactor authentication options in your Google or Microsoft account security settings.
 
diff --git a/deploy-manage/deploy/_snippets/create-serverless-project-intro.md b/deploy-manage/deploy/_snippets/create-serverless-project-intro.md
@@ -0,0 +1,4 @@
+There are two options to create serverless projects:
+
+* If you are a new user, [sign up for a free 14-day trial](https://cloud.elastic.co/serverless-registration) to create a serverless project. For more information about the {{ecloud}} trials, check [Trial features](/deploy-manage/deploy/elastic-cloud/create-an-organization.md#general-sign-up-trial-what-is-included-in-my-trial).
+* If you are an existing customer, [log in to {{ecloud}}](https://cloud.elastic.co/login). On the home page, you will see a new option to create serverless projects. The `admin` predefined role or an equivalent custom role is required to create projects. Refer to [](/deploy-manage/users-roles/cloud-organization/user-roles.md).
diff --git a/deploy-manage/deploy/elastic-cloud/create-serverless-project.md b/deploy-manage/deploy/elastic-cloud/create-serverless-project.md
@@ -9,17 +9,15 @@ products:
 
 # Create a serverless project [serverless-get-started]
 
-There are two options to create serverless projects:
-
-* If you are a new user, [sign up for a free 14-day trial](https://cloud.elastic.co/serverless-registration) to create a serverless project. For more information about the {{ecloud}} trials, check [Trial features](create-an-organization.md#general-sign-up-trial-what-is-included-in-my-trial).
-* If you are an existing customer, [log in to {{ecloud}}](https://cloud.elastic.co/login). On the home page, you will see a new option to create serverless projects.
+:::{include} /deploy-manage/deploy/_snippets/create-serverless-project-intro.md
+:::
 
 Choose the type of project that matches your needs and we’ll help you get started with our solution guides.
 
 |     |     |
 | --- | --- |
 |  |  |
-| ![elasticsearch](../../images/64x64_Color_elasticsearch-logo-color-64px.png "elasticsearch =50%") | **Elasticsearch**<br> Build custom search applications with {{es}}.<br><br>[**View guide →**](/solutions/search/serverless-elasticsearch-get-started.md)<br> |
+| ![elasticsearch](../../images/64x64_Color_elasticsearch-logo-color-64px.png "elasticsearch =50%") | **Elasticsearch**<br> Build custom search applications with {{es}}.<br><br>[**View guide →**](/solutions/search/get-started.md)<br> |
 | ![observability](../../images/64x64_Color_observability-logo-color-64px.png "observability =50%") | **Observability**<br> Monitor applications and systems with Elastic Observability.<br><br>[**View guide →**](/solutions/observability/get-started.md)<br> |
 | ![security](../../images/64x64_Color_security-logo-color-64px.png "security =50%") | **Security**<br> Detect, investigate, and respond to threats with Elastic Security.<br><br>[**View guide →**](/solutions/security/get-started/create-security-project.md)<br> |
 |  |  |
diff --git a/deploy-manage/deploy/elastic-cloud/serverless.md b/deploy-manage/deploy/elastic-cloud/serverless.md
@@ -27,7 +27,7 @@ There are differences between {{es-serverless}} and {{ech}}, for a list of diffe
 
 Elastic provides three serverless solutions available on {{ecloud}}. Follow these guides to get started with your serverless project:
 
-* **[{{es-serverless}}](../../../solutions/search/serverless-elasticsearch-get-started.md)**: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries.
+* **[{{es-serverless}}](/solutions/search/get-started.md)**: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries.
 * **[{{obs-serverless}}](../../../solutions/observability/get-started.md)**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data.
 * **[{{sec-serverless}}](../../../solutions/security/get-started/create-security-project.md)**: Detect, investigate, and respond to threats with SIEM, endpoint protection, and AI-powered analytics capabilities.
 
diff --git a/deploy-manage/deploy/self-managed/_snippets/install-next-steps.md b/deploy-manage/deploy/self-managed/_snippets/install-next-steps.md
@@ -6,7 +6,7 @@ You now have a test {{es}} environment set up. Before you start serious developm
 
 You can also do the following:
 
-* Consider installing [additional {{stack}} components](/get-started/the-stack.md).
+* Consider installing [additional {{stack}} components](/get-started/search-ai-platform.md).
 * Learn how to [ingest data into {{es}}](/manage-data/index.md).
 * Learn about [production considerations](/deploy-manage/production-guidance.md).
 * Explore [other topics](/deploy-manage/deploy/self-managed.md#other-important-sections) to learn how to secure and manage your cluster.
diff --git a/deploy-manage/deploy/self-managed/_snippets/ports.md b/deploy-manage/deploy/self-managed/_snippets/ports.md
@@ -10,4 +10,4 @@ These settings can be overridden in the relevant configuration file.
 | 9300 and onwards | TCP |	Transport API. Used for intra-cluster communications and client access via the transport API (Java client). | Elasticsearch [`transport.port`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md#common-network-settings) |
 | 5601 | HTTP |	{{kib}} default access port. | Kibana [`server.port`](kibana://reference/configuration-reference/general-settings.md#server-port) |
 
-Additional ports might be required for [optional {{stack}} components](/get-started/the-stack.md). Refer to the installation guide for the component that you want to install.
+Additional ports might be required for [optional {{stack}} components](/get-started/search-ai-platform.md). Refer to the installation guide for the component that you want to install.
diff --git a/explore-analyze/alerts-cases/alerts/view-alerts.md b/explore-analyze/alerts-cases/alerts/view-alerts.md
@@ -77,11 +77,13 @@ Alert flapping is turned on by default. You can modify the criteria for changing
     Once a flapping alert is recovered, it cannot be changed to flapping again. Only new alerts with repeated status changes are candidates for the flapping status. 
 
 `untracked`
-:   The rule is disabled, or you’ve marked the alert as untracked. To mark the alert as untracked, go to the **Alerts** table, click the {icon}`boxes_horizontal` icon to expand the **More actions** menu, and click **Mark as untracked**. When an alert is marked as untracked, actions are no longer generated. You can choose to move active alerts to this state when you disable or delete rules.
+:   The rule is disabled, or you’ve marked the alert as untracked. To mark the alert as untracked, go to the **Alerts** table, click the {icon}`boxes_horizontal` icon to expand the **More actions** menu, and click **Mark as untracked**. When an alert is marked as untracked, actions are no longer generated and the alert's status can no longer be changed. You can choose to move active alerts to this state when you disable or delete rules.
 
 ## Mute alerts [mute-alerts]
 
-If an alert is active or flapping, you can mute it to temporarily suppress future actions. In both **{{stack-manage-app}} > Alerts** and **{{rules-ui}}**, you can open the action menu (…) for the appropriate alert and select **Mute**. To permanently suppress actions for an alert, open the actions menu and select **Mark as untracked**.
+If an alert is active or flapping, you can mute it to temporarily suppress future actions. In **{{stack-manage-app}} > Alerts**, open the action menu (…) for the appropriate alert, then select **Mute**. While muted, the alert's status will continue to update but rule actions won't run. All future alerts with the same alert ID will also be muted.
+
+To permanently suppress an alert's actions, open the actions menu for the appropriate alert, then select **Mark as untracked**. In this case, the alert's status is no longer updated and actions are no longer run. These changes are only applied to the alert that you untracked and cannot be reverted. Future alerts with the same alert ID are unaffected.
 
 To affect the behavior of the rule rather than individual alerts, check out [Snooze and disable rules](create-manage-rules.md#controlling-rules).
 
diff --git a/manage-data/ingest.md b/manage-data/ingest.md
@@ -16,7 +16,7 @@ products:
   - id: elasticsearch
 ---
 
-# Bring your data to Elastic
+# Ingest: Bring your data to Elastic
 
 Whether you call it *adding*, *indexing*, or *ingesting* data, you have to get the data into {{es}} before you can search it, visualize it, and use it for insights.
 
@@ -55,4 +55,4 @@ Integrations are available for many popular platforms and services, and are a go
 
 Check out the [Integration quick reference](https://docs.elastic.co/en/integrations/all_integrations) to search for available integrations. If you don’t find an integration for your data source or if you need additional processing to extend the integration, we still have you covered. Refer to [Transform and enrich data](ingest/transform-enrich.md) to learn more.
 
-::::
+::::
diff --git a/reference/fleet/fleet-agent-release-process.md b/reference/fleet/fleet-agent-release-process.md
@@ -0,0 +1,20 @@
+---
+navigation_title: "{{agent}} release process"
+applies_to:
+  stack: ga
+products:
+  - id: fleet
+  - id: elastic-agent
+---
+
+# {{agent}} release process [fleet-agent-release-process]
+
+## Scheduled releases
+
+{{agent}} follows a release process aligned with the broader {{stack}} release schedule. The latest features, enhancements, and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md).
+
+## Independent {{agent}} releases [independent-agent-releases]
+
+Independent {{agent}} releases deliver critical fixes and updates for {{agent}} and {{elastic-defend}}, independently of the full stack release. This is a more conservative process than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an independent {{agent}} hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch.
+
+In independent {{agent}} releases, a build identifier is appended to the semantic version of the base release in the format `+build{yyyymmddhhmm}`, where `{yyyymmddhhmm}` is the release timestamp of the build.
diff --git a/reference/fleet/toc.yml b/reference/fleet/toc.yml
@@ -19,6 +19,7 @@ toc:
       - file: fleet-server-monitoring.md
   - file: install-elastic-agents.md
     children:
+      - file: fleet-agent-release-process.md
       - file: install-fleet-managed-elastic-agent.md
       - file: install-standalone-elastic-agent.md
         children:
diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md
@@ -80,7 +80,9 @@ With the right [subscription level](https://www.elastic.co/subscriptions), you c
 
 3. In the Upgrade agent window, select or specify an upgrade version and click **Upgrade agent**.
 
-    In certain cases the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field.
+    {{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent {{agent}} release version](./fleet-agent-release-process.md#independent-agent-releases).
+
+    In certain cases, the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field.
 
     :::{image} images/upgrade-agent-custom.png
     :alt: Menu for upgrading a single {{agent}}
diff --git a/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md b/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md
@@ -100,22 +100,28 @@ To send data to the {{motlp}} from the {{edot}} Collector or the contrib Collect
 ```yaml
 exporters:
   otlp:
-    endpoint: https://<motlp-endpoint>
+    endpoint: https://<motlp-endpoint> <1>
     headers:
-      Authorization: ApiKey <your-api-key>
+      Authorization: ApiKey <your-api-key> <2>
 ```
 
+1. The endpoint retrieved at [step 2](#locate-your-motlp)
+2. The API key created at [step 3](#create-an-api-key)
+
 Set the API key as an environment variable or directly in the configuration as shown in the example.
 :::
 
 :::{tab-item} OpenTelemetry SDK example
 To send data to the {{motlp}} from {{edot}} SDKs or contrib SDKs, set the following variables in your application's environment:
 
 ```bash
-export OTEL_EXPORTER_OTLP_ENDPOINT="https://<motlp-endpoint>"
-export OTEL_EXPORTER_OTLP_HEADERS="Authorization=ApiKey <your-api-key>"
+export OTEL_EXPORTER_OTLP_ENDPOINT="https://<motlp-endpoint>" <1>
+export OTEL_EXPORTER_OTLP_HEADERS="Authorization=ApiKey <your-api-key>" <2>
 ```
 
+1. The endpoint retrieved at [step 2](#locate-your-motlp)
+2. The API key created at [step 3](#create-an-api-key)
+
 Avoid extra spaces in the header. For Python SDKs replace any spaces with `%20`. For example:
 
 ```
@@ -141,11 +147,14 @@ Mount the secret as an environment variable or file, then reference it in your O
 ```yaml
 exporters:
   otlp:
-    endpoint: https://<motlp-endpoint>
+    endpoint: https://<motlp-endpoint> <1>
     headers:
-      Authorization: ${API_KEY}
+      Authorization: ${API_KEY} <2>
 ```
 
+1. The endpoint retrieved at [step 2](#locate-your-motlp)
+2. The API key created at [step 3](#create-an-api-key)
+
 And in your deployment spec:
 
 ```yaml
diff --git a/solutions/observability/incident-management/view-alerts.md b/solutions/observability/incident-management/view-alerts.md
@@ -94,7 +94,7 @@ Alert flapping is turned on by default. You can modify the criteria for changing
     Once a flapping alert is recovered, it cannot be changed to flapping again. Only new alerts with repeated status changes are candidates for the flapping status. 
 
 `untracked`
-:   The rule is disabled, or you’ve marked the alert as untracked. To mark the alert as untracked, go to the **Alerts** table, click the {icon}`boxes_horizontal` icon to expand the **More actions** menu, and click **Mark as untracked**. When an alert is marked as untracked, actions are no longer generated. You can choose to move active alerts to this state when you disable or delete rules.
+:   The rule is disabled, or you’ve marked the alert as untracked. To mark the alert as untracked, go to the **Alerts** table, click the {icon}`boxes_horizontal` icon to expand the **More actions** menu, and click **Mark as untracked**. When an alert is marked as untracked, actions are no longer generated and the alert's status can no longer be changed. You can choose to move active alerts to this state when you disable or delete rules.
 
 
 ## Customize the alerts table [observability-view-alerts-customize-the-alerts-table]
diff --git a/solutions/search/get-started.md b/solutions/search/get-started.md
@@ -21,11 +21,21 @@ New to {{es}}? Start building a search experience by setting up your first deplo
 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
+::::::{stepper}
+:::::{step} Choose your deployment type
 
 Elastic provides several self-managed and Elastic-managed options.
-For simplicity and speed, try out [{{es-serverless}}](/solutions/search/serverless-elasticsearch-get-started.md).
+For simplicity and speed, try out [{{es-serverless}}](/solutions/search/serverless-elasticsearch-get-started.md):
+
+::::{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:
 
@@ -34,17 +44,17 @@ 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
+:::::{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
+:::::
+:::::{{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.
@@ -54,18 +64,18 @@ To learn about adding data for other search goals, go to [](/solutions/search/in
 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).
-::::
+:::::
 
-::::{{step}} Build your search queries
+:::::{{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
 
diff --git a/solutions/search/get-started/keyword-search-python.md b/solutions/search/get-started/keyword-search-python.md
@@ -24,10 +24,11 @@ To follow the steps, you must have a recent version of a Python interpreter.
 
 ::::{step} Create a project
 
-Create an [{{es-serverless}}](/solutions/search/serverless-elasticsearch-get-started.md) general purpose project.
-To add the sample data, you must have a `developer` or `admin` predefined role or an equivalent custom role.
-To learn about role-based access control, go to [](/deploy-manage/users-roles/cluster-or-deployment-auth/user-roles.md).
+:::{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).
 ::::
 ::::{step} Create an index
 
diff --git a/solutions/search/ingest-for-search.md b/solutions/search/ingest-for-search.md
