diff --git a/deploy-manage/_snippets/autoops-callout-with-ech.md b/deploy-manage/_snippets/autoops-callout-with-ech.md new file mode 100644 index 0000000000..6dc74e961d --- /dev/null +++ b/deploy-manage/_snippets/autoops-callout-with-ech.md @@ -0,0 +1,5 @@ +:::{admonition} Simplify monitoring with AutoOps +Use AutoOps in your {{ech}}, ECE, ECK, or self-managed deployments. + +AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). +:::: \ No newline at end of file diff --git a/deploy-manage/cloud-connect.md b/deploy-manage/cloud-connect.md index 884bd94e80..fcd5b36faa 100644 --- a/deploy-manage/cloud-connect.md +++ b/deploy-manage/cloud-connect.md @@ -9,7 +9,7 @@ navigation_title: Cloud Connect # Cloud Connect -Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-managed cluster without having to install and maintain their infrastructure yourself. In this way, you can get faster access to new features while significantly reducing your operational overhead. +Cloud Connect enables you to use {{ecloud}} services in your ECE, ECK, or self-managed cluster without having to install and maintain their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead. AutoOps is the first service available for use with Cloud Connect. More services are coming soon. diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index e3338e4d39..54491c9896 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/deploy-manage/cloud-organization/billing/billing-faq.md @@ -98,8 +98,8 @@ $$$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. +$$$billing-cc-additional-payment$$$Does Cloud Connect require additional payment? +: Each [cloud connected service](/deploy-manage/cloud-connect.md) 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.md b/deploy-manage/deploy.md index 8359e7da1b..3a4c65da7f 100644 --- a/deploy-manage/deploy.md +++ b/deploy-manage/deploy.md @@ -38,6 +38,10 @@ To learn how to deploy optional {{stack}} components, refer to the following sec :::{include} _snippets/deployment-options-overview.md ::: +::::{tip} +Documentation will specify when certain features or configurations are not applicable to specific deployment types. +:::: + ### Who manages the infrastructure? #### Managed by Elastic @@ -58,8 +62,8 @@ If you need to run Elastic on your infrastructure, choose between a fully self-m - **{{eck}} (ECK)**: If you need Kubernetes-native orchestration - **{{ece}} (ECE)**: If you need a multi-tenant orchestration platform -::::{tip} -Documentation will specify when certain features or configurations are not applicable to specific deployment types. +:::{admonition} Use cloud services in your self-hosted environment with Cloud Connect +With [Cloud Connect](/deploy-manage/cloud-connect.md), you can use Elastic-managed cloud services in your self-managed, ECE, or ECK environment without having to install and manage their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead. :::: ### About orchestration @@ -100,5 +104,5 @@ Learn more about [versioning and availability](/get-started/versioning-availabil - **Self-hosted options**: Infrastructure costs plus operational overhead mean a higher total cost of ownership (TCO) :::::{tip} -For a detailed comparison of features and capabilities across deployment types, see the [Deployment comparison reference](./deploy/deployment-comparison.md). +For a detailed comparison of features and capabilities across deployment types, see the [](./deploy/deployment-comparison.md). ::::: diff --git a/deploy-manage/deploy/cloud-enterprise.md b/deploy-manage/deploy/cloud-enterprise.md index 59c2211dc0..47cbe23862 100644 --- a/deploy-manage/deploy/cloud-enterprise.md +++ b/deploy-manage/deploy/cloud-enterprise.md @@ -24,6 +24,10 @@ With {{ece}}, you can: Refer to [](./cloud-enterprise/ece-architecture.md) for details about the ECE platform architecture and the technologies used. +:::{admonition} Use cloud services in your ECE environment with Cloud Connect +With [Cloud Connect](/deploy-manage/cloud-connect.md), you can use Elastic-managed cloud services in your ECE environment without having to install and manage their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead. +:::: + ## ECE features - **Automated scaling & orchestration**: Handles cluster provisioning, scaling, and upgrades automatically. diff --git a/deploy-manage/deploy/cloud-on-k8s.md b/deploy-manage/deploy/cloud-on-k8s.md index 4dfb7e487b..5140e44783 100644 --- a/deploy-manage/deploy/cloud-on-k8s.md +++ b/deploy-manage/deploy/cloud-on-k8s.md @@ -16,6 +16,10 @@ products: Built on the Kubernetes Operator pattern, {{eck}} (ECK) extends the basic Kubernetes orchestration capabilities to support the setup and management of {{eck_resources_list}} on Kubernetes. +:::{admonition} Use cloud services in your ECK environment with Cloud Connect +With [Cloud Connect](/deploy-manage/cloud-connect.md), you can use Elastic-managed cloud services in your ECK environment without having to install and manage their infrastructure yourself. In this way, you can get faster access to new features without adding to your operational overhead. +:::: + ## ECK overview With {{eck}}, you can streamline critical operations, such as: @@ -35,7 +39,7 @@ This section provides everything you need to install, configure, and manage {{st Other sections of the documentation include the following important topics around ECK: -- [Logging and Monitoring](../monitor.md): Configure stack monitoring and logs forwarding with the help of ECK. +- [Logging and Monitoring](../monitor.md): Configure monitoring and logs forwarding with the help of ECK. - [Remote Clusters](../remote-clusters.md): Configure remote clusters on ECK. - [](../tools.md): Add snapshot repositories to your {{es}} clusters for automatic snapshots. - [Security](../security.md): Secure communications, manage HTTP certificates, or add secure settings to your applications. diff --git a/deploy-manage/deploy/elastic-cloud/cloud-hosted.md b/deploy-manage/deploy/elastic-cloud/cloud-hosted.md index 9669092e27..b3d9f6cd60 100644 --- a/deploy-manage/deploy/elastic-cloud/cloud-hosted.md +++ b/deploy-manage/deploy/elastic-cloud/cloud-hosted.md @@ -80,7 +80,10 @@ Refer to [](/deploy-manage/security.md) for more details. **Monitor your deployments and keep them healthy** -{{ech}} provides several ways to monitor your deployments, anticipate and prevent issues, or fix them when they occur. Check [Monitoring your deployment](/deploy-manage/monitor.md) to get more details. +{{ech}} provides several ways to monitor your deployments, anticipate and prevent issues, or fix them when they occur. Check [](/deploy-manage/monitor.md) to get more details. + +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## More about {{ech}} [ec-about] diff --git a/deploy-manage/deploy/self-managed.md b/deploy-manage/deploy/self-managed.md index 582df38e81..74d7b469c0 100644 --- a/deploy-manage/deploy/self-managed.md +++ b/deploy-manage/deploy/self-managed.md @@ -29,6 +29,12 @@ Self-hosted options: For a comparison of these deployment options, refer to [Choosing your deployment type](/deploy-manage/deploy.md#choosing-your-deployment-type) and [](/deploy-manage/deploy/deployment-comparison.md). ::: +:::{admonition} Use cloud services in your self-managed cluster with Cloud Connect +If you need to run Elastic on your own infrastructure, use [Cloud Connect](/deploy-manage/cloud-connect.md). Cloud connect enables you to use Elastic-managed cloud services in your self-managed cluster without having to install and manage their infrastructure yourself. + +This way, you can get faster access to new cloud features while still meeting your infrastructure requirements. +:::: + ## Section overview This section focuses on deploying {{es}} and {{kib}} without an orchestrator. diff --git a/deploy-manage/index.md b/deploy-manage/index.md index 162abc15ea..30b5d635c7 100644 --- a/deploy-manage/index.md +++ b/deploy-manage/index.md @@ -44,6 +44,7 @@ Learn how to design and deploy a production-ready Elastic environment. * [](/deploy-manage/reference-architectures.md): Explore blueprints for deploying clusters tailored to different use cases. * [](/deploy-manage/tools.md): Learn about the tools available to safeguard data, ensure continuous availability, and maintain resilience in your {{es}} environment. * [](/deploy-manage/autoscaling.md): Learn how to configure your [orchestrated](/deploy-manage/deploy.md#about-orchestration) deployment to scale based on policies and cluster signals. Applies to {{ech}}, {{ece}}, and {{eck}} deployments. +* [](/deploy-manage/cloud-connect.md): Learn how to use {{ecloud}} services in your self-hosted environment. :::{admonition} Serverless does it for you If you deploy an {{serverless-full}} project, then you don't need to learn about Elastic architecture, production design, resilience, or scaling concepts. Serverless automatically scales and backs up your cluster for you, and is ready for production out of the box. diff --git a/deploy-manage/monitor.md b/deploy-manage/monitor.md index de6b9226cf..b28c058a17 100644 --- a/deploy-manage/monitor.md +++ b/deploy-manage/monitor.md @@ -21,15 +21,17 @@ Depending on your deployment type, you can use a variety of solutions for monito ## Monitoring your cluster or deployment -Depending on your deployment type and context, you have several options for monitoring your cluster or deployment. +You have several options for monitoring your cluster or deployment. -If you’re using {{ech}}, you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster. +Use [AutoOps](/deploy-manage/monitor/autoops.md) in your {{ech}}, ECE, ECK, or self-managed deployments. AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. -AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection, and resolution paths. AutoOps is [rolling out](/deploy-manage/monitor/autoops/ec-autoops-regions.md) in phases across {{ech}} regions and cloud service providers. It will be automatically activated for your deployment with no installation required. +Alternatively, you can use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}. -For other deployment types, use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}. +To help you decide between these two options, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md). -To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md). +For ECE and {{ech}} deployments, there are also a number of out of the box monitoring tools available. + +The following sections provide more details. ### AutoOps (recommended) @@ -43,7 +45,7 @@ deployment: AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization. -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). +In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md), and 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/_snippets/autoops.md b/deploy-manage/monitor/_snippets/autoops.md deleted file mode 100644 index 30d701998b..0000000000 --- a/deploy-manage/monitor/_snippets/autoops.md +++ /dev/null @@ -1,5 +0,0 @@ -If you’re using {{ech}}, you can use [AutoOps](/deploy-manage/monitor/autoops.md) to monitor your cluster. - -AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection, and resolution paths. AutoOps is [rolling out](/deploy-manage/monitor/autoops/ec-autoops-regions.md) in phases across {{ech}} regions and cloud service providers. It will be automatically activated for your deployment with no installation required. - -To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md). \ No newline at end of file diff --git a/deploy-manage/monitor/autoops.md b/deploy-manage/monitor/autoops.md index 161bfdf985..c295fe0ac9 100644 --- a/deploy-manage/monitor/autoops.md +++ b/deploy-manage/monitor/autoops.md @@ -3,6 +3,7 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops.html applies_to: deployment: + serverless: ess: all self: ece: @@ -45,16 +46,20 @@ AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing r * Possibility to customize event triggers and connect to different notification services such as PagerDuty, Slack, MS Teams, and webhooks. * Long-term reports for sustained evaluation. This feature is currently not available and will be rolled out shortly. +## AutoOps availability + +In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). + +AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future. ## AutoOps retention period [ec_autoops_retention_period] -AutoOps currently has a 10 day retention period for all {{ech}} customers. +AutoOps currently has a 10 day retention period. ## AutoOps scope [ec_autoops_scope] -AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment information pertains solely to {{es}}. AutoOps supports {{es}} versions according to the [supported {{es}} versions](https://www.elastic.co/support/eol). There are plans to expand AutoOps monitoring to the entire stack. - +AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment information pertains solely to {{es}}. AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol)(7.17.x and above). We plan to expand AutoOps monitoring to the entire stack in the future. ## Section overview @@ -62,7 +67,7 @@ In this section, you'll find the following information: * 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. +* [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available. * What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md). * Which [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into your deployment. -* [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available. * [Frequently asked questions](/deploy-manage/monitor/autoops/ec-autoops-faq.md) about AutoOps. diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index 839dc19062..786407247a 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -23,7 +23,7 @@ $$$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-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. +: 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 can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). $$$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. diff --git a/deploy-manage/monitor/stack-monitoring.md b/deploy-manage/monitor/stack-monitoring.md index be4079abc6..1f21151c16 100644 --- a/deploy-manage/monitor/stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring.md @@ -17,10 +17,13 @@ products: :::{include} _snippets/stack-monitoring-def.md ::: -::::{admonition} Better monitoring with AutoOps -:::{include} _snippets/autoops.md +:::{admonition} Simplify monitoring with AutoOps +Use [AutoOps](/deploy-manage/monitor/autoops.md) in your {{ech}}, ECE, ECK, or self-managed deployments. + +AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. In the [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). + +To help you make your decision, refer to [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md). ::: -:::: ## How it works diff --git a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md index e95b492663..6738aba40c 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md @@ -32,10 +32,7 @@ Monitoring consists of two components: With logging and monitoring enabled for a deployment, metrics are collected for {{es}}, {{kib}}, and APM with Fleet Server. -:::{admonition} Simplify monitoring with AutoOps -If you’re using {{ech}}, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. - -For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: ## Before you begin [logging-and-monitoring-limitations] diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 038db80f27..034d57859f 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -451,6 +451,7 @@ toc: - file: autoscaling/autoscaling-in-eck.md - file: autoscaling/autoscaling-deciders.md - file: autoscaling/trained-model-autoscaling.md + - file: cloud-connect.md - file: security.md children: - file: security/secure-hosting-environment.md @@ -657,7 +658,6 @@ toc: - file: remote-clusters/remote-clusters-migrate.md - file: remote-clusters/remote-clusters-settings.md - file: remote-clusters/eck-remote-clusters.md - - file: cloud-connect.md - file: monitor.md children: - file: monitor/autoops.md diff --git a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md index bc09708a91..1f0162c7d7 100644 --- a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md +++ b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md @@ -19,4 +19,7 @@ The **Deployments** page in the Cloud UI provides several ways to find deploymen * Use the visual indicators to review the health of your deployments at a glance. * Search by full or partial deployment names or IDs. -* Use the **Health** and **Version** dropdown filters to narrow the list of deployments shown. These filters help you find deployments by version, configuration status, or other attributes, making it easier to identify those that require upgrades, are undergoing changes, or match specific operational criteria. \ No newline at end of file +* Use the **Health** and **Version** dropdown filters to narrow the list of deployments shown. These filters help you find deployments by version, configuration status, or other attributes, making it easier to identify those that require upgrades, are undergoing changes, or match specific operational criteria. + +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: \ No newline at end of file diff --git a/troubleshoot/deployments/cloud-enterprise/common-issues.md b/troubleshoot/deployments/cloud-enterprise/common-issues.md index dc848e8d08..e6ccb283d8 100644 --- a/troubleshoot/deployments/cloud-enterprise/common-issues.md +++ b/troubleshoot/deployments/cloud-enterprise/common-issues.md @@ -12,6 +12,8 @@ products: This set of common symptoms and resolutions can help you to diagnose unexpected behavior with Elastic Cloud Enterprise. You can also refer to the list of product [Limitations and known problems](cloud://release-notes/cloud-enterprise/known-issues.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## Emergency token not spinning up the coordinator role [ece_emergency_token_not_spinning_up_the_coordinator_role] diff --git a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md index afd664891d..f6da1a27d0 100644 --- a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md +++ b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md @@ -35,6 +35,9 @@ To run a no-op plan: If multiple health warnings appear for one of your deployments, check [](/troubleshoot/deployments/cloud-enterprise/common-issues.md) or [contact us](/troubleshoot/index.md#contact-us). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + ## Additional resources * [](/troubleshoot/monitoring/deployment-health-warnings.md) * [Troubleshooting overview](/troubleshoot/index.md) \ No newline at end of file diff --git a/troubleshoot/deployments/cloud-enterprise/node-bootlooping.md b/troubleshoot/deployments/cloud-enterprise/node-bootlooping.md index b2f468f5c6..6185634ed2 100644 --- a/troubleshoot/deployments/cloud-enterprise/node-bootlooping.md +++ b/troubleshoot/deployments/cloud-enterprise/node-bootlooping.md @@ -33,6 +33,9 @@ Here are some frequent causes of a failed configuration change: If you’re unable to remediate the failing plan’s root cause, you can attempt to reset the deployment to the latest successful {{es}} configuration by performing a [no-op plan](/troubleshoot/monitoring/deployment-health-warnings.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + ## Secure settings [ece-config-change-errors-secure-settings] The most frequent cause of a failed deployment configuration change is due to invalid or mislocated [secure settings](/deploy-manage/security/secure-settings.md). diff --git a/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md b/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md index e4391eec20..82138ac2c5 100644 --- a/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md +++ b/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md @@ -83,3 +83,5 @@ Finished creating file: /tmp/ecediag-192.168.44.10-20220506-084902.tar.gz (total At that point, you’re ready to upload the `.tar.gz` file to Elastic Support. +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index a025912bec..7359f9108f 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -11,6 +11,8 @@ products: # Troubleshoot common Elastic Cloud on Kubernetes issues [k8s-common-problems] +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## Operator crashes on startup with `OOMKilled` [k8s-common-problems-operator-oom] diff --git a/troubleshoot/deployments/cloud-on-k8s/kubernetes.md b/troubleshoot/deployments/cloud-on-k8s/kubernetes.md index f0e390f80a..ee242d4ce9 100644 --- a/troubleshoot/deployments/cloud-on-k8s/kubernetes.md +++ b/troubleshoot/deployments/cloud-on-k8s/kubernetes.md @@ -11,10 +11,12 @@ products: # Troubleshoot Elastic Cloud on Kubernetes [k8s-troubleshooting] +This section provides information on the following topics: -* [*Common problems*](common-problems.md) -* [*Troubleshooting methods*](troubleshooting-methods.md) -* [*Run eck-diagnostics*](run-eck-diagnostics.md) +* [Common issues](common-problems.md) +* [Troubleshooting resources and logs](troubleshooting-methods.md) +* [Running diagnostics](run-eck-diagnostics.md) +* [JVM heap dumps](jvm-heap-dumps.md) If you are an existing Elastic customer with an active support contract, you can create a case in the [Elastic Support Portal](https://support.elastic.co/). Kindly attach an [ECK diagnostic](run-eck-diagnostics.md) when opening your case. @@ -23,3 +25,5 @@ Alternatively, or if you do not have a support contract, and if you are unable t * [ECK Discuss forums](https://discuss.elastic.co/c/eck) to ask any question * [Github issues](https://github.com/elastic/cloud-on-k8s/issues) for bugs and feature requests +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: \ No newline at end of file diff --git a/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md b/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md index c8afaa6f74..074c055227 100644 --- a/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md +++ b/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md @@ -11,6 +11,9 @@ products: # Run eck-diagnostics [k8s-take-eck-dump] +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + `eck-diagnostics` is a stand-alone command line tool to create a diagnostic archive to help troubleshoot issues with ECK. diff --git a/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md b/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md index e7bd5f2cc7..2e670e17a1 100644 --- a/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md +++ b/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md @@ -34,6 +34,8 @@ Alternatively, or if you do not have a support contract, and if you are unable t * [ECK Discuss forums](https://discuss.elastic.co/c/eck) to ask any question * [Github issues](https://github.com/elastic/cloud-on-k8s/issues) for bugs and feature requests +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## View the list of resources [k8s-get-resources] diff --git a/troubleshoot/deployments/elastic-cloud.md b/troubleshoot/deployments/elastic-cloud.md index 62ee32a9e7..bf91030fa6 100644 --- a/troubleshoot/deployments/elastic-cloud.md +++ b/troubleshoot/deployments/elastic-cloud.md @@ -25,4 +25,7 @@ Use the topics in this section to troubleshoot {{ecloud}}: * [](/troubleshoot/monitoring/cluster-response-time.md) * [](/troubleshoot/monitoring/node-moves-outages.md) * [](/troubleshoot/monitoring/deployment-health-warnings.md) -* [](/troubleshoot/monitoring/node-bootlooping.md) \ No newline at end of file +* [](/troubleshoot/monitoring/node-bootlooping.md) + +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: \ No newline at end of file diff --git a/troubleshoot/elasticsearch.md b/troubleshoot/elasticsearch.md index b6a35e3797..cbed0874c7 100644 --- a/troubleshoot/elasticsearch.md +++ b/troubleshoot/elasticsearch.md @@ -10,9 +10,8 @@ products: This section helps you fix issues with {{es}} deployments. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## General [troubleshooting-general] diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 61b251c0d6..6c170e614b 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -20,9 +20,8 @@ By default, the [parent circuit breaker](elasticsearch://reference/elasticsearch See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough of diagnosing circuit breaker errors. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/cluster-allocation-api-examples.md b/troubleshoot/elasticsearch/cluster-allocation-api-examples.md index f0e8e3091d..0848a6643d 100644 --- a/troubleshoot/elasticsearch/cluster-allocation-api-examples.md +++ b/troubleshoot/elasticsearch/cluster-allocation-api-examples.md @@ -4,6 +4,9 @@ navigation_title: Cluster allocation API examples # Using the cluster allocation API for troubleshooting +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + Troubleshooting shard allocation issues in an {{es}} cluster can be complex, especially when dealing with unassigned shards or rebalancing issues. The [cluster allocation explain API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-allocation-explain) helps diagnose these problems by providing detailed, node-by-node explanations of allocation decisions. This page walks you through common scenarios to show how the API can guide you in resolving allocation issues efficiently. diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md index 82777f8d27..82e42a5a87 100644 --- a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md +++ b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md @@ -17,6 +17,9 @@ products: # Diagnose unassigned shards [diagnose-unassigned-shards] +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + There are multiple reasons why shards might get unassigned, ranging from misconfigured allocation settings to lack of disk space. In order to diagnose the unassigned shards in your deployment use the following steps: @@ -240,11 +243,7 @@ For more guidance on fixing the most common causes for unassinged shards follow :::::: ::::::: -See [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health. - -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +Watch [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health. ## Common issues diff --git a/troubleshoot/elasticsearch/diagnostic.md b/troubleshoot/elasticsearch/diagnostic.md index fed12da445..546ac260ed 100644 --- a/troubleshoot/elasticsearch/diagnostic.md +++ b/troubleshoot/elasticsearch/diagnostic.md @@ -22,11 +22,10 @@ This information can be used to troubleshoot problems with your cluster. For exa You can generate diagnostic information using this tool before you contact [Elastic Support](https://support.elastic.co) or [Elastic Discuss](https://discuss.elastic.co) to minimize turnaround time. -See this [this video](https://www.youtube.com/watch?v=Bb6SaqhqYHw) for a walkthrough of capturing an {{es}} diagnostic. +Watch [this video](https://www.youtube.com/watch?v=Bb6SaqhqYHw) for a walkthrough of capturing an {{es}} diagnostic. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/fix-common-cluster-issues.md b/troubleshoot/elasticsearch/fix-common-cluster-issues.md index b5b65d9574..7878400bce 100644 --- a/troubleshoot/elasticsearch/fix-common-cluster-issues.md +++ b/troubleshoot/elasticsearch/fix-common-cluster-issues.md @@ -17,10 +17,8 @@ products: Use these topics to fix common issues with {{es}} clusters. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: - +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: [](fix-watermark-errors.md) : Fix watermark errors that occur when a data node is critically low on disk space and has reached the flood-stage disk usage watermark. diff --git a/troubleshoot/elasticsearch/fix-watermark-errors.md b/troubleshoot/elasticsearch/fix-watermark-errors.md index ef7873a5b3..380d55e26b 100644 --- a/troubleshoot/elasticsearch/fix-watermark-errors.md +++ b/troubleshoot/elasticsearch/fix-watermark-errors.md @@ -24,9 +24,8 @@ To prevent a full disk, when a node reaches this watermark, {{es}} [blocks write {{es}} will automatically remove the write block when the affected node’s disk usage falls below the [high disk watermark](elasticsearch://reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings.md#cluster-routing-watermark-high). To achieve this, {{es}} attempts to rebalance some of the affected node’s shards to other nodes in the same data tier. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## Monitor rebalancing [fix-watermark-errors-rebalance] diff --git a/troubleshoot/elasticsearch/high-cpu-usage.md b/troubleshoot/elasticsearch/high-cpu-usage.md index 95593c7803..e239dc1bde 100644 --- a/troubleshoot/elasticsearch/high-cpu-usage.md +++ b/troubleshoot/elasticsearch/high-cpu-usage.md @@ -19,9 +19,8 @@ products: If a thread pool is depleted, {{es}} will [reject requests](rejected-requests.md) related to the thread pool. For example, if the `search` thread pool is depleted, {{es}} will reject search requests until more threads are available. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md index c25ca86336..2be03c59c4 100644 --- a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md +++ b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md @@ -16,9 +16,8 @@ products: High JVM memory usage can degrade cluster performance and trigger [circuit breaker errors](circuit-breaker-errors.md). To prevent this, we recommend taking steps to reduce memory pressure if a node’s JVM memory usage consistently exceeds 85%. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/hotspotting.md b/troubleshoot/elasticsearch/hotspotting.md index 92cc927414..46a73e954f 100644 --- a/troubleshoot/elasticsearch/hotspotting.md +++ b/troubleshoot/elasticsearch/hotspotting.md @@ -20,12 +20,10 @@ products: Computer [hot spotting](https://en.wikipedia.org/wiki/Hot_spot_(computer_programming)) may occur in {{es}} when resource utilizations are unevenly distributed across [nodes](elasticsearch://reference/elasticsearch/configuration-reference/node-settings.md). Temporary spikes are not usually considered problematic, but ongoing significantly unique utilization may lead to cluster bottlenecks and should be reviewed. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +Watch [this video](https://www.youtube.com/watch?v=Q5ODJ5nIKAM) for a walkthrough of troubleshooting a hot spotting issue. - -See [this video](https://www.youtube.com/watch?v=Q5ODJ5nIKAM) for a walkthrough of troubleshooting a hot spotting issue. +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: ## Detect hot spotting [detect] diff --git a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md index c9d836460a..2bad9edb46 100644 --- a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md +++ b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md @@ -17,11 +17,11 @@ products: # Total number of shards per node has been reached [increase-cluster-shard-limit] -Elasticsearch tries to take advantage of all the available resources by distributing data (index shards) amongst the cluster nodes. +{{es}} takes advantage of all available resources by distributing data (index shards) among the cluster nodes. -Users might want to influence this data distribution by configuring the [`cluster.routing.allocation.total_shards_per_node`](elasticsearch://reference/elasticsearch/index-settings/total-shards-per-node.md#cluster-total-shards-per-node) system setting to restrict the number of shards that can be hosted on a single node in the system, regardless of the index. Various configurations limiting how many shards can be hosted on a single node can lead to shards being unassigned due to the cluster not having enough nodes to satisfy the configuration. +You might want to influence this data distribution by configuring the [`cluster.routing.allocation.total_shards_per_node`](elasticsearch://reference/elasticsearch/index-settings/total-shards-per-node.md#cluster-total-shards-per-node) system setting to restrict the number of shards that can be hosted on a single node in the system, regardless of the index. Various configurations limiting how many shards can be hosted on a single node can lead to shards being unassigned, because the cluster does not have enough nodes to satisfy the configuration. -In order to fix this follow the next steps: +To fix this issue, complete the following steps: :::::::{tab-set} @@ -137,6 +137,5 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec :::::: ::::::: -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md index 9a5357cf96..99f9c27b23 100644 --- a/troubleshoot/elasticsearch/increase-shard-limit.md +++ b/troubleshoot/elasticsearch/increase-shard-limit.md @@ -17,11 +17,11 @@ products: # Total number of shards for an index on a single node exceeded [increase-shard-limit] -Elasticsearch tries to take advantage of all the available resources by distributing data (index shards) among nodes in the cluster. +{{es}} takes advantage of all available resources by distributing data (index shards) among the cluster nodes. -Users might want to influence this data distribution by configuring the [index.routing.allocation.total_shards_per_node](elasticsearch://reference/elasticsearch/index-settings/total-shards-per-node.md#total-shards-per-node) index setting to a custom value (for e.g. `1` in case of a highly trafficked index). Various configurations limiting how many shards an index can have located on one node can lead to shards being unassigned due to the cluster not having enough nodes to satisfy the index configuration. +You might want to influence this data distribution by configuring the [index.routing.allocation.total_shards_per_node](elasticsearch://reference/elasticsearch/index-settings/total-shards-per-node.md#total-shards-per-node) index setting to a custom value (for example, `1` in case of a highly trafficked index). Various configurations limiting how many shards an index can have located on one node can lead to shards being unassigned, because the cluster does not have enough nodes to satisfy the index configuration. -In order to fix this follow the next steps: +To fix this issue, complete the following steps: :::::::{tab-set} @@ -136,6 +136,6 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec ``` :::::: -:::{tip}} -If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). -::: +::::::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: \ No newline at end of file diff --git a/troubleshoot/elasticsearch/increase-tier-capacity.md b/troubleshoot/elasticsearch/increase-tier-capacity.md index 711989b15f..3c1c9d1696 100644 --- a/troubleshoot/elasticsearch/increase-tier-capacity.md +++ b/troubleshoot/elasticsearch/increase-tier-capacity.md @@ -15,11 +15,11 @@ products: # Warning: Not enough nodes to allocate all shard replicas [increase-tier-capacity] -Distributing copies of the data (index shard replicas) on different nodes can parallelize processing requests thus speeding up search queries. This can be achieved by increasing the number of replica shards up to the maximum value (total number of nodes minus one) which also serves the purpose to protect against hardware failure. If the index has a preferred tier, Elasticsearch will only place the copies of the data for that index on nodes in the target tier. +Distributing copies of the data (index shard replicas) on different nodes can parallelize processing requests, speeding up search queries. To achieve this, increase the number of replica shards up to the maximum value (total number of nodes minus one), which also protects against hardware failure. If the index has a preferred tier, {{es}} will only place the copies of the data for that index on nodes in the target tier. -If a warning is encountered with not enough nodes to allocate all shard replicas, you can influence this behavior by adding more nodes to the cluster (or tier if tiers are in use), or by reducing the [`index.number_of_replicas`](elasticsearch://reference/elasticsearch/index-settings/index-modules.md#dynamic-index-number-of-replicas) index setting. +If a warning is encountered with not enough nodes to allocate all shard replicas, you can influence this behavior by adding more nodes to the cluster (or tier), or by reducing the [`index.number_of_replicas`](elasticsearch://reference/elasticsearch/index-settings/index-modules.md#dynamic-index-number-of-replicas) index setting. -In order to fix this follow the next steps: +To accomplish this, complete the following steps: :::::::{tab-set} @@ -214,6 +214,6 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec :::::: ::::::: -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: + +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/monitoring-troubleshooting.md b/troubleshoot/elasticsearch/monitoring-troubleshooting.md index 088b6ada35..29976710d3 100644 --- a/troubleshoot/elasticsearch/monitoring-troubleshooting.md +++ b/troubleshoot/elasticsearch/monitoring-troubleshooting.md @@ -21,6 +21,9 @@ Use the information in this section to troubleshoot common problems and find ans If you can't find your issue here, explore the other [troubleshooting topics](/troubleshoot/index.md) or [contact us](/troubleshoot/index.md#contact-us). ::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + ## No monitoring data is visible in {{kib}} [monitoring-troubleshooting-no-data] **Symptoms**: There is no information about your cluster on the **Stack Monitoring** page in {{kib}}. diff --git a/troubleshoot/elasticsearch/red-yellow-cluster-status.md b/troubleshoot/elasticsearch/red-yellow-cluster-status.md index 3749b48d37..7ddef6495b 100644 --- a/troubleshoot/elasticsearch/red-yellow-cluster-status.md +++ b/troubleshoot/elasticsearch/red-yellow-cluster-status.md @@ -24,9 +24,8 @@ When your cluster has a red or yellow health status, it will continue to process In many cases, your cluster will recover to green health status automatically. If the cluster doesn’t automatically recover, then you must [manually address](#fix-red-yellow-cluster-status) the remaining problems so management and cleanup activities can proceed. See [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/rejected-requests.md b/troubleshoot/elasticsearch/rejected-requests.md index 9b3f8ff828..bd46bca07b 100644 --- a/troubleshoot/elasticsearch/rejected-requests.md +++ b/troubleshoot/elasticsearch/rejected-requests.md @@ -20,10 +20,8 @@ When {{es}} rejects a request, it stops the operation and returns an error with * A [circuit breaker error](circuit-breaker-errors.md). * High [indexing pressure](elasticsearch://reference/elasticsearch/index-settings/pressure.md) that exceeds the [`indexing_pressure.memory.limit`](elasticsearch://reference/elasticsearch/index-settings/pressure.md#memory-limits). -::::{tip} -If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). - -:::: +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md index 457827a96d..7033bb23d7 100644 --- a/troubleshoot/elasticsearch/repeated-snapshot-failures.md +++ b/troubleshoot/elasticsearch/repeated-snapshot-failures.md @@ -175,6 +175,6 @@ In the event that snapshots are failing for other reasons check the logs on the :::::: ::::::: -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: + +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md index 927294deac..89208fac80 100644 --- a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md +++ b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md @@ -15,6 +15,9 @@ products: # Troubleshoot shard capacity health issues [troubleshooting-shards-capacity-issues] +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + {{es}} limits the maximum number of shards to be held per node using the [`cluster.max_shards_per_node`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node) and [`cluster.max_shards_per_node.frozen`](elasticsearch://reference/elasticsearch/configuration-reference/miscellaneous-cluster-settings.md#cluster-max-shards-per-node-frozen) settings. The current shards capacity of the cluster is available in the [health API shards capacity section](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-health-report). @@ -434,6 +437,3 @@ PUT _cluster/settings :::::: ::::::: -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: diff --git a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md index bbb2da2f01..1dfeefbed3 100644 --- a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md +++ b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md @@ -17,17 +17,15 @@ products: # Troubleshoot an unbalanced cluster [troubleshooting-unbalanced-cluster] +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + Elasticsearch balances shards across data tiers to achieve a good compromise between: * shard count * disk usage * write load (for indices in data streams) -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: - - Elasticsearch does not take into account the amount or complexity of search queries when rebalancing shards. This is indirectly achieved by balancing shard count and disk usage. There is no guarantee that individual components will be evenly spread across the nodes. This could happen if some nodes have fewer shards, or are using less disk space, but are assigned shards with higher write loads. diff --git a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md index 9d2fa42fdf..4c0ee4f87c 100644 --- a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md +++ b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md @@ -23,10 +23,8 @@ Normally, a node will only leave a cluster if deliberately shut down. If a node * The `.security` index may be unavailable, blocking access to the cluster. * The master may appear busy due to frequent cluster state updates. -::::{tip} -If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md). -:::: - +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: To troubleshoot a cluster in this state, first ensure the cluster has a [stable master](discovery-troubleshooting.md). Next, focus on the nodes unexpectedly leaving the cluster ahead of all other issues. It will not be possible to solve other issues until the cluster has a stable master node and stable node membership. diff --git a/troubleshoot/monitoring/cluster-response-time.md b/troubleshoot/monitoring/cluster-response-time.md index b7cf32c134..8ba0368200 100644 --- a/troubleshoot/monitoring/cluster-response-time.md +++ b/troubleshoot/monitoring/cluster-response-time.md @@ -26,6 +26,5 @@ So what caused the sudden increase in response times? The key to the puzzle lies This cluster was sized to handle a certain number of user requests. As the user requests exceeded the maximum throughput that a cluster of this size could sustain, response times increased. To avoid such a slowdown, you either need to control the volume of user requests that reaches the {{es}} cluster or you need to size your cluster to be able to accommodate a sudden increase in user requests. -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: \ No newline at end of file diff --git a/troubleshoot/monitoring/deployment-health-warnings.md b/troubleshoot/monitoring/deployment-health-warnings.md index 92ee2e38b9..65a6ff5ee9 100644 --- a/troubleshoot/monitoring/deployment-health-warnings.md +++ b/troubleshoot/monitoring/deployment-health-warnings.md @@ -32,8 +32,7 @@ If multiple health warnings appear for one of your deployments, or if your deplo If the warning refers to a system change, check the deployment’s [Activity](/deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) page. -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: ## Additional resources diff --git a/troubleshoot/monitoring/high-availability.md b/troubleshoot/monitoring/high-availability.md index e302000a4b..70b43aa001 100644 --- a/troubleshoot/monitoring/high-availability.md +++ b/troubleshoot/monitoring/high-availability.md @@ -28,6 +28,5 @@ This CPU usage graph indicates that your cluster is load-balancing between the n Even if your cluster is performing well, you still need to make sure that there is sufficient spare capacity to deal with the outage of an entire availability zone. For this cluster to remain highly available at all times, you either need to increase its size or reduce its workload. -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: \ No newline at end of file diff --git a/troubleshoot/monitoring/high-memory-pressure.md b/troubleshoot/monitoring/high-memory-pressure.md index 611d8c90da..5c5dd85259 100644 --- a/troubleshoot/monitoring/high-memory-pressure.md +++ b/troubleshoot/monitoring/high-memory-pressure.md @@ -34,8 +34,7 @@ In our example, the **Index Response Times** metric shows that high memory press If the performance impact from high memory pressure is not acceptable, you need to increase the cluster size or reduce the workload. -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: ## Increase the deployment size [ec_increase_the_deployment_size] diff --git a/troubleshoot/monitoring/node-bootlooping.md b/troubleshoot/monitoring/node-bootlooping.md index a6a4dceac0..e5552b2ccf 100644 --- a/troubleshoot/monitoring/node-bootlooping.md +++ b/troubleshoot/monitoring/node-bootlooping.md @@ -40,10 +40,9 @@ Following are some frequent causes of a failed configuration change: 4. [Existing index](/troubleshoot/monitoring/node-bootlooping.md#ec-config-change-errors-existing-index) 5. [Insufficient Storage](/troubleshoot/monitoring/node-bootlooping.md#ec-config-change-errors-insufficient-storage) -If you’re unable to remediate the failing plan’s root cause, you can attempt to reset the deployment to the latest successful {{es}} configuration by performing a [no-op plan](/troubleshoot/monitoring/deployment-health-warnings.md). For an example, see this [video walkthrough](https://www.youtube.com/watch?v=8MnXZ9egBbQ). +If you’re unable to remediate the failing plan’s root cause, you can attempt to reset the deployment to the latest successful {{es}} configuration by performing a [no-op plan](/troubleshoot/monitoring/deployment-health-warnings.md). For an example, watch this [video walkthrough](https://www.youtube.com/watch?v=8MnXZ9egBbQ). -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: ## Secure settings [ec-config-change-errors-secure-settings] diff --git a/troubleshoot/monitoring/performance.md b/troubleshoot/monitoring/performance.md index 82fc6e8470..19fa0de018 100644 --- a/troubleshoot/monitoring/performance.md +++ b/troubleshoot/monitoring/performance.md @@ -24,6 +24,5 @@ Between just after 00:10 and 00:20, excessively high CPU usage consumes all CPU If you need your cluster to be able to sustain a certain level of performance, you cannot rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster. -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md ::: diff --git a/troubleshoot/monitoring/unavailable-nodes.md b/troubleshoot/monitoring/unavailable-nodes.md index 47ca48770b..968819e5f0 100644 --- a/troubleshoot/monitoring/unavailable-nodes.md +++ b/troubleshoot/monitoring/unavailable-nodes.md @@ -41,12 +41,11 @@ Some actions described here, such as stopping indexing or Machine Learning jobs, For production deployments, we recommend setting up a dedicated monitoring cluster to collect metrics and logs, troubleshooting views, and cluster alerts. -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). -::: - If your issue is not addressed here, then [contact Elastic support for help](/troubleshoot/index.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + ## Full disk on single-node deployment [ec-single-node-deployment-disk-used] **Health check** diff --git a/troubleshoot/monitoring/unavailable-shards.md b/troubleshoot/monitoring/unavailable-shards.md index 074fadaa13..5302c101c1 100644 --- a/troubleshoot/monitoring/unavailable-shards.md +++ b/troubleshoot/monitoring/unavailable-shards.md @@ -37,12 +37,11 @@ If a cluster has unassigned shards, you might see an error message such as this :alt: Unhealthy deployment error message ::: -:::{important} - If you’re using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [Monitor with AutoOps](/deploy-manage/monitor/autoops.md). -::: - If your issue is not addressed here, then [contact Elastic support for help](/troubleshoot/index.md). +:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md +::: + ## Analyze unassigned shards using the {{es}} API [ec-analyze_shards_with-api] You can retrieve information about the status of your cluster, indices, and shards using the {{es}} API. To access the API you can either use the [Kibana Dev Tools Console](/explore-analyze/query-filter/tools/console.md), or the [Elasticsearch API console](cloud://reference/cloud-hosted/ec-api-console.md). If you have your own way to run the {{es}} API, check [How to access the API](cloud://reference/cloud-hosted/ec-api-access.md). This section shows you how to: