diff --git a/deploy-manage/_snippets/autoops-cc-ech-faq.md b/deploy-manage/_snippets/autoops-cc-ech-faq.md index 150165f54b..6100e72bc7 100644 --- a/deploy-manage/_snippets/autoops-cc-ech-faq.md +++ b/deploy-manage/_snippets/autoops-cc-ech-faq.md @@ -1,6 +1,3 @@ -:::{dropdown} 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. -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..2f615ea877 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,20 +23,19 @@ 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?](#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) -Each cloud connected service has its own licensing and payment requirements. +$$$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 +::: -:::{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 ::: -::: - -:::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md -::: - -:::{dropdown} 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. -::: +$$$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. 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..c443da844b 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -11,77 +11,73 @@ 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? - -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. - -When you need support, AutoOps gives the Elastic team real-time visibility into your cluster, leading to faster resolutions. - -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 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) + +**Questions about setting up** +* [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) + +**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) + +## 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. + +$$$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?** +: 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. + +## Questions about setting up +$$$cc-autoops-ech$$$ **Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?** +: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md ::: -:::{dropdown} Does this feature require additional payment? +$$$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. -:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md -::: +$$$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} Which versions of {{es}} does AutoOps support? +$$$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. -AutoOps is compatible with all [supported {{es}} versions](https://www.elastic.co/support/eol). -::: + 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. -:::{dropdown} Which deployment types can be connected to AutoOps? +: For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). -You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. -::: - -:::{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. -::: +## 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} Can I use macOS to install {{agent}} for this feature? + 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. -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}}? - -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. - -For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). -::: - -:::{dropdown} Where are AutoOps metrics stored, and does it cost extra to ship metrics 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. -::: - -:::{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: - -| 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 | -::: +$$$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 | 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..138dab2950 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -15,31 +15,23 @@ 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) -:::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md +$$$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 ::: -::: - -:::{dropdown} I need to uninstall {{agent}}. - -Refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md) for instructions. -::: - -:::{dropdown} My cluster was disconnected from {{ecloud}} and I want to reconnect it. +$$$unistall-agent$$$**I need to uninstall {{agent}}.** +: Refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md) for instructions. -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). +$$$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). -:::{include} /deploy-manage/monitor/_snippets/disconnect-cluster.md -::: - -::: - -:::{dropdown} 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). -::: +$$$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