Enhance and restructure AutoOps pages

deploy-manage/_snippets/autoops-callout-with-ech.md

@@ -1,5 +1,4 @@
 :::{admonition} Simplify monitoring with AutoOps
-Use AutoOps in your {{ech}}, ECE, ECK, or self-managed deployments. 
-
-AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
-::::
+:applies_to: { ess:, ece:, eck:, self:, "serverless": "ga" }
+AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. Learn more about [](/deploy-manage/monitor/autoops.md).
+:::

deploy-manage/_snippets/autoops-cc-ech-faq.md

@@ -1,3 +1,3 @@
 This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.
 
-For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md#ec-autoops-how-to-access) from the deployment overview page.
+For {{ech}} deployments, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) from the deployment overview page.

deploy-manage/deploy/elastic-cloud/serverless.md

@@ -20,7 +20,7 @@ products:
 Serverless projects use the core components of the {{stack}}, such as {{es}} and {{kib}}, and are based on an architecture that decouples compute and storage. Search and indexing operations are separated, which offers high flexibility for scaling your workloads while ensuring a high level of performance.
 
 :::{note}
-There are differences between {{es-serverless}} and {{ech}}, for a list of differences between them, see [differences between {{ech}} and {{es-serverless}}](../elastic-cloud.md#general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud).
+There are differences between {{es-serverless}} and {{ech}}. Learn more in [Compare {{ech}} and {{es-serverless}}](../elastic-cloud.md#general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud).
 :::
 
 ## Get started
@@ -55,6 +55,9 @@ Afterwards, you can:
   * **Data:** Choose the data you want to ingest and the method to ingest it. By default, data is stored indefinitely in your project, and you define the retention settings for your data streams.
   * **Performance:** For granular control over costs and query performance against your project data, serverless projects come with a set of predefined settings you can edit.
 
+:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md
+:::
+
 ## Monitor serverless status [general-serverless-status]
 
 Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.

deploy-manage/monitor.md

@@ -24,7 +24,7 @@ Depending on your deployment type, you can use a variety of solutions for monito
 
 You have several options for monitoring your cluster or deployment.
 
-Use [AutoOps](/deploy-manage/monitor/autoops.md) in your {{ech}}, ECE, ECK, or self-managed deployments. AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. 
+Use [](/deploy-manage/monitor/autoops.md) to simplify cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. 
 
 Alternatively, you can use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.
 
@@ -47,7 +47,8 @@ deployment:
 
 AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization.
 
-In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+:::{include} /deploy-manage/monitor/_snippets/autoops-availability.md
+:::
 
 ### Stack monitoring
 

deploy-manage/monitor/_snippets/autoops-availability.md

@@ -0,0 +1 @@
+AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect.

deploy-manage/monitor/autoops-vs-stack-monitoring.md

@@ -69,7 +69,7 @@ You can store your Stack Monitoring logs and metrics in the following ways:
 ### Availability
 
 #### AutoOps [ao-availability]
-AutoOps lives in {{ecloud}}, so you need to have an {{ecloud}} account to access it. Once logged in, you can [access](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) AutoOps from your hosted deployments.
+AutoOps lives in {{ecloud}}, so you need to have an {{ecloud}} account to access it. Once logged in, you can access AutoOps from your [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md), [{{serverless-short}} projects](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md), or [connect your self-managed clusters](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to it.
 
 #### Stack Monitoring [sm-availability]
 Once setup is complete, you can access the Stack Monitoring UI inside {{kib}}, where you can monitor all your {{stack}} components.

deploy-manage/monitor/autoops.md

@@ -23,8 +23,7 @@
 :alt: Screenshot showing the Overview page in AutoOps
 :::
 
-
-## AutoOps key features [ec_autoops_key_features]
+## Key features in AutoOps [ec_autoops_key_features]
 
 * Real-time root-cause analysis for hundreds of issues.
 * Accurate resolution paths and customized recommendations.
@@ -38,38 +37,43 @@
     * Unbalanced loads between nodes.
     * Indexing latency, rejections, search latency, high index/search queues, and slow queries.
     * Resource utilization.
+* Multi-deployment dashboard to quickly spot issues across all clusters.
+* Possibility to customize event triggers and connect to different notification services such as PagerDuty, Slack, MS Teams, and webhooks.
+* Coming soon: Long-term reports for sustained evaluation.
 
+## Regions where AutoOps is available
 
+Depending on your deployment type, AutoOps has been rolled out across various [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). More regions and CSPs are coming soon.
 
-## Additional capabilities [ec_additional_capabilities]
+## Deployment types where AutoOps is available
 
-* Multi-deployment dashboard to quickly spot issues across all clusters.
-* Possibility to customize event triggers and connect to different notification services such as PagerDuty, Slack, MS Teams, and webhooks.
-* Long-term reports for sustained evaluation. This feature is currently not available and will be rolled out shortly.
+:::{include} /deploy-manage/monitor/_snippets/autoops-availability.md
+:::
 
-## AutoOps availability
+AutoOps is currently not available for air-gapped environments because it's a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
 
-In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md).
+## How AutoOps is licensed
 
-AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
+For {{ech}} deployments and {{serverless-short}} projects, AutoOps is available to {{ecloud}} customers at all subscription levels at no additional cost, and it does not consume ECU.
+:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md
+:::
 
-## AutoOps retention period [ec_autoops_retention_period]
+## How long AutoOps retains data [ec_autoops_retention_period]
 
 AutoOps currently has a 10 day retention period.
 
+## What AutoOps monitors [ec_autoops_scope]
 
-## AutoOps scope [ec_autoops_scope]
-
-AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment information pertains solely to {{es}}. AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol)(7.17.x and above). We plan to expand AutoOps monitoring to the entire stack in the future.
+AutoOps currently only monitors {{es}}, not the entire {{stack}}. AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol)(7.17.x and above). We plan to expand AutoOps monitoring to the entire stack in the future.
 
 ## Section overview
 
 In this section, you'll find the following information:
 
-* How to [use AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md).
+* How to [access AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md).
 * How to [use AutoOps in your {{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md).
 * How to [connect your ECE, ECK, or self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) to AutoOps.
 * [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
-* What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).
 * Which [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into your deployment.
+* What AutoOps [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).
 * [Frequently asked questions](/deploy-manage/monitor/autoops/ec-autoops-faq.md) about AutoOps.

deploy-manage/monitor/autoops/autoops-for-serverless.md

@@ -69,7 +69,7 @@ Let’s say you ingest 1TB of data into your Observability project.
 * **Retention**: Given that 1GB retained per hour = [$0.018](https://www.elastic.co/pricing/serverless-observability) and assuming it took one hour to ingest 1TB of data, that 1TB will be billed 1.42GB for that slice of one hour (1TB/720 hours per month), which translates to $0.025. Each subsequent hour in that month will cost the same.
 :::
 
-## Coming soon
+## Coming soon to AutoOps for Serverless
 
 The following features are coming soon to AutoOps for {{serverless-short}}:
 
@@ -85,3 +85,6 @@ In this section, you'll find the following information:
 * How to use the [Search tier view](search-tier-view-autoops-serverless.md) to see the impact of search performance on your use of search VCUs.
 * How to use the [Search AI Lake view](search-ai-lake-view-autoops-serverless.md) to drill down into your storage-related usage.
 
+:::{tip}
+Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md) for answers to frequently asked questions about AutoOps.
+:::

deploy-manage/monitor/autoops/autoops-sm-troubleshoot-firewalls.md

@@ -0,0 +1,150 @@
+---
+applies_to:
+  deployment:
+    self:
+    ece:
+    eck:
+navigation_title: Firewalls blocking {{agent}}
+products:
+  - id: cloud-kubernetes
+  - id: cloud-enterprise
+---
+
+# Troubleshoot firewalls blocking {{agent}}
+
+If you are running into issues connecting your cluster to AutoOps, a corporate firewall might be blocking {{agent}}.
+
+There are [three main components](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md#how-your-self-managed-cluster-connects-to-autoops) of {{agent}}'s connection with your system:
+
+:::{include} /deploy-manage/monitor/_snippets/autoops-cc-components.md
+:::
+
+The following subsections describe how to test each of these components to find out where the problem lies, and then implement an appropriate solution.
+
+:::{tip}
+Run the following tests within the context of your execution environment. That is, if your chosen installation method is Kubernetes, run the commands from within the pod; for Docker, run the commands from within the container, and so on. 
+:::
+
+## 1. Test {{agent}}'s connection with your cluster
+If there is an issue with the first component, {{agent}} cannot connect to your cluster. 
+
+To test if your organization is not allowing this connection, run the following command depending on your chosen authentication method:
+
+:::::{tab-set}
+:group: api-key-or-basic
+
+::::{tab-item} API key
+:sync: api-key
+
+```json
+curl -XGET -i $AUTOOPS_ES_URL \
+-H "Authorization: ApiKey $AUTOOPS_ES_API_KEY"
+```
+::::
+
+::::{tab-item} Basic
+:sync: basic
+
+```json
+curl -XGET -i $AUTOOPS_ES_URL \
+-u $AUTOOPS_ES_USERNAME
+```
+::::
+
+:::::
+
+The command returns a response similar to the following:
+
+```json
+{
+"name" : "1c72f00a6195",
+"cluster_name" : "my-ccm-cluster",
+"cluster_uuid" : "2O_EjO6kTR6AEVYwL5fPEw",
+"version" : {
+"number" : "9.1.3",
+"build_flavor" : "default",
+"build_type" : "docker",
+"build_hash" : "0c781091a2f57de895a73a1391ff8426c0153c8d",
+"build_date" : "2025-08-24T22:05:04.526302670Z",
+"build_snapshot" : false,
+"lucene_version" : "10.2.2",
+"minimum_wire_compatibility_version" : "8.19.0",
+"minimum_index_compatibility_version" : "8.0.0"
+},
+"tagline" : "You Know, for Search"
+}
+```
+
+If you do not receive a similar response, your system returns an error indicating one or more reasons for the failure as outlined in the following table. Use the corresponding proposed solution to fix the issue.
+
+| Reason for failure | Proposed solution |
+| :--- | :--- |
+| The {{es}} endpoint URL you specified is incorrect/not reachable | - Make sure you are using the correct protocol in the cluster URL:`http` or `https`. <br> - Make sure you are providing the correct port. The default port is **9200**. <br> - If you have verified that the URL is correct, your network team might need to open the firewall to allow-list this URL. |
+| Your API key is incorrect | - Recheck for typos. <br> - If your cluster is on versions 9.1.0 through 9.1.3, ensure that you have the base64-decoded version of the key by running the following command: <br><br> `echo $AUTOOPS_ES_API_KEY | base64 -d` <br><br> If your key has a colon (:), it is not base64 encoded. If your key has an equal sign (=), it is base64 coded. <br> For versions 9.1.4 and above, both formats work.|
+| Your username or password is incorrect | - Recheck for typos. <br> - Ensure that your provided user has the [necessary privileges](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#configure-agent). We do not recommend providing a privileged superuser like `elastic` for this purpose.|
+| You are providing both the API key and username/password | Choose one type of authentication only. |
+| A proxy is blocking communication with your {{es}} cluster | You might have to [configure `NO_PROXY`](/reference/fleet/host-proxy-env-vars.md). |
+| You are using a custom SSL/TLS configuration with {{es}} | Disable SSL/TLS verification so that your system trusts all certificates. We do not recommend disabling verification in production environments. <br><br> If you are using API key authentication, run the following command: <br><br>`curl -XGET --insecure -i $AUTOOPS_ES_URL \ -H "Authorization: ApiKey $AUTOOPS_ES_API_KEY"`. <br><br> If you are using username/password authentication, run the following command: <br><br> `curl -XGET --insecure -i $AUTOOPS_ES_URL \ -u $AUTOOPS_ES_USERNAME` <br><br> If the issue is resolved, you need to configure your custom SSL/TLS settings with {{agent}}. If the issue persists, contact [Elastic support](https://support.elastic.co/).| 
+| You are connecting a local development cluster using Docker without specifying `--network host` | - Make sure you are following all the steps to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md#connect-your-local-development-cluster-to-autoops). <br> - In the [Install agent](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#install-agent) step, make sure you are replacing `docker run -d \` with `docker run -d --network host \`. |
+
+## 2. Test your cluster's registration with {{ecloud}} 
+
+If there is an issue with the second component, the agent stops working and your logs might show the following error: 
+
+```sh
+... failed to register Cloud Connected Mode: ... Post \"https://api.elastic-cloud.com/api/v1/cloud-connected/clusters\": ...
+```
+
+To test if your organization is not allowing the agent to register your cluster with {{ecloud}}, run the following command:
+
+```json
+curl -XPOST -i \
+https://api.elastic-cloud.com/api/v1/cloud-connected/clusters \
+-H 'Content-Type: application/json' \
+-d '{"self_managed_cluster": {"id": "my-cluster-uuid", "name": "my-cluster-name", "version": "9.1.0"}, "license": {"uid": "my-license-id", "type": "basic"}}'
+```
+
+The command should return an HTTP 401 response: 
+
+```json
+      {"UnauthorizedMessages":["Invalid credential headers"],"Cause":null}
+```
+If you do not receive a similar response, configure your HTTP proxy to allow it to reach the URL (with headers and a JSON body):
+
+```json
+      POST https://api.elastic-cloud.com/api/v1/cloud-connected/clusters
+```
+:::{note}
+If you are using Docker, you might need to complete this configuration directly using the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
+:::
+
+## 3. Test if {{agent}} is able to send metrics
+
+If there is an issue with the third component, the agent attempts to establish the connection and your logs might show the following error: 
+
+```sh
+... Exporting failed. Dropping data. ... no more retries left: failed to make an HTTP request: Post \"https://otel-collector.auto-ops.eu-west-1.aws.cloud.elastic.co:4318/v1/logs\": ...
+```
+
+To test if your organization is not allowing the agent to send metrics from your cluster to {{ecloud}}, run the following command. The command uses AWS eu-west-1 as the CSP (cloud service provider) region, but you should replace it with your chosen CSP region before running the command.
+
+```json
+curl -XPOST -i \
+https://otel-collector.auto-ops.eu-west-1.aws.cloud.elastic.co:4318/v1/logs \
+-H 'Content-Type: application/json'
+
+```
+The command should return an HTTP 401 response: 
+
+```json
+  {"code":16,"message":"no auth provided"}
+```
+
+If you do not receive a similar response, configure your HTTP proxy to allow it to reach the URL (with headers and an arbitrary body):
+
+```json
+  POST https://otel-collector.auto-ops.${REGION}.${CSP}.cloud.elastic.co:4318/v1/logs
+```
+:::{note}
+If you are using Docker, you might need to complete this configuration directly using the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables.
+:::