diff --git a/deploy-manage/_snippets/autoops-cc-ech-faq.md b/deploy-manage/_snippets/autoops-cc-ech-faq.md index 6100e72bc7..9fbb7fa288 100644 --- a/deploy-manage/_snippets/autoops-cc-ech-faq.md +++ b/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) 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#ec-autoops-how-to-access) 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 2f615ea877..884bd94e80 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -23,11 +23,11 @@ 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) +* [Does 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?** +$$$cc-additional-payment$$$ **Does 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 ::: diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index 57fb163c7b..e3338e4d39 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/deploy-manage/cloud-organization/billing/billing-faq.md @@ -3,6 +3,9 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-faq-billing.html applies_to: deployment: + self: + ece: + eck: ess: all serverless: all products: @@ -29,6 +32,7 @@ This frequently-asked-questions list answers some of your more common questions * [How can I delete my {{ecloud}} account?](#faq-deleteaccount) * [Can I get a refund?](#faq-refund) * [What is included in my paid {{ecloud}} deployment?](#faq-included) +* [Does Cloud Connect require additional payment?](#billing-cc-additional-payment) * [What are the data transfer and storage charges and how can I control them?](#faq-dts) * [What taxes will be applied on my invoice?](#faq-taxes) @@ -94,6 +98,9 @@ $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account? $$$faq-refund$$$Can I get a refund? : Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md). +$$$billing-cc-additional-payment$$$ **Does Cloud Connect require additional payment?** +: Each cloud connected service has its own licensing and payment requirements. For more information, refer to the [Elastic self-managed subscriptions](https://www.elastic.co/subscriptions) page. + $$$faq-included$$$What is included in my paid {{ech}} deployment? : All subscription tiers for {{ech}} include the following free allowance: diff --git a/deploy-manage/deploy/deployment-comparison.md b/deploy-manage/deploy/deployment-comparison.md index 1c3e4efef8..2beb1adffc 100644 --- a/deploy-manage/deploy/deployment-comparison.md +++ b/deploy-manage/deploy/deployment-comparison.md @@ -30,7 +30,7 @@ For more details about feature availability in Serverless, check [](elastic-clou | Feature/capability | Self-managed | {{ech}} | Serverless | |-------------------|-------------|--------------------------------|-------------------------| -| [Deployment health monitoring](/deploy-manage/monitor.md) | Monitoring cluster | AutoOps or monitoring cluster | Managed by Elastic | +| [Deployment health monitoring](/deploy-manage/monitor.md) | AutoOps or monitoring cluster | AutoOps or monitoring cluster | Managed by Elastic | | [Alerting](/explore-analyze/alerts-cases.md) | Watcher or {{kib}} alerts | Watcher or {{kib}} alerts | Alerts ([why?](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#elasticsearch-differences-serverless-features-replaced)) | ## Data lifecycle diff --git a/deploy-manage/images/cloud-autoops-deployment-view.png b/deploy-manage/images/cloud-autoops-deployment-view.png deleted file mode 100644 index d38e57dbf9..0000000000 Binary files a/deploy-manage/images/cloud-autoops-deployment-view.png and /dev/null differ diff --git a/deploy-manage/images/cloud-autoops-setup.png b/deploy-manage/images/cloud-autoops-setup.png index e636463e63..ed950c774e 100644 Binary files a/deploy-manage/images/cloud-autoops-setup.png and b/deploy-manage/images/cloud-autoops-setup.png differ diff --git a/deploy-manage/images/self-managed-autoops-setup.png b/deploy-manage/images/self-managed-autoops-setup.png new file mode 100644 index 0000000000..31d1464586 Binary files /dev/null and b/deploy-manage/images/self-managed-autoops-setup.png differ diff --git a/deploy-manage/monitor.md b/deploy-manage/monitor.md index b3c19faf5f..de6b9226cf 100644 --- a/deploy-manage/monitor.md +++ b/deploy-manage/monitor.md @@ -36,11 +36,14 @@ To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-st ```{applies_to} deployment: ess: + self: + ece: + eck: ``` 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. -AutoOps is currently only available for Elastic Cloud Hosted deployments. +AutoOps is available in all {{ech}} deployments and {{serverless-full}} projects, and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). ### Stack monitoring diff --git a/deploy-manage/monitor/autoops-vs-stack-monitoring.md b/deploy-manage/monitor/autoops-vs-stack-monitoring.md index 7c9f43fb77..77fbd57d52 100644 --- a/deploy-manage/monitor/autoops-vs-stack-monitoring.md +++ b/deploy-manage/monitor/autoops-vs-stack-monitoring.md @@ -1,11 +1,16 @@ --- applies_to: + serverless: deployment: ess: all ece: all eck: all self: all navigation_title: AutoOps vs. Stack Monitoring +products: + - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # AutoOps and Stack Monitoring comparison @@ -26,18 +31,24 @@ With Stack Monitoring, you are responsible for storing your monitoring data. Thi ### Setup #### AutoOps [ao-setup] -On {{ech}} (ECH), AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), with no action required from you. - -:::{note} -AutoOps is planned to be available in self-managed environments in the future. -::: +On {{ech}} and {{serverless-full}}, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), with no action required from you. :::{image} /deploy-manage/images/cloud-autoops-setup.png :alt: Diagram showing AutoOps setup in Elastic Cloud ::: +For {{ece}} (ECE), {{eck}} (ECK), and self-managed clusters, you need to [connect your cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md). This involves installing {{agent}} to ship your monitoring metrics to {{ecloud}} through [](/deploy-manage/cloud-connect.md). Since you can only access AutoOps from the {{ecloud}} UI, you need an {{ecloud}} account for this service. + +:::{image} /deploy-manage/images/self-managed-autoops-setup.png +:alt: Diagram showing AutoOps setup for ECE, ECK, and self-managed clusters +::: + +:::{note} +AutoOps will be available for self-managed air-gapped environments (ECE, ECK, or standard stack deployments) in the future. +::: + #### Stack Monitoring [sm-setup] -Stack Monitoring is a {{kib}} application that can be enabled on self-managed clusters on your premises, ECH deployments, {{eck}} (ECK), and {{ece}} (ECE). Stack Monitoring is not available on {{serverless-full}} since Elastic takes care of monitoring and managing your Serverless projects. +Stack Monitoring is a {{kib}} application that can be enabled on self-managed clusters on your premises, {{ech}} deployments, {{ece}} (ECE), and {{eck}} (ECK). Stack Monitoring is not available on {{serverless-full}} since Elastic takes care of monitoring and managing your Serverless projects. Depending on your deployment model, there is [some setting up](/deploy-manage/monitor/stack-monitoring.md#configure-and-use-stack-monitoring) involved to enable Stack Monitoring. You need to configure an agent, specify which logs and metrics you want to collect from all your {{stack}} components, and where to send them. diff --git a/deploy-manage/monitor/autoops.md b/deploy-manage/monitor/autoops.md index 08b90c9f60..268407018b 100644 --- a/deploy-manage/monitor/autoops.md +++ b/deploy-manage/monitor/autoops.md @@ -4,8 +4,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # AutoOps [ec-autoops] @@ -43,7 +48,7 @@ AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing r ## AutoOps retention period [ec_autoops_retention_period] -AutoOps currently has a four-day retention period for all {{ech}} customers. +AutoOps currently has a four-day retention period. ## AutoOps scope [ec_autoops_scope] @@ -55,7 +60,8 @@ AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment In this section, you'll find the following information: -* How to [open AutoOps](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) for your deployment. +* How to [access AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md). +* How to [connect your ECE, ECK, or self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) to AutoOps. * 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. * [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available. diff --git a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md index 4b12c585af..2773f3291f 100644 --- a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md +++ b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md @@ -4,7 +4,10 @@ applies_to: self: ece: eck: -navigation_title: AutoOps for self-managed clusters +navigation_title: For self-managed clusters +products: + - id: cloud-kubernetes + - id: cloud-enterprise --- # AutoOps for self-managed clusters 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 4c54472046..ef9c129d65 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md @@ -5,6 +5,9 @@ applies_to: ece: eck: navigation_title: FAQ +products: + - id: cloud-kubernetes + - id: cloud-enterprise --- # AutoOps for self-managed clusters FAQ @@ -16,7 +19,7 @@ Find answers to your questions about AutoOps for ECE, ECK, and self-managed clus * [Does this feature require additional payment?](#additional-payment) * [Is there an added cost for shipping metrics data to {{ecloud}}?](#autoops-metrics-cost) * [Which versions of {{es}} does AutoOps support?](#es-versions) -* [Which deployment types can be connected to AutoOps?](#deployment-types) +* [Which deployment types can be connected to AutoOps through Cloud Connect?](#deployment-types) **Questions about setting up** * [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech) @@ -45,7 +48,7 @@ $$$autoops-metrics-cost$$$ **Is there an added cost for shipping metrics data to $$$es-versions$$$ **Which versions of {{es}} does AutoOps support?** : AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). -$$$deployment-types$$$ **Which deployment types can be connected to AutoOps?** +$$$deployment-types$$$ **Which deployment types can be connected to AutoOps through Cloud Connect?** : You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. ## Questions about setting up 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 e1ba71ecc4..0a6fd44f75 100644 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md +++ b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md @@ -5,6 +5,9 @@ applies_to: ece: eck: navigation_title: Troubleshooting +products: + - id: cloud-kubernetes + - id: cloud-enterprise --- # AutoOps for self-managed clusters troubleshooting diff --git a/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md index b59af94708..a3147131c4 100644 --- a/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md @@ -3,6 +3,9 @@ applies_to: deployment: self: navigation_title: Connect your local development cluster +products: + - id: cloud-kubernetes + - id: cloud-enterprise --- # Connect your local development cluster to AutoOps diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index 6596902c9a..e386300539 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -5,6 +5,9 @@ applies_to: ece: eck: navigation_title: Connect your self-managed cluster +products: + - id: cloud-kubernetes + - id: cloud-enterprise --- # Connect your self-managed cluster to AutoOps @@ -25,15 +28,16 @@ Ensure your system meets the following requirements before proceeding: * Your cluster is on an [Enterprise self-managed license](https://www.elastic.co/subscriptions) or an active self-managed [trial](https://cloud.elastic.co/registration). * The agent you install for the connection is allowed to send metrics to {{ecloud}}. -## Connect to AutoOps (private preview) [connect-to-autoops] +## Connect to AutoOps [connect-to-autoops] :::{note} :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md ::: ::: -The following steps describe how to connect to AutoOps during the private preview of AutoOps for self-managed clusters. +The following steps describe how to connect your ECE, ECK, or self-managed cluster to AutoOps. + :::::{tab-set} :group: existing-or-new-cloud-account @@ -70,6 +73,7 @@ If you already have an {{ecloud}} account: 1. Log in to [{{ecloud}}](https://cloud.elastic.co?page=docs&placement=docs-body). 2. On your home page, in the **Connected clusters** section, select **Connect self-managed cluster**. 3. On the **Connect your self-managed cluster** page, in the **AutoOps** section, select **Connect**. +4. Go through the installation wizard as detailed in the following sections. :::: ::::{tab-item} New account @@ -82,7 +86,7 @@ If you don’t have an existing {{ecloud}} account: :::: ::::: ---> + ### Select installation method diff --git a/deploy-manage/monitor/autoops/cc-manage-users.md b/deploy-manage/monitor/autoops/cc-manage-users.md index 2a5d9f9c90..d3794d3150 100644 --- a/deploy-manage/monitor/autoops/cc-manage-users.md +++ b/deploy-manage/monitor/autoops/cc-manage-users.md @@ -5,6 +5,9 @@ applies_to: ece: eck: navigation_title: Manage connected cluster users +products: + - id: cloud-kubernetes + - id: cloud-enterprise --- # Manage connected cluster users diff --git a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md index a4acffb06c..ea10c43f43 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md @@ -1,21 +1,22 @@ --- -navigation_title: Deployment +navigation_title: Deployment or Cluster mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-deployment-view.html applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- -# Deployment view in AutoOps [ec-autoops-deployment-view] +# Deployment or Cluster view in AutoOps [ec-autoops-deployment-view] -The **Deployment** view is the event control panel that allows you to see which issues are affecting the {{es}} cluster and get a list of action items to address them. - -:::{image} /deploy-manage/images/cloud-autoops-deployment-view.png -:alt: The Deployment view -::: +The **Deployment** view (for {{ECH}} deployments) or **Cluster** view (for ECE, ECK, and self-managed clusters), is the event control panel that allows you to see which issues are affecting the {{es}} cluster and get a list of action items to address them. ## Events over time [ec-autoops-events-over-time] @@ -34,9 +35,9 @@ The **Open Events** panel lists open events sorted by severity and time. When th The **Events History** panel lists events that happened at some point and that have been triggered, but some conditions changed and are no longer active. For example, when your cluster experiences a peak in search rate, that might trigger a "Too many tasks on queue" event. Now, your cluster is more relaxed in terms of search rate, so this event is no longer an issue, but it was recorded for historical reasons. Events history is also sorted by severity first and then by time. -## Deployment Resources [ec-deployment-resources] +## Resources [ec-deployment-resources] -The **Deployment Resources** panel provides a quick overview of Elasticsearch cluster resource usage. The resources are presented based on their respective data tiers and include JVM memory usage, CPU usage, and storage usage over time. You can view essential cluster information such as the Elasticsearch version, total number of nodes, total shards, and total used storage. +The **Resources** panel provides a quick overview of {{es}} cluster resource usage. The resources are presented based on their respective data tiers and include JVM memory usage, CPU usage, and storage usage over time. You can view essential cluster information such as the {{es}} version, total number of nodes, total number of shards, and total volume of used storage. :::{image} /deploy-manage/images/cloud-autoops-deployment-resources.png :alt: The AutoOps Resources panel @@ -51,7 +52,7 @@ The **Performance** panel shows key performance metrics, aggregated at both the :alt: The AutoOps Deployment Performance ::: -* **Search rate**: The number of search requests executed per second across all shards in the deployment, as well as within the selected data tiers. -* **Search latency**: The average latency of search operations across all shards in the deployment, and within the selected data tiers. -* **Indexing rate**: The number of documents indexed per second across all shards in the deployment, as well as within the selected data tiers. -* **Indexing latency**: The average latency of indexing operations across all shards in the deployment, and within the selected data tiers. +* **Search rate**: The number of search requests executed per second across all shards in the deployment or cluster, as well as within the selected data tiers. +* **Search latency**: The average latency of search operations across all shards in the deployment or cluster, and within the selected data tiers. +* **Indexing rate**: The number of documents indexed per second across all shards in the deployment or cluster, as well as within the selected data tiers. +* **Indexing latency**: The average latency of indexing operations across all shards in the deployment or cluster, and within the selected data tiers. diff --git a/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md b/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md index 54a618eada..4c6a4c51cb 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md +++ b/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md @@ -4,8 +4,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Dismiss Events [ec-autoops-dismiss-event] diff --git a/deploy-manage/monitor/autoops/ec-autoops-event-settings.md b/deploy-manage/monitor/autoops/ec-autoops-event-settings.md index 4ec0894109..de17a71aaa 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-event-settings.md +++ b/deploy-manage/monitor/autoops/ec-autoops-event-settings.md @@ -4,8 +4,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Event Settings [ec-autoops-event-settings] diff --git a/deploy-manage/monitor/autoops/ec-autoops-events.md b/deploy-manage/monitor/autoops/ec-autoops-events.md index 680e4dbbaa..aa89b43d5b 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-events.md +++ b/deploy-manage/monitor/autoops/ec-autoops-events.md @@ -4,8 +4,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise navigation_title: Events --- @@ -17,7 +22,7 @@ When AutoOps detects an issue, it creates an event. Events provide detailed anal ## Event insights -You can view events on the **Deployment** page in the **Open Events** and **Events History** sections. +You can view events on the **Deployment** page (for {{ECH}} deployments) or the **Cluster** page (for ECE, ECK, and self-managed clusters) in the **Open Events** and **Events History** sections. When you select an event, a flyout appears with insights and context for the detected issue. @@ -63,6 +68,6 @@ This action can be reversed using the **Dismiss events** report. You can share event information with other users by sending them a link to the event in AutoOps. Select **Share event link** to share the event. :::{note} -Users can only view the event from the shared link if they have access to the AutoOps deployment from which the link was copied. +Users can only view the event from the shared link if they have access to the AutoOps deployment or cluster from which the link was copied. ::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index 367c2ed9fa..b3c8634207 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -2,10 +2,17 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-faq.html applies_to: + serverless: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise +navigation_title: FAQ --- # AutoOps FAQ [ec-autoops-faq] @@ -15,8 +22,11 @@ Here are answers to some common questions about AutoOps. $$$faq-what-is-autoops$$$What does AutoOps do? : AutoOps for {{es}} significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, real-time issue detection and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps recommends operational and monitoring insights that deliver savings in administration time and hardware costs. -$$$faq-autoops-availability$$$Will AutoOps be available for {{serverless-full}} and self-hosted users? -: AutoOps will be available for {{serverless-full}} and self-hosted customers with a different set of capabilities in the future. +$$$faq-autoops-deployment-types$$$Is AutoOps available in all types of deployments? +: In the [regions](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, and can be [set up](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) for ECE, ECK, and self-managed clusters. + +$$$faq-autoops-regions$$$Why can't I see AutoOps in some deployments? +: AutoOps is rolling out in phases across CSPs and [regions](ec-autoops-regions.md), so you may not see it if your deployment is in a region where AutoOps is not available yet. $$$faq-autoops-monitoring$$$Does AutoOps monitor the entire {{stack}}? : AutoOps is currently limited to {{es}} (not {{kib}}, Logstash, and Beats). @@ -25,10 +35,9 @@ $$$faq-autoops-supported-versions$$$What versions of {{es}} are supported for {{ : AutoOps supports {{es}} versions according to the [supported {{stack}} versions](https://www.elastic.co/support/eol). $$$faq-autoops-license$$$How is AutoOps currently licensed? -: AutoOps' current feature set is available to {{ech}} customers at all subscription tiers. For more information, refer to the [subscription page](https://www.elastic.co/subscriptions/cloud). - -$$$faq-autoops-installation$$$How does AutoOps get installed and why may I not see AutoOps available on specific deployments? -: AutoOps is automatically applied to {{es}} clusters on {{ecloud}}, rolling out in phases across CSPs and regions. Read more about AutoOps [regions](ec-autoops-regions.md). +: Using AutoOps for {{ech}} deployments is available at all [subscription tiers](https://www.elastic.co/subscriptions/cloud). + :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md + ::: $$$faq-autoops-issue-resolution$$$Can AutoOps currently automatically resolve issues? : AutoOps only analyzes metrics, and is a read-only solution. diff --git a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md index 4fd9214024..5267446c6d 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md +++ b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md @@ -6,14 +6,14 @@ applies_to: ess: all products: - id: cloud-hosted +navigation_title: For {{ech}} --- -# How to access AutoOps [ec-autoops-how-to-access] +# AutoOps for {{ech}} -::::{note} -AutoOps supports {{es}} versions according to the [supported {{stack}} versions](https://www.elastic.co/support/eol). -:::: +For {{ech}} deployments, AutoOps is set up and enabled automatically in all supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon. +## How to access AutoOps [ec-autoops-how-to-access] To access AutoOps from your {{ecloud}} console, follow these steps: diff --git a/deploy-manage/monitor/autoops/ec-autoops-index-view.md b/deploy-manage/monitor/autoops/ec-autoops-index-view.md index 5607c64b15..124d41de3d 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-index-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-index-view.md @@ -5,8 +5,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Indices view in AutoOps [ec-autoops-index-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md index ec0a02bb24..9286318ce6 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md @@ -5,21 +5,26 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Nodes view in AutoOps [ec-autoops-nodes-view] -The **Nodes** view provides a thorough overview on the essential metrics for all monitored deployment nodes. You can delve into specific nodes to observe metrics over extended periods. This includes data on the indexing rate and latency, search rate and latency, as well as details concerning thread pools, data, circuit breakers, network, disk, and additional elements. +The **Nodes** view provides a thorough overview on the essential metrics for all monitored nodes. You can delve into specific nodes to observe metrics over extended periods. This includes data on the indexing rate and latency, search rate and latency, as well as details concerning thread pools, data, circuit breakers, network, disk, and additional elements. :::{image} /deploy-manage/images/cloud-autoops-node-view.png :alt: The Node view ::: -Similar to the **Deployment** view, the list of open events is sorted by severity and open time. +Similar to the **Deployment** or **Cluster** view, the list of open events is sorted by severity and open time. -The following table lists all the nodes used by the Deployment {{es}} cluster, presenting node name, role and status. The elected master node will be marked with a start sign. +The following table lists all the nodes used by the {{es}} cluster, presenting node name, role and status. The elected master node will be marked with a start sign. | Area | Metrics name | Metrics description | | --- | --- | --- | diff --git a/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md b/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md index dcd40043c9..2eb4ffb001 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md +++ b/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md @@ -4,8 +4,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Notifications Settings [ec-autoops-notifications-settings] diff --git a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md index 57c0188b5c..2aef418dc6 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md @@ -5,24 +5,29 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Overview in AutoOps [ec-autoops-overview-view] -The **Overview** page displays the current status of customer deployments in {{ech}} that are linked to the same Elastic organization. +The **Overview** page displays the current status of customer deployments and clusters that are linked to the same Elastic organization. :::{image} /deploy-manage/images/cloud-autoops-overview-page.png :alt: The Overview page ::: ::::{note} -The **Overview** page displays a complete list of deployments only if AutoOps is available in the specific Cloud Service Provider (CSP) region. +The **Overview** page displays a complete list of deployments and clusters only if AutoOps is available in the specific Cloud Service Provider (CSP) region. :::: -High-level metrics are available, including the most important and currently open events in a single pane. You can view the cluster status, the number of open events in each {{es}} deployments over different periods of time, and navigate to a specific deployment for more details. +High-level metrics are available, including the most important and currently open events in a single pane. You can view the cluster status, the number of open events in each {{es}} deployment or cluster over different periods of time, and navigate to a specific deployment or cluster for more details. ## Deployments table [ec-autoops-deployment-table] @@ -37,14 +42,14 @@ This section shows the number of active deployments, the number of nodes, and a ## Top events [ec-autoops-top-events] -This section provides a quick overview of the top open events in the selected period. You can filter by deployment, severity, name, and search for a specific event across all of the connected deployments. +This section provides a quick overview of the top open events in the selected period. You can filter by deployment/cluster, severity, name, and search for a specific event across all of the connected deployments or clusters. -The default view lists the top 10 important events across all deployments, sorted by severity. +The default view lists the top 10 important events, sorted by severity. -The event card indicates when the last event occurred, the number of occurrences across all deployments, the deployments impacted by the event, and it includes a direct link to the event to get additional details. +The event card indicates when the last event occurred, the number of occurrences across all deployments/clusters, the deployments/clusters impacted by the event, and it includes a direct link to the event to get additional details. ## Events in time period [ec-autoops-events-time-period] -This time series chart displays all events identified across the connected deployments during the selected period. This allows you to detect which deployment is generating the most events, investigate, and take appropriate actions to resolve any issues. +This time series chart displays all events identified across the connected deployments/clusters during the selected period. This allows you to detect which deployment/cluster is generating the most events, investigate, and take appropriate actions to resolve any issues. diff --git a/deploy-manage/monitor/autoops/ec-autoops-regions.md b/deploy-manage/monitor/autoops/ec-autoops-regions.md index d2a25df812..dcf7b3351a 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-regions.md +++ b/deploy-manage/monitor/autoops/ec-autoops-regions.md @@ -1,18 +1,26 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-regions.html +navigation_title: Regions applies_to: deployment: + self: + ece: + eck: ess: all products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # AutoOps regions [ec-autoops-regions] -A region is where a cloud service provider's data center that hosts your deployments is located. Based on a planned release schedule, Elastic is enabling AutoOps on the following cloud service providers: AWS, Azure, and GCP. +A region is where a cloud service provider's data center hosts your deployments or clusters. -AutoOps is currently available in the following regions for AWS: +## AutoOps for {{ECH}} regions + +AutoOps for {{ECH}} is currently available in the following regions for AWS: | Region | Name | | --- | --- | --- | --- | @@ -38,8 +46,18 @@ AutoOps is currently available in the following regions for AWS: | sa-east-1 | Sao Paulo | | af-south-1 | Cape Town | -Regions for Azure and GCP will be added in the future. +Regions for Azure and GCP are coming soon. + +## AutoOps for self-managed clusters regions + +You can also use AutoOps with your ECE ({{ece}}), ECK ({{eck}}), or self-managed clusters through [Cloud Connect](/deploy-manage/cloud-connect.md). + +This service is currently available in the following regions for AWS: + +:::{include} ../_snippets/autoops-cc-regions.md +::: +
::::{note} AutoOps is currently not available for GovCloud customers. :::: diff --git a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md index 6592a4d2f3..c900e3569a 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md @@ -5,8 +5,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Shards view in AutoOps [ec-autoops-shards-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md index 5771d4f4c9..3b1ca78fc5 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md +++ b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md @@ -5,8 +5,13 @@ mapped_pages: applies_to: deployment: ess: all + self: + ece: + eck: products: - id: cloud-hosted + - id: cloud-kubernetes + - id: cloud-enterprise --- # Template Optimizer view in AutoOps [ec-autoops-template-optimizer] @@ -17,5 +22,5 @@ The **Template Optimizer** view offers detailed recommendations for optimizing t :alt: The Template Optimizer view ::: -When AutoOps identifies a recommended change, it logs the template separately, allowing you to track past impactful changes. You can navigate between different deployments to view all template recommendations. +When AutoOps identifies a recommended change, it logs the template separately, allowing you to track past impactful changes. You can navigate between different deployments/clusters to view all template recommendations. diff --git a/deploy-manage/monitor/autoops/views.md b/deploy-manage/monitor/autoops/views.md index fdaad129f2..b99da65fc9 100644 --- a/deploy-manage/monitor/autoops/views.md +++ b/deploy-manage/monitor/autoops/views.md @@ -2,15 +2,18 @@ applies_to: deployment: ess: all + self: + ece: + eck: navigation_title: Views --- # AutoOps views -AutoOps offers the following views to gain further insight into difference facets of your deployment: +AutoOps offers the following views to gain further insight into difference facets of your deployment or cluster: * [Overview](/deploy-manage/monitor/autoops/ec-autoops-overview-view.md) -* [Deployment](/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md) +* [Deployment or Cluster](/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md) * [Nodes](/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md) * [Indices](/deploy-manage/monitor/autoops/ec-autoops-index-view.md) * [Shards](/deploy-manage/monitor/autoops/ec-autoops-shards-view.md) diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 14eda45617..dd51844754 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -656,12 +656,20 @@ toc: - file: remote-clusters/remote-clusters-migrate.md - file: remote-clusters/remote-clusters-settings.md - file: remote-clusters/eck-remote-clusters.md - - hidden: cloud-connect.md + - file: cloud-connect.md - file: monitor.md children: - file: monitor/autoops.md children: - file: monitor/autoops/ec-autoops-how-to-access.md + - file: monitor/autoops/cc-autoops-as-cloud-connected.md + children: + - file: monitor/autoops/cc-connect-self-managed-to-autoops.md + - file: monitor/autoops/cc-connect-local-dev-to-autoops.md + - file: monitor/autoops/cc-manage-users.md + - file: monitor/autoops/cc-cloud-connect-autoops-faq.md + - file: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md + - file: monitor/autoops/ec-autoops-regions.md - file: monitor/autoops/ec-autoops-events.md children: - file: monitor/autoops/ec-autoops-event-settings.md @@ -675,14 +683,7 @@ toc: - file: monitor/autoops/ec-autoops-shards-view.md - file: monitor/autoops/ec-autoops-template-optimizer.md - hidden: monitor/autoops/ec-autoops-dismiss-event.md - - file: monitor/autoops/ec-autoops-regions.md - file: monitor/autoops/ec-autoops-faq.md - - hidden: monitor/autoops/cc-autoops-as-cloud-connected.md - - hidden: monitor/autoops/cc-connect-self-managed-to-autoops.md - - hidden: monitor/autoops/cc-connect-local-dev-to-autoops.md - - hidden: monitor/autoops/cc-manage-users.md - - hidden: monitor/autoops/cc-cloud-connect-autoops-faq.md - - hidden: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md - file: monitor/stack-monitoring.md children: - file: monitor/stack-monitoring/ece-ech-stack-monitoring.md