From 5ba367e97a9fcca5d2b094ac209d530a1ccd0d79 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Mon, 25 Aug 2025 18:07:53 -0400 Subject: [PATCH 01/11] [AutoOps] Convert Cloud Connect dropdowns to lists --- deploy-manage/_snippets/autoops-cc-ech-faq.md | 8 +- deploy-manage/cloud-connect.md | 17 ++-- .../autoops/cc-cloud-connect-autoops-faq.md | 79 +++++++++---------- ...c-cloud-connect-autoops-troubleshooting.md | 23 +++++- 4 files changed, 72 insertions(+), 55 deletions(-) diff --git a/deploy-manage/_snippets/autoops-cc-ech-faq.md b/deploy-manage/_snippets/autoops-cc-ech-faq.md index 150165f54b..1681eca587 100644 --- a/deploy-manage/_snippets/autoops-cc-ech-faq.md +++ b/deploy-manage/_snippets/autoops-cc-ech-faq.md @@ -1,6 +1,4 @@ -:::{dropdown} Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? +$$$cloud-connect-ech$$$ Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? +: This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps. -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) from the deployment overview page. -::: \ No newline at end of file +: 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) from the deployment overview page. \ No newline at end of file diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index 0b4d4f6d74..c41b4c2d73 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -13,7 +13,7 @@ Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-m AutoOps is the first service available for use with Cloud Connect. More services are coming soon. -### AutoOps +## AutoOps [AutoOps](/deploy-manage/monitor/autoops.md) is a monitoring tool that helps you manage your cluster with real-time issue detection, performance recommendations, and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and your usage patterns, AutoOps recommends operational and monitoring insights that deliver real savings in administration time and hardware cost. @@ -23,11 +23,15 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou Find answers to your questions about Cloud Connect. -:::{dropdown} Does using Cloud Connect require additional payment? +* [Does using Cloud Connect require additional payment?](#cloud-connect-payment) +* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cloud-connect-ech) +* [Are more services going to be available with Cloud Connect?](#more-cloud-connected-services) -Each cloud connected service has its own licensing and payment requirements. +$$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? -:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +: Each cloud connected service has its own licensing and payment requirements. + +: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: ::: @@ -35,8 +39,7 @@ Each cloud connected service has its own licensing and payment requirements. :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: -:::{dropdown} Are more services going to be available with Cloud Connect? +$$$more-cloud-connected-services$$$Are more services going to be available with Cloud Connect? -Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. -::: +: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index c4623b7d39..cf1546842b 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -11,64 +11,63 @@ navigation_title: FAQ Find answers to your questions about AutoOps for ECE, ECK, and self-managed clusters. -:::{dropdown} Why should I use AutoOps for my clusters? +**General questions** +* [Why should I use AutoOps for my clusters?](#why-autoops) +* [Does this feature require additional payment?](#additional-payment) +* [Which versions of {{es}} does AutoOps support?](#es-versions) +* [Which deployment types can be connected to AutoOps?](#deployment-types) -AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. +**Questions about setting up** +* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cloud-connect-ech) +* [Can I use AutoOps for my clusters if my environment is air-gapped?](#autoops-air-gapped) +* [Can I use macOS to install {{agent}} for this feature?](#macos-install) +* [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address) -When you need support, AutoOps gives the Elastic team real-time visibility into your cluster, leading to faster resolutions. +**Questions about collected metrics** +* [Where are AutoOps metrics stored, and does it cost extra to ship metrics data to {{ecloud}}?](#autoops-metrics) +* [What information does {{agent}} extract from my cluster?](#extracted-info) -Using AutoOps for your ECE, ECK, and self-managed clusters lets you access all these capabilities without the operational overhead of managing their infrastructure. -::: +## General questions +$$$why-autoops$$$ Why should I use AutoOps for my clusters? +: AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. -:::{dropdown} Does this feature require additional payment? +$$$additional-payment$$$ Does this feature require additional payment? +: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +::: -:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md -::: +$$$es-versions$$$ Which versions of {{es}} does AutoOps support? +: AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol). -::: +$$$deployment-types$$$ Which deployment types can be connected to AutoOps? +: You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. -:::{dropdown} Which versions of {{es}} does AutoOps support? - -AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol). -::: - -:::{dropdown} Which deployment types can be connected to AutoOps? - -You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. +## Questions about setting up ::: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: -:::{dropdown} Can I use AutoOps for my clusters if my environment is air-gapped? - -Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. -::: - -:::{dropdown} Can I use macOS to install {{agent}} for this feature? +$$$autoops-air-gapped$$$ Can I use AutoOps for my clusters if my environment is air-gapped? +: Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. -macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps. -::: +$$$macos-install$$$ Can I use macOS to install {{agent}} for this feature? +: macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps. -:::{dropdown} Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? +$$$elastic-ip-address$$$ Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? +: You may need to define an IP address if your organization’s settings will block the agent from sending out data. -You may need to define an IP address if your organization’s settings will block the agent from sending out data. +: To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. -To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. +: For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). -For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). -::: +## Questions about collected metrics +$$$autoops-metrics$$$ Where are AutoOps metrics stored, and does it cost extra to ship metrics data to {{ecloud}}? +: You can choose the CSP and region in which your cluster metrics will be stored from a list of [available regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). -:::{dropdown} Where are AutoOps metrics stored, and does it cost extra to ship metrics to {{ecloud}}? +: Shipping metrics to {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. -You can choose the CSP and region in which your cluster metrics will be stored from a list of [available regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). - -Shipping metrics to {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. -::: - -:::{dropdown} What information does {{agent}} extract from my cluster? - -{{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: +$$$extracted-info$$$ What information does {{agent}} extract from my cluster? +: {{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: | API | Description | Collected data | | --- | --- | --- | @@ -82,6 +81,4 @@ Shipping metrics to {{ecloud}} may come at an additional cost. For example, when | [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details | | [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format | | [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects | -::: - diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index 612bbebac2..83ada84e5a 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -15,7 +15,25 @@ Learn about issues that might come up when connecting your clusters and using Au Use this guide to troubleshoot any issues you may encounter. -:::{dropdown} I’m trying to create a Cloud organization, but I’m already part of a different one. +* [I’m trying to create a Cloud organization, but I’m already part of a different one.](#single-cloud-org) +* [I need to uninstall {{agent}}.](#unistall-agent) +* [My cluster was disconnected from {{ecloud}} and I want to reconnect it.](#disconnected-cluster) +* [After running the installation command, I can't move on to the next steps.](#next-steps) + +$$$single-cloud-org$$$ I’m trying to create a Cloud organization, but I’m already part of a different one. +: :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md +::: + +$$$unistall-agent$$$I need to uninstall {{agent}}. +: Refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md) for instructions. + +$$$disconnected-cluster$$$My cluster was disconnected from {{ecloud}} and I want to reconnect it. +: If the cluster was disconnected by one of the users in your Cloud organization, you can repeat the [installation process](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to reconnect. If not, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). + +$$$next-steps$$$After running the installation command, I can't move on to the next steps. +: If an error appears on the screen, follow the suggestion in the error message and try to run the command again. If the issue is not resolved, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). + + ## Potential errors From 6d1d9614bd97ca9ac084f6493db03a065b850fd1 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 11:02:01 -0400 Subject: [PATCH 02/11] Remove extra character --- deploy-manage/cloud-connect.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index c41b4c2d73..cb75571919 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -34,8 +34,6 @@ $$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? : :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: -::: - :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: From 36abbee76001edc689ee719fedb118e2bd3807f7 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 11:10:10 -0400 Subject: [PATCH 03/11] build error --- deploy-manage/cloud-connect.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index cb75571919..4af48da547 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -32,6 +32,8 @@ $$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? : Each cloud connected service has its own licensing and payment requirements. : :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +: ::: + ::: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md From c28dbb1fd6e5d5555f97ff94bd5113fc60247706 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 13:16:27 -0400 Subject: [PATCH 04/11] testing build fix --- deploy-manage/cloud-connect.md | 20 -------------------- 1 file changed, 20 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index 4af48da547..e814de97ea 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -21,25 +21,5 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou ## FAQ -Find answers to your questions about Cloud Connect. -* [Does using Cloud Connect require additional payment?](#cloud-connect-payment) -* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cloud-connect-ech) -* [Are more services going to be available with Cloud Connect?](#more-cloud-connected-services) - -$$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? - -: Each cloud connected service has its own licensing and payment requirements. - -: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md -: ::: - -::: - -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md -::: - -$$$more-cloud-connected-services$$$Are more services going to be available with Cloud Connect? - -: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. From c282f1f00c4d84ea96ba69553d1ac5e8ecf8ff3a Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 13:36:39 -0400 Subject: [PATCH 05/11] build fix --- deploy-manage/cloud-connect.md | 16 +++++++++++ ...c-cloud-connect-autoops-troubleshooting.md | 27 ------------------- 2 files changed, 16 insertions(+), 27 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index e814de97ea..baed5ebd8d 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -21,5 +21,21 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou ## FAQ +Find answers to your questions about Cloud Connect. +* [Does using Cloud Connect require additional payment?](#cloud-connect-payment) +* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cloud-connect-ech) +* [Are more services going to be available with Cloud Connect?](#more-cloud-connected-services) + +$$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? +: Each cloud connected service has its own licensing and payment requirements. +: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +::: + +::: +:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +::: + +$$$more-cloud-connected-services$$$Are more services going to be available with Cloud Connect? +: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index 83ada84e5a..c8a03bfa47 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -33,33 +33,6 @@ $$$disconnected-cluster$$$My cluster was disconnected from {{ecloud}} and I want $$$next-steps$$$After running the installation command, I can't move on to the next steps. : If an error appears on the screen, follow the suggestion in the error message and try to run the command again. If the issue is not resolved, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). - - ## Potential errors The following table shows the errors you might encounter if something goes wrong while you set up and use AutoOps on your clusters. From 05b86ac37cbf01da005218e8d02e2d0e87de7fb3 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 13:49:27 -0400 Subject: [PATCH 06/11] narrowing down error --- deploy-manage/cloud-connect.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index baed5ebd8d..a46163f1f8 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -32,10 +32,6 @@ $$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? : :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: -::: -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md -::: - $$$more-cloud-connected-services$$$Are more services going to be available with Cloud Connect? : Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. From 8f532d9d9916214e059aea9d668cdf15970fabe7 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 14:05:57 -0400 Subject: [PATCH 07/11] build fix attempt 2 --- deploy-manage/_snippets/autoops-cc-ech-faq.md | 5 ++--- deploy-manage/cloud-connect.md | 10 +++++++--- .../monitor/autoops/cc-cloud-connect-autoops-faq.md | 7 +++---- 3 files changed, 12 insertions(+), 10 deletions(-) diff --git a/deploy-manage/_snippets/autoops-cc-ech-faq.md b/deploy-manage/_snippets/autoops-cc-ech-faq.md index 1681eca587..6100e72bc7 100644 --- a/deploy-manage/_snippets/autoops-cc-ech-faq.md +++ b/deploy-manage/_snippets/autoops-cc-ech-faq.md @@ -1,4 +1,3 @@ -$$$cloud-connect-ech$$$ Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? -: This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps. +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) from the deployment overview page. \ No newline at end of file +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) from the deployment overview page. \ No newline at end of file diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index a46163f1f8..3bfbab1a15 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -24,14 +24,18 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou Find answers to your questions about Cloud Connect. * [Does using Cloud Connect require additional payment?](#cloud-connect-payment) -* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cloud-connect-ech) +* [Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?](#cloud-connect-ech) * [Are more services going to be available with Cloud Connect?](#more-cloud-connected-services) $$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? -: Each cloud connected service has its own licensing and payment requirements. +: Each cloud connected service has its own licensing and payment requirements. : :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: +$$$cloud-connect-ech$$$Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps? +: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +::: + $$$more-cloud-connected-services$$$Are more services going to be available with Cloud Connect? -: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. +: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index cf1546842b..0327ca0baa 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -18,7 +18,7 @@ Find answers to your questions about AutoOps for ECE, ECK, and self-managed clus * [Which deployment types can be connected to AutoOps?](#deployment-types) **Questions about setting up** -* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cloud-connect-ech) +* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech) * [Can I use AutoOps for my clusters if my environment is air-gapped?](#autoops-air-gapped) * [Can I use macOS to install {{agent}} for this feature?](#macos-install) * [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address) @@ -42,9 +42,8 @@ $$$deployment-types$$$ Which deployment types can be connected to AutoOps? : You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. ## Questions about setting up -::: - -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +$$$cc-autoops-ech$$$ Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? +: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: $$$autoops-air-gapped$$$ Can I use AutoOps for my clusters if my environment is air-gapped? From d0ea28d555764805fa18d1e8350639a0020179c8 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Tue, 26 Aug 2025 14:51:34 -0400 Subject: [PATCH 08/11] reformatting --- deploy-manage/cloud-connect.md | 18 +++++------- .../autoops/cc-cloud-connect-autoops-faq.md | 28 +++++++++---------- 2 files changed, 21 insertions(+), 25 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index 3bfbab1a15..d23af6067d 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -23,19 +23,15 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou Find answers to your questions about Cloud Connect. -* [Does using Cloud Connect require additional payment?](#cloud-connect-payment) -* [Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?](#cloud-connect-ech) -* [Are more services going to be available with Cloud Connect?](#more-cloud-connected-services) - -$$$cloud-connect-payment$$$Does using Cloud Connect require additional payment? -: Each cloud connected service has its own licensing and payment requirements. -: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +### Does using Cloud Connect require additional payment? +Each cloud connected service has its own licensing and payment requirements. +:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: -$$$cloud-connect-ech$$$Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps? -: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +### Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps? +:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: -$$$more-cloud-connected-services$$$Are more services going to be available with Cloud Connect? -: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. +### Are more services going to be available with Cloud Connect? +Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index 0327ca0baa..857004fe78 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -55,7 +55,7 @@ $$$macos-install$$$ Can I use macOS to install {{agent}} for this feature? $$$elastic-ip-address$$$ Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? : You may need to define an IP address if your organization’s settings will block the agent from sending out data. -: To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. + To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. : For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). @@ -63,21 +63,21 @@ $$$elastic-ip-address$$$ Do I have to define an Elastic IP address to enable the $$$autoops-metrics$$$ Where are AutoOps metrics stored, and does it cost extra to ship metrics data to {{ecloud}}? : You can choose the CSP and region in which your cluster metrics will be stored from a list of [available regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). -: Shipping metrics to {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. + Shipping metrics to {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. $$$extracted-info$$$ What information does {{agent}} extract from my cluster? : {{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: -| API | Description | Collected data | -| --- | --- | --- | -| [_cat/shards](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards) | Returns detailed information about the shards within the cluster | Shard states, node allocation, index names, sizes, and replica information | -| [_nodes/stats](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) | Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics | CPU usage, memory utilization, thread pools, file system stats | -| [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations | -| [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards | -| [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings | -| [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases | -| [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings | -| [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details | -| [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format | -| [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects | + | API | Description | Collected data | + | --- | --- | --- | + | [_cat/shards](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards) | Returns detailed information about the shards within the cluster | Shard states, node allocation, index names, sizes, and replica information | + | [_nodes/stats](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) | Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics | CPU usage, memory utilization, thread pools, file system stats | + | [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations | + | [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards | + | [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings | + | [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases | + | [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings | + | [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details | + | [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format | + | [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects | From 24abbf9a29432da17ea992c8c21fd65a9b8c9644 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Wed, 27 Aug 2025 16:30:26 -0400 Subject: [PATCH 09/11] making questions bold --- .../autoops/cc-cloud-connect-autoops-faq.md | 20 +++++++++---------- ...c-cloud-connect-autoops-troubleshooting.md | 8 ++++---- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md index 857004fe78..c443da844b 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -28,31 +28,31 @@ Find answers to your questions about AutoOps for ECE, ECK, and self-managed clus * [What information does {{agent}} extract from my cluster?](#extracted-info) ## General questions -$$$why-autoops$$$ Why should I use AutoOps for my clusters? +$$$why-autoops$$$ **Why should I use AutoOps for my clusters?** : AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. -$$$additional-payment$$$ Does this feature require additional payment? +$$$additional-payment$$$ **Does this feature require additional payment?** : :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: -$$$es-versions$$$ Which versions of {{es}} does AutoOps support? +$$$es-versions$$$ **Which versions of {{es}} does AutoOps support?** : AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol). -$$$deployment-types$$$ Which deployment types can be connected to AutoOps? +$$$deployment-types$$$ **Which deployment types can be connected to AutoOps?** : You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. ## Questions about setting up -$$$cc-autoops-ech$$$ Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps? +$$$cc-autoops-ech$$$ **Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?** : :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: -$$$autoops-air-gapped$$$ Can I use AutoOps for my clusters if my environment is air-gapped? +$$$autoops-air-gapped$$$ **Can I use AutoOps for my clusters if my environment is air-gapped?** : Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. -$$$macos-install$$$ Can I use macOS to install {{agent}} for this feature? +$$$macos-install$$$ **Can I use macOS to install {{agent}} for this feature?** : macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps. -$$$elastic-ip-address$$$ Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}? +$$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?** : You may need to define an IP address if your organization’s settings will block the agent from sending out data. To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. @@ -60,12 +60,12 @@ $$$elastic-ip-address$$$ Do I have to define an Elastic IP address to enable the : For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). ## Questions about collected metrics -$$$autoops-metrics$$$ Where are AutoOps metrics stored, and does it cost extra to ship metrics data to {{ecloud}}? +$$$autoops-metrics$$$ **Where are AutoOps metrics stored, and does it cost extra to ship metrics data to {{ecloud}}?** : You can choose the CSP and region in which your cluster metrics will be stored from a list of [available regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). Shipping metrics to {{ecloud}} may come at an additional cost. For example, when sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. -$$$extracted-info$$$ What information does {{agent}} extract from my cluster? +$$$extracted-info$$$ **What information does {{agent}} extract from my cluster?** : {{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: | API | Description | Collected data | diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md index c8a03bfa47..138dab2950 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -20,17 +20,17 @@ Use this guide to troubleshoot any issues you may encounter. * [My cluster was disconnected from {{ecloud}} and I want to reconnect it.](#disconnected-cluster) * [After running the installation command, I can't move on to the next steps.](#next-steps) -$$$single-cloud-org$$$ I’m trying to create a Cloud organization, but I’m already part of a different one. +$$$single-cloud-org$$$**I’m trying to create a Cloud organization, but I’m already part of a different one.** : :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md ::: -$$$unistall-agent$$$I need to uninstall {{agent}}. +$$$unistall-agent$$$**I need to uninstall {{agent}}.** : Refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md) for instructions. -$$$disconnected-cluster$$$My cluster was disconnected from {{ecloud}} and I want to reconnect it. +$$$disconnected-cluster$$$**My cluster was disconnected from {{ecloud}} and I want to reconnect it.** : If the cluster was disconnected by one of the users in your Cloud organization, you can repeat the [installation process](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to reconnect. If not, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). -$$$next-steps$$$After running the installation command, I can't move on to the next steps. +$$$next-steps$$$**After running the installation command, I can't move on to the next steps.** : If an error appears on the screen, follow the suggestion in the error message and try to run the command again. If the issue is not resolved, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). ## Potential errors From 79deb7c09f9230ba61f849b379896be9250c6c10 Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Thu, 28 Aug 2025 13:47:33 -0400 Subject: [PATCH 10/11] retry definintion list on Cloud Connect --- deploy-manage/cloud-connect.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index d23af6067d..41776a8ac8 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -23,6 +23,24 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou Find answers to your questions about Cloud Connect. +* [Does using Cloud Connect require additional payment?](#cc-additional-payment) +* [Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?](#cc-ech) +* [Are more services going to be available with Cloud Connect?](#cc-more-services) + +$$$cc-additional-payment$$$ **Does using Cloud Connect require additional payment?** +: Each cloud connected service has its own licensing and payment requirements. + :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +::: + +$$$cc-ech$$$ **Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?** +: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +::: + +$$$cc-more-services$$$ **Are more services going to be available with Cloud Connect?** +: Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. + +Find answers to your questions about Cloud Connect. + ### Does using Cloud Connect require additional payment? Each cloud connected service has its own licensing and payment requirements. :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md From 57329f445ad9970362c30909636889ae79c094ea Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Thu, 28 Aug 2025 13:52:09 -0400 Subject: [PATCH 11/11] remove headings --- deploy-manage/cloud-connect.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index 41776a8ac8..2f615ea877 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -39,17 +39,3 @@ $$$cc-ech$$$ **Can I use Cloud Connect to connect my Elastic Cloud Hosted cluste $$$cc-more-services$$$ **Are more services going to be available with Cloud Connect?** : Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. -Find answers to your questions about Cloud Connect. - -### Does using Cloud Connect require additional payment? -Each cloud connected service has its own licensing and payment requirements. -:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md -::: - -### Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps? -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md -::: - -### Are more services going to be available with Cloud Connect? -Yes. AutoOps is the first of many cloud connected services to come. The next planned service is the Elastic Inference Service (EIS), which will provide GPU-powered inference for use cases like semantic search and text embeddings. -