diff --git a/troubleshoot/deployments.md b/troubleshoot/deployments.md deleted file mode 100644 index baaa2d849c..0000000000 --- a/troubleshoot/deployments.md +++ /dev/null @@ -1,3 +0,0 @@ -# Deployments - -% What needs to be done: Write from scratch \ No newline at end of file diff --git a/troubleshoot/deployments/cloud-enterprise/ask-for-help.md b/troubleshoot/deployments/cloud-enterprise/ask-for-help.md index 60d856bd5d..f87855aeb5 100644 --- a/troubleshoot/deployments/cloud-enterprise/ask-for-help.md +++ b/troubleshoot/deployments/cloud-enterprise/ask-for-help.md @@ -5,6 +5,12 @@ mapped_pages: # Ask for help [ece-getting-help] +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on moving this content to the [Troubleshooting overview](/troubleshoot/index.md). +::: + For issues with Elastic Cloud Enterprise that you cannot fix yourself …​ we’re here to help! If you are an existing Elastic customer with a support contract, please create a ticket in the [Elastic Support Portal](https://support.elastic.co) and provide an ECE [diagnostics package and log files](../../../deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md). By providing a diagnostics package, you make it easier for us to help you. diff --git a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md index 31c532bd6c..c3fa60cd8a 100644 --- a/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md +++ b/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md @@ -1,10 +1,17 @@ --- +navigation_title: "Elastic Cloud Enterprise" mapped_urls: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting.html - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-find.html --- -# Elastic Cloud Enterprise +# Troubleshoot Elastic Cloud Enterprise + +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure. +::: ## Finding deployments [ts-ece-find] diff --git a/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md b/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md index 49c25c461a..8a2e698556 100644 --- a/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md +++ b/troubleshoot/deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md @@ -1,4 +1,5 @@ --- +navigation_title: "Zookeeper quorum" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-zookeeper-quorum.html --- diff --git a/troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md b/troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md index 96576ca40c..ca3c12a37f 100644 --- a/troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md +++ b/troubleshoot/deployments/cloud-enterprise/remove-cloud-enterprise.md @@ -1,9 +1,10 @@ --- +navigation_title: "Removing containers" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-uninstall.html --- -# Remove Elastic Cloud Enterprise [ece-uninstall] +# Remove Elastic Cloud Enterprise containers [ece-uninstall] You might need to remove Elastic Cloud Enterprise for one of the following reasons: @@ -14,23 +15,18 @@ You remove Elastic Cloud Enterprise by removing all containers on the host: * If using Docker -::::{admonition} + ```sh docker rm -f frc-runners-runner frc-allocators-allocator $(docker ps -a -q); sudo rm -rf /mnt/data/elastic/ && docker ps -a ``` -:::: - * If using Podman -::::{admonition} ```sh sudo podman rm -f frc-runners-runner frc-allocators-allocator $(sudo podman ps -a -q); sudo rm -rf /mnt/data/elastic && sudo podman ps -a ``` -:::: - If you plan to reinstall Elastic Cloud Enterprise on the host, make sure you [delete the host](../../../deploy-manage/maintenance/ece/delete-ece-hosts.md) from the Cloud UI first. Reinstallation can fail if the host is still associated with your old Elastic Cloud Enterprise installation. diff --git a/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md b/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md index 76056da7bc..46c1625d44 100644 --- a/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md +++ b/troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md @@ -1,4 +1,5 @@ --- +navigation_title: "Diagnostics" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-run-ece-diagnostics.html --- diff --git a/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md b/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md index ca28e92c35..ba1b83ddb0 100644 --- a/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md +++ b/troubleshoot/deployments/cloud-enterprise/troubleshooting-container-engines.md @@ -1,9 +1,10 @@ --- +navigation_title: "Container engines" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-containers.html --- -# Troubleshooting container engines [ece-troubleshooting-containers] +# Troubleshoot container engines [ece-troubleshooting-containers] This article describes how to troubleshoot container engine services in Elastic Cloud Enterprise. We refer to [Docker](https://www.docker.com/) by default, as it’s the most common container engine, but these steps are also valid for [Podman](https://podman.io/). You can simply replace `docker` in the commands with `podman` as needed. diff --git a/troubleshoot/deployments/cloud-enterprise/use-emergency-roles-token.md b/troubleshoot/deployments/cloud-enterprise/use-emergency-roles-token.md index b8a9d66da9..4e3b73c4f7 100644 --- a/troubleshoot/deployments/cloud-enterprise/use-emergency-roles-token.md +++ b/troubleshoot/deployments/cloud-enterprise/use-emergency-roles-token.md @@ -1,4 +1,5 @@ --- +navigation_title: "Emergency roles token" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-emergency.html --- diff --git a/troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md b/troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md index 512215e3ac..bb10b642c3 100644 --- a/troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md +++ b/troubleshoot/deployments/cloud-enterprise/verify-zookeeper-sync-status.md @@ -1,9 +1,10 @@ --- +navigation_title: "ZooKeeper sync status" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-zookeeper-sync.html --- -# Verify ZooKeeper Sync Status [ece-zookeeper-sync] +# Verify ZooKeeper sync status [ece-zookeeper-sync] It is recommended to check the ZooKeeper sync status before starting any maintenance on your Director nodes. This helps you prevent the following scenarios: diff --git a/troubleshoot/deployments/cloud-on-k8s/common-problems.md b/troubleshoot/deployments/cloud-on-k8s/common-problems.md index 660edc1bd9..df9fd6bd07 100644 --- a/troubleshoot/deployments/cloud-on-k8s/common-problems.md +++ b/troubleshoot/deployments/cloud-on-k8s/common-problems.md @@ -1,9 +1,12 @@ --- +navigation_title: "Common issues" +applies: + eck: all mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-common-problems.html --- -# Common problems [k8s-common-problems] +# Troubleshoot common Elastic Cloud on Kubernetes issues [k8s-common-problems] ## Operator crashes on startup with `OOMKilled` [k8s-common-problems-operator-oom] diff --git a/troubleshoot/deployments/cloud-on-k8s/jvm-heap-dumps.md b/troubleshoot/deployments/cloud-on-k8s/jvm-heap-dumps.md index 35afff0757..a6702ebba7 100644 --- a/troubleshoot/deployments/cloud-on-k8s/jvm-heap-dumps.md +++ b/troubleshoot/deployments/cloud-on-k8s/jvm-heap-dumps.md @@ -1,9 +1,12 @@ --- +navigation_title: "JVM heap dumps" +applies: + eck: all mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-jvm-heap-dumps.html --- -# JVM heap dumps [k8s-jvm-heap-dumps] +# Troubleshoot JVM heap dumps [k8s-jvm-heap-dumps] ## Ensure sufficient storage [k8s_ensure_sufficient_storage] diff --git a/troubleshoot/deployments/cloud-on-k8s/kubernetes.md b/troubleshoot/deployments/cloud-on-k8s/kubernetes.md index 748f120581..ba90fc7883 100644 --- a/troubleshoot/deployments/cloud-on-k8s/kubernetes.md +++ b/troubleshoot/deployments/cloud-on-k8s/kubernetes.md @@ -8,6 +8,12 @@ mapped_pages: # Troubleshoot Elastic Cloud on Kubernetes [k8s-troubleshooting] +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure. +::: + * [*Common problems*](common-problems.md) * [*Troubleshooting methods*](troubleshooting-methods.md) * [*Run eck-diagnostics*](run-eck-diagnostics.md) diff --git a/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md b/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md index a73665cabf..d75d10ed58 100644 --- a/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md +++ b/troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md @@ -1,4 +1,5 @@ --- +navigation_title: "Diagnostics" mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-take-eck-dump.html --- diff --git a/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md b/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md index 44a972a3c1..b107875150 100644 --- a/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md +++ b/troubleshoot/deployments/cloud-on-k8s/troubleshooting-methods.md @@ -1,9 +1,12 @@ --- +navigation_title: "Resources and logs" +applies: + eck: all mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-troubleshooting-methods.html --- -# Troubleshooting methods [k8s-troubleshooting-methods] +# Troubleshoot ECK resources and logs [k8s-troubleshooting-methods] Most common issues can be identified and resolved by following these instructions: diff --git a/troubleshoot/deployments/elastic-cloud.md b/troubleshoot/deployments/elastic-cloud.md index 5d6af2aa87..10784093cd 100644 --- a/troubleshoot/deployments/elastic-cloud.md +++ b/troubleshoot/deployments/elastic-cloud.md @@ -1,3 +1,27 @@ -# Elastic Cloud +--- +navigation_title: "Elastic Cloud" +mapped_pages: + - https://www.elastic.co/guide/en/kibana/current/kibana-troubleshooting.html + - https://www.elastic.co/guide/en/cloud/current/ec-monitoring-diagnose-resolve.html +--- -% What needs to be done: Write from scratch \ No newline at end of file +# Troubleshoot {{ecloud}} + +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on restructuring this section. It currently reflects a legacy product-centric structure. +::: + +Use the topics in this section to troubleshoot {{ecloud}}: + +* [](/troubleshoot/deployments/elastic-cloud/sso.md) +* [](/troubleshoot/monitoring/unavailable-nodes.md) +* [](/troubleshoot/monitoring/unavailable-shards.md) +* [](/troubleshoot/monitoring/performance.md) +* [](/troubleshoot/monitoring/high-memory-pressure.md) +* [](/troubleshoot/monitoring/high-availability.md) +* [](/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 diff --git a/troubleshoot/deployments/elastic-cloud/monitoring.md b/troubleshoot/deployments/elastic-cloud/monitoring.md deleted file mode 100644 index 9e7608412e..0000000000 --- a/troubleshoot/deployments/elastic-cloud/monitoring.md +++ /dev/null @@ -1,6 +0,0 @@ -# Monitoring - -% What needs to be done: Write from scratch - -% Scope notes: xrefs to Monitoring section and other sections? -% or just remove this section until later? \ No newline at end of file diff --git a/troubleshoot/deployments/serverless.md b/troubleshoot/deployments/serverless.md index 4406ff2c6b..83c84dc45c 100644 --- a/troubleshoot/deployments/serverless.md +++ b/troubleshoot/deployments/serverless.md @@ -12,3 +12,4 @@ Use the topics in this section to troubleshoot {{serverless-full}}: ## Additional resources +[Troubleshooting overview](/troubleshoot/index.md) \ No newline at end of file diff --git a/troubleshoot/elasticsearch/capacity.md b/troubleshoot/elasticsearch/capacity.md index a0495ffad4..15e320b1b2 100644 --- a/troubleshoot/elasticsearch/capacity.md +++ b/troubleshoot/elasticsearch/capacity.md @@ -4,4 +4,10 @@ navigation_title: Capacity # Troubleshoot Elasticsearch capacity issues +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on this section. Contributions welcome! +::: + % What needs to be done: Write from scratch \ No newline at end of file diff --git a/troubleshoot/elasticsearch/circuit-breaker-errors.md b/troubleshoot/elasticsearch/circuit-breaker-errors.md index 41dcd7d3fd..e177e89d0a 100644 --- a/troubleshoot/elasticsearch/circuit-breaker-errors.md +++ b/troubleshoot/elasticsearch/circuit-breaker-errors.md @@ -11,7 +11,7 @@ By default, the [parent circuit breaker](https://www.elastic.co/guide/en/elastic See [this video](https://www.youtube.com/watch?v=k3wYlRVbMSw) for a walkthrough of diagnosing circuit breaker errors. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/clients.md b/troubleshoot/elasticsearch/clients.md index 9181201c37..a85f2ba99f 100644 --- a/troubleshoot/elasticsearch/clients.md +++ b/troubleshoot/elasticsearch/clients.md @@ -1,3 +1,13 @@ -# Clients +--- +navigation_title: "Clients" +--- + +# Troubleshoot {{es}} clients + +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on this section. Contributions welcome! +::: % What needs to be done: Write from scratch \ No newline at end of file diff --git a/troubleshoot/elasticsearch/clusters.md b/troubleshoot/elasticsearch/clusters.md index 8cf162b7f4..e3c4a9ab2b 100644 --- a/troubleshoot/elasticsearch/clusters.md +++ b/troubleshoot/elasticsearch/clusters.md @@ -4,4 +4,19 @@ navigation_title: Clusters # Troubleshoot Elasticsearch clusters -% What needs to be done: Write from scratch +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on this section. Contributions welcome! +::: + +Use the topics in this section to troubleshoot {{es}} clusters: + +* [](/troubleshoot/elasticsearch/clusters.md) +* [](/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md) +* [](/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md) +* [](/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md) +* [](/troubleshoot/elasticsearch/diagnose-unassigned-shards.md) +* [](/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md) +* []() + diff --git a/troubleshoot/elasticsearch/data.md b/troubleshoot/elasticsearch/data.md index 577a5bbde6..0ebe16f090 100644 --- a/troubleshoot/elasticsearch/data.md +++ b/troubleshoot/elasticsearch/data.md @@ -4,6 +4,23 @@ navigation_title: Data # Troubleshoot Elasticsearch data issues -% What needs to be done: Write from scratch +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on this section. Contributions welcome! +::: + +Use the topics in this section to troubleshoot {{es}} data issues: + +* [](/troubleshoot/elasticsearch/allow-all-cluster-allocation.md) +* [](/troubleshoot/elasticsearch/allow-all-index-allocation.md) +* [](/troubleshoot/elasticsearch/add-tier.md) +* [](/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md) +* [](/troubleshoot/elasticsearch/increase-tier-capacity.md) +* [](/troubleshoot/elasticsearch/increase-shard-limit.md) +* [](/troubleshoot/elasticsearch/increase-cluster-shard-limit.md) +* [](/troubleshoot/elasticsearch/corruption-troubleshooting.md) + + % see also fix-watermark-errors.md \ No newline at end of file diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md index 61c86f0a4b..4cfc1317a2 100644 --- a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md +++ b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md @@ -233,7 +233,7 @@ For more guidance on fixing the most common causes for unassinged shards please ::::::: See [this video](https://www.youtube.com/watch?v=v2mbeSd1vTQ) for a walkthrough of monitoring allocation health. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/diagnostic.md b/troubleshoot/elasticsearch/diagnostic.md index 36148f8fe7..ba929b77bc 100644 --- a/troubleshoot/elasticsearch/diagnostic.md +++ b/troubleshoot/elasticsearch/diagnostic.md @@ -15,7 +15,7 @@ You can generate diagnostic information using this tool before you contact [Elas See this [this video](https://www.youtube.com/watch?v=Bb6SaqhqYHw) for a walkthrough of capturing an {{es}} diagnostic. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: @@ -69,8 +69,7 @@ To capture an {{es}} diagnostic: sudo .\diagnostics.bat --type local --host localhost --port 9200 -u elastic -p --bypassDiagVerify --ssl --noVerify ``` - ::::{admonition} Script execution modes - :class: tip + ::::{tip} You can execute the script in three [modes](https://github.com/elastic/support-diagnostics#diagnostic-types): diff --git a/troubleshoot/elasticsearch/elasticsearch-reference.md b/troubleshoot/elasticsearch/elasticsearch-reference.md index 916e1dcdb2..e0d992f644 100644 --- a/troubleshoot/elasticsearch/elasticsearch-reference.md +++ b/troubleshoot/elasticsearch/elasticsearch-reference.md @@ -1,13 +1,14 @@ --- +navigation_title: "Elasticsearch" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting.html --- -# Elasticsearch [troubleshooting] +# Troubleshoot {{es}} [troubleshooting] This section provides a series of troubleshooting solutions aimed at helping users fix problems that an {{es}} deployment might encounter. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/fix-common-cluster-issues.md b/troubleshoot/elasticsearch/fix-common-cluster-issues.md index 8107518bf0..579ed275b7 100644 --- a/troubleshoot/elasticsearch/fix-common-cluster-issues.md +++ b/troubleshoot/elasticsearch/fix-common-cluster-issues.md @@ -11,7 +11,7 @@ mapped_pages: This guide describes how to fix common errors and problems with {{es}} clusters. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/fix-watermark-errors.md b/troubleshoot/elasticsearch/fix-watermark-errors.md index 0fec3d1bcf..17938fa29b 100644 --- a/troubleshoot/elasticsearch/fix-watermark-errors.md +++ b/troubleshoot/elasticsearch/fix-watermark-errors.md @@ -15,7 +15,7 @@ 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](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cluster.html#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. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/high-cpu-usage.md b/troubleshoot/elasticsearch/high-cpu-usage.md index 34777a6f28..07f2185617 100644 --- a/troubleshoot/elasticsearch/high-cpu-usage.md +++ b/troubleshoot/elasticsearch/high-cpu-usage.md @@ -12,7 +12,7 @@ If a thread pool is depleted, {{es}} will [reject requests](rejected-requests.md You might experience high CPU usage if a [data tier](../../manage-data/lifecycle/data-tiers.md), and therefore the nodes assigned to that tier, is experiencing more traffic than other tiers. This imbalance in resource utilization is also known as [hot spotting](hotspotting.md). -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md index 7fd5572bb8..c9290ea23f 100644 --- a/troubleshoot/elasticsearch/high-jvm-memory-pressure.md +++ b/troubleshoot/elasticsearch/high-jvm-memory-pressure.md @@ -7,7 +7,7 @@ mapped_pages: 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%. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/hotspotting.md b/troubleshoot/elasticsearch/hotspotting.md index c1205e59aa..9d99211ae9 100644 --- a/troubleshoot/elasticsearch/hotspotting.md +++ b/troubleshoot/elasticsearch/hotspotting.md @@ -11,7 +11,7 @@ mapped_pages: Computer [hot spotting](https://en.wikipedia.org/wiki/Hot_spot_(computer_programming)) may occur in {{es}} when resource utilizations are unevenly distributed across [nodes](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html). Temporary spikes are not usually considered problematic, but ongoing significantly unique utilization may lead to cluster bottlenecks and should be reviewed. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md index aab5dde603..883be25e3a 100644 --- a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md +++ b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md @@ -128,7 +128,7 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec :::::: ::::::: -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md index d7358b8df8..22038406b0 100644 --- a/troubleshoot/elasticsearch/increase-shard-limit.md +++ b/troubleshoot/elasticsearch/increase-shard-limit.md @@ -127,8 +127,6 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec ``` :::::: -::::::: -::::{admonition} +:::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). - -:::: +::: diff --git a/troubleshoot/elasticsearch/increase-tier-capacity.md b/troubleshoot/elasticsearch/increase-tier-capacity.md index 64604f334b..723cb0f9bc 100644 --- a/troubleshoot/elasticsearch/increase-tier-capacity.md +++ b/troubleshoot/elasticsearch/increase-tier-capacity.md @@ -205,7 +205,7 @@ Alternatively, if adding more nodes to the {{es}} cluster is not desired, inspec :::::: ::::::: -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/more-topics.md b/troubleshoot/elasticsearch/more-topics.md index 692ad11965..b27e9ad218 100644 --- a/troubleshoot/elasticsearch/more-topics.md +++ b/troubleshoot/elasticsearch/more-topics.md @@ -4,4 +4,10 @@ navigation_title: More topics # More Elasticsearch troubleshooting topics +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on this section. Contributions welcome! +::: + % What needs to be done: Write from scratch diff --git a/troubleshoot/elasticsearch/red-yellow-cluster-status.md b/troubleshoot/elasticsearch/red-yellow-cluster-status.md index 8a3e057820..6928108a14 100644 --- a/troubleshoot/elasticsearch/red-yellow-cluster-status.md +++ b/troubleshoot/elasticsearch/red-yellow-cluster-status.md @@ -15,7 +15,7 @@ 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. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/rejected-requests.md b/troubleshoot/elasticsearch/rejected-requests.md index 60d0586e5f..7832af9be3 100644 --- a/troubleshoot/elasticsearch/rejected-requests.md +++ b/troubleshoot/elasticsearch/rejected-requests.md @@ -11,7 +11,7 @@ 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](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-indexing-pressure.html) that exceeds the [`indexing_pressure.memory.limit`](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-indexing-pressure.html#memory-limits). -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md index a7127c14c6..3739bc7e9c 100644 --- a/troubleshoot/elasticsearch/repeated-snapshot-failures.md +++ b/troubleshoot/elasticsearch/repeated-snapshot-failures.md @@ -166,7 +166,7 @@ In the event that snapshots are failing for other reasons check the logs on the :::::: ::::::: -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/snapshot-and-restore.md b/troubleshoot/elasticsearch/snapshot-and-restore.md index c87bb8949f..3906aeb9e1 100644 --- a/troubleshoot/elasticsearch/snapshot-and-restore.md +++ b/troubleshoot/elasticsearch/snapshot-and-restore.md @@ -4,4 +4,10 @@ navigation_title: Snapshot and restore # Troubleshoot snapshot and restore +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on this section. Contributions welcome! +::: + % What needs to be done: Write from scratch diff --git a/troubleshoot/elasticsearch/start-ilm.md b/troubleshoot/elasticsearch/start-ilm.md index f5356d2bd0..81645dfeee 100644 --- a/troubleshoot/elasticsearch/start-ilm.md +++ b/troubleshoot/elasticsearch/start-ilm.md @@ -2,6 +2,7 @@ navigation_title: Lifecycle management mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/start-ilm.html + - https://www.elastic.co/guide/en/elasticsearch/reference/current/start-slm.html --- % TODO reframe how-to stuff as troubleshooting content diff --git a/troubleshoot/elasticsearch/task-queue-backlog.md b/troubleshoot/elasticsearch/task-queue-backlog.md index c602e05087..7cfae0a2ee 100644 --- a/troubleshoot/elasticsearch/task-queue-backlog.md +++ b/troubleshoot/elasticsearch/task-queue-backlog.md @@ -5,11 +5,8 @@ mapped_pages: # Task queue backlog [task-queue-backlog] -::::{admonition} -**Product:** Elasticsearch
**Deployment type:** Elastic Cloud Enterprise, Elastic Cloud Hosted, Elastic Cloud on Kubernetes, Elastic Self-Managed
**Versions:** All - -:::: - +% **Product:** Elasticsearch
**Deployment type:** Elastic Cloud % Enterprise, Elastic Cloud Hosted, Elastic Cloud on Kubernetes, Elastic +% Self-Managed
**Versions:** All A backlogged task queue can prevent tasks from completing and lead to an unhealthy cluster state. Contributing factors include resource constraints, a large number of tasks triggered at once, and long-running tasks. @@ -116,4 +113,4 @@ Related symptoms: * [High CPU usage](high-cpu-usage.md) * [Rejected requests](rejected-requests.md) * [Hot spotting](hotspotting.md) - +* [Troubeshooting overview](/troubleshoot/index.md) diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md index ef3a777042..63a6c142bd 100644 --- a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md +++ b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md @@ -425,7 +425,7 @@ PUT _cluster/settings :::::: ::::::: -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md index 0f6f3b7cd3..7772b9bd63 100644 --- a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md +++ b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md @@ -14,7 +14,7 @@ Elasticsearch balances shards across data tiers to achieve a good compromise bet * disk usage * write load (for indices in data streams) -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md index 4277bcf689..bfd05ef887 100644 --- a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md +++ b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md @@ -14,7 +14,7 @@ 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. -::::{admonition} +::::{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, real-time issue detection and resolution paths. For more information, refer to [Monitor with AutoOps](https://www.elastic.co/guide/en/cloud/current/ec-autoops.html). :::: diff --git a/troubleshoot/index.md b/troubleshoot/index.md index 2d9ce6d005..ccf5f83ef7 100644 --- a/troubleshoot/index.md +++ b/troubleshoot/index.md @@ -1,4 +1,5 @@ --- +navigation_title: "Troubleshoot" mapped_urls: - https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/get-support-help.html - https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/troubleshooting-and-faqs.html @@ -9,8 +10,31 @@ mapped_urls: % What needs to be done: Refine +:::{admonition} WIP +⚠️ **This section is a work in progress.** ⚠️ + +The documentation team is actively working on structure, user focus, and more. +::: + +Use the topics in this section to troubleshoot Elastic products, features, and deployments. + + +* [](/troubleshoot/elasticsearch/elasticsearch-reference.md) +* [](/troubleshoot/kibana.md) +* [](/troubleshoot/observability.md) +* [](/troubleshoot/security.md) +* [](/troubleshoot/ingest.md) +* [](/troubleshoot/deployments/elastic-cloud.md) +* [](/troubleshoot/deployments/cloud-enterprise/cloud-enterprise.md) +* [](/troubleshoot/deployments/cloud-on-k8s/kubernetes.md) + + ## Contact us [contact-us] +:::{warning} +Work in progress +::: + % Scope notes: - Match new content type; TOC entry TBD - consider splitting out subsections? % Use migrated content from existing pages that map to this page: diff --git a/troubleshoot/ingest.md b/troubleshoot/ingest.md index 4a6abf467d..c26eeb9075 100644 --- a/troubleshoot/ingest.md +++ b/troubleshoot/ingest.md @@ -1,3 +1,25 @@ -# Ingest tools +--- +navigation_title: "Ingest tools" +--- + +# Troubleshoot ingestion tools + +:::{admonition} WIP +⚠️ **This page is a work in progress.** ⚠️ + +The documentation team is working on restructuring this section. +::: + +Use the topics in this section to troubleshoot ingestion tools: + +* [](/troubleshoot/ingest/logstash.md) +* [](/troubleshoot/ingest/fleet/fleet-elastic-agent.md) +* [](/troubleshoot/ingest/beats-loggingplugin/elastic-logging-plugin-for-docker.md) +* []() +* []() +* []() +* []() +* []() +* []() +* []() -% What needs to be done: Write from scratch \ No newline at end of file diff --git a/troubleshoot/kibana.md b/troubleshoot/kibana.md index 978dee45fd..14ca40c32c 100644 --- a/troubleshoot/kibana.md +++ b/troubleshoot/kibana.md @@ -6,16 +6,17 @@ mapped_pages: # Troubleshoot Kibana [kibana-troubleshooting] -These topics help you troubleshoot issues with {{kib}}: - -## Debugging - -* [Using {{kib}} server logs](kibana/using-kibana-server-logs.md) -* [Trace {{es}} query to the origin in {{kib}}](kibana/trace-elasticsearch-query-to-the-origin-in-kibana.md) -* [Capture {{kib}} diagnostic](kibana/capturing-diagnostics.md) - -## General -* -* - +Use the topics in this section to troubleshoot issues with {{kib}}: +* [](/troubleshoot/kibana/using-kibana-server-logs.md) +* [](/troubleshoot/kibana/access.md) +* [](/troubleshoot/kibana/error-server-not-ready.md) +* [](/troubleshoot/kibana/trace-elasticsearch-query-to-the-origin-in-kibana.md) +* [](/troubleshoot/kibana/monitoring.md) +* [](/troubleshoot/kibana/alerts.md) +* [](/troubleshoot/kibana/reporting.md) +* [](/troubleshoot/kibana/task-manager.md) +* [](/troubleshoot/kibana/maps.md) +* [](/troubleshoot/kibana/graph.md) +* [](/troubleshoot/kibana/migration-failures.md) +* [](/troubleshoot/kibana/capturing-diagnostics.md) \ No newline at end of file diff --git a/troubleshoot/kibana/capturing-diagnostics.md b/troubleshoot/kibana/capturing-diagnostics.md index b922b9abbe..c28d955f7a 100644 --- a/troubleshoot/kibana/capturing-diagnostics.md +++ b/troubleshoot/kibana/capturing-diagnostics.md @@ -63,8 +63,7 @@ To run a {{kib}} diagnostic: sudo .\diagnostics.bat --type kibana-local --host localhost --port 5601 -u elastic -p --bypassDiagVerify --ssl --noVerify ``` - ::::{admonition} Script execution modes - :class: tip + ::::{tip} You can execute the script in three [modes](https://github.com/elastic/support-diagnostics#diagnostic-types): diff --git a/troubleshoot/monitoring/autoops.md b/troubleshoot/monitoring/autoops.md deleted file mode 100644 index 8e7e7cb476..0000000000 --- a/troubleshoot/monitoring/autoops.md +++ /dev/null @@ -1,5 +0,0 @@ -# AutoOps - -% What needs to be done: Write from scratch - -% Scope notes: position in TOC TBD \ No newline at end of file diff --git a/troubleshoot/monitoring/cloud.md b/troubleshoot/monitoring/cloud.md deleted file mode 100644 index 1f62c78f3d..0000000000 --- a/troubleshoot/monitoring/cloud.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud/current/ec-monitoring-diagnose-resolve.html ---- - -# Monitoring [ec-monitoring-diagnose-resolve] - -Use the topics in this section to troubleshoot monitoring, including AutoOps. - -* [](/troubleshoot/monitoring/autoops.md) -* [](/troubleshoot/monitoring/unavailable-nodes.md) -* [](/troubleshoot/monitoring/unavailable-shards.md) -* [](/troubleshoot/monitoring/performance.md) -* [](/troubleshoot/monitoring/high-memory-pressure.md) -* [](/troubleshoot/monitoring/high-availability.md) -* [](/troubleshoot/monitoring/cluster-response-time.md) -* [](/troubleshoot/monitoring/node-moves-outages.md) -* [](/troubleshoot/monitoring/deployment-health-warnings.md) -* [](/troubleshoot/monitoring/node-bootlooping.md) - - - - - - diff --git a/troubleshoot/monitoring/cluster-response-time.md b/troubleshoot/monitoring/cluster-response-time.md index 4c7235b2db..125093a6d5 100644 --- a/troubleshoot/monitoring/cluster-response-time.md +++ b/troubleshoot/monitoring/cluster-response-time.md @@ -19,10 +19,4 @@ Memory pressure is not the culprit. The **Memory Pressure per Node** metric is a So what caused the sudden increase in response times? The key to the puzzle lies in the **Number of Requests** metric, which indicates the number of requests that a cluster receives per second. Beginning shortly before 13:32, there was a substantial increase in the number of user requests per second. The number of requests per second continued to rise until the requests began to plateau as your cluster reached its maximum throughput, which in turn caused response times to rise. The number of requests remained at a high level for approximately five minutes, until they started to drop off again around 13:40. Overall, the sustained increase of user requests lasted a bit over 10 minutes, consistent with the slowdown you observed. -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. - - - -% Notes: Lift and shift this one -% - [ ] ./raw-migrated-files/cloud/cloud-heroku/echscenario_why_are_my_cluster_response_times_suddenly_so_much_worse.md -% Notes: dupe, redirect \ No newline at end of file +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. \ No newline at end of file diff --git a/troubleshoot/monitoring/unavailable-nodes.md b/troubleshoot/monitoring/unavailable-nodes.md index 9631965208..18fcc6397c 100644 --- a/troubleshoot/monitoring/unavailable-nodes.md +++ b/troubleshoot/monitoring/unavailable-nodes.md @@ -324,22 +324,3 @@ Stack Monitoring comes with out-of-the-box rules, but you need to enable them wh * Nodes unable to join: Fix the {{es}} configuration. * Nodes unable to join: Contact support. - - -% Notes: dupe - -% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc): - -$$$ec-single-node-deployment-disk-used$$$ - -$$$ec-multiple-node-deployment-disk-used$$$ - -$$$ec-single-node-deployment-disk-used$$$ - -$$$ec-multiple-node-deployment-disk-used$$$ - -$$$ec-jvm-heap-usage-exceed-allowed-threshold$$$ - -$$$ec-cpu-usage-exceed-allowed-threshold$$$ - -$$$ec-nodes-unavailable-missing$$$ \ No newline at end of file diff --git a/troubleshoot/observability.md b/troubleshoot/observability.md index 49d8f7e06d..2224ada060 100644 --- a/troubleshoot/observability.md +++ b/troubleshoot/observability.md @@ -4,7 +4,7 @@ mapped_pages: - https://www.elastic.co/guide/en/observability/current/troubleshooting.html --- -# Troubleshoot observability [troubleshooting] +# Troubleshoot Observability [troubleshooting] Learn how to troubleshoot common issues on your own or ask for help. diff --git a/troubleshoot/observability/apm/known-issues.md b/troubleshoot/observability/apm/known-issues.md index 324c989f3a..16420ef09e 100644 --- a/troubleshoot/observability/apm/known-issues.md +++ b/troubleshoot/observability/apm/known-issues.md @@ -110,7 +110,7 @@ There are three ways to fix this error: 1. Find broken rules - :::::{admonition} + :::::{{tip} To identify rules in this exact state, you can use the [find rules endpoint](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-alerting) and search for the APM anomaly rule type as well as this exact error message indicating that the rule is in the broken state. We will also use the `fields` parameter to specify only the fields required when making the update request later. * `search_fields=alertTypeId` @@ -162,7 +162,7 @@ There are three ways to fix this error: 2. Prepare the update JSON doc(s) - ::::{admonition} + ::::{tip} For each broken rule found, create a JSON rule document with what was returned from the API in the previous step. You will need to make two changes to each document: 1. Remove the `id` key but keep the value connected to this document (e.g. rename the file to `{{id}}.json`). **The `id` cannot be sent as part of the request body for the PUT request, but you will need it for the URL path.** @@ -187,7 +187,7 @@ There are three ways to fix this error: 3. Update each rule using the `PUT /api/alerting/rule/{{id}}` API - ::::{admonition} + ::::{tip} For each rule, submit a PUT request to the [update rule endpoint](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-alerting) using that rule’s ID and its stored update document from the previous step. For example, assuming the first broken rule’s ID is `046c0d4f`: ```shell diff --git a/troubleshoot/security.md b/troubleshoot/security.md index 65c6741984..16c1e85952 100644 --- a/troubleshoot/security.md +++ b/troubleshoot/security.md @@ -1,10 +1,11 @@ --- +navigation_title: "Security" mapped_pages: - https://www.elastic.co/guide/en/security/current/troubleshooting-ov.html - https://www.elastic.co/guide/en/serverless/current/security-troubleshooting-ov.html --- -# Security [troubleshooting-ov] +# Troubleshoot Security [troubleshooting-ov] This section covers common {{elastic-sec}} related issues and how to resolve them. diff --git a/troubleshoot/toc.yml b/troubleshoot/toc.yml index 2755e74a01..741dcb1032 100644 --- a/troubleshoot/toc.yml +++ b/troubleshoot/toc.yml @@ -107,69 +107,6 @@ toc: - file: kibana/graph.md - file: kibana/migration-failures.md - file: kibana/capturing-diagnostics.md - - file: deployments.md - children: - - file: deployments/serverless.md - children: - - file: deployments/serverless-status.md - - file: deployments/esf/elastic-serverless-forwarder.md - - file: deployments/elastic-cloud.md - children: - - file: deployments/elastic-cloud/sso.md - - file: deployments/elastic-cloud/monitoring.md - - file: deployments/cloud-enterprise/cloud-enterprise.md - children: - - file: deployments/cloud-enterprise/common-issues.md - - file: deployments/cloud-enterprise/use-emergency-roles-token.md - - file: deployments/cloud-enterprise/remove-cloud-enterprise.md - - file: deployments/cloud-enterprise/verify-zookeeper-sync-status.md - - file: deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md - - file: deployments/cloud-enterprise/troubleshooting-container-engines.md - - file: deployments/cloud-enterprise/run-ece-diagnostics-tool.md - - file: deployments/cloud-enterprise/ask-for-help.md - - file: deployments/cloud-enterprise/heap-dumps.md - - file: deployments/cloud-enterprise/thread-dumps.md - - file: deployments/cloud-on-k8s/kubernetes.md - children: - - file: deployments/cloud-on-k8s/common-problems.md - - file: deployments/cloud-on-k8s/troubleshooting-methods.md - - file: deployments/cloud-on-k8s/run-eck-diagnostics.md - - file: deployments/cloud-on-k8s/jvm-heap-dumps.md - - file: monitoring/cloud.md - children: - - file: monitoring/autoops.md - - file: monitoring/unavailable-nodes.md - - file: monitoring/unavailable-shards.md - - file: monitoring/performance.md - children: - - file: monitoring/high-memory-pressure.md - - file: monitoring/high-availability.md - - file: monitoring/cluster-response-time.md - - file: monitoring/node-moves-outages.md - - file: monitoring/deployment-health-warnings.md - - file: monitoring/node-bootlooping.md - - file: ingest.md - children: - # - file: ingest/enterprise-search/crawls.md - - file: ingest/logstash.md - children: - - file: ingest/logstash/plugins.md - children: - - file: ingest/logstash/kafka.md - - file: ingest/logstash/azure-event-hub.md - - file: ingest/logstash/health-report-pipelines.md - - file: ingest/logstash/contribute.md - - file: ingest/fleet/fleet-elastic-agent.md - children: - - file: ingest/fleet/common-problems.md - - file: ingest/fleet/frequently-asked-questions.md - - file: ingest/beats-loggingplugin/elastic-logging-plugin-for-docker.md - - file: security.md - children: - - file: security/detection-rules.md - - file: security/elastic-defend.md - - file: security/indicators-of-compromise.md - - file: security/agentless-integrations.md - file: observability.md children: - file: observability/explore-data.md @@ -205,4 +142,61 @@ toc: - file: observability/troubleshooting-infrastructure-monitoring.md children: - file: observability/troubleshooting-infrastructure-monitoring/understanding-no-results-found-message.md - - file: observability/troubleshoot-service-level-objectives-slos.md \ No newline at end of file + - file: observability/troubleshoot-service-level-objectives-slos.md + - file: security.md + children: + - file: security/detection-rules.md + - file: security/elastic-defend.md + - file: security/indicators-of-compromise.md + - file: security/agentless-integrations.md + - file: ingest.md + children: + # - file: ingest/enterprise-search/crawls.md + - file: ingest/logstash.md + children: + - file: ingest/logstash/plugins.md + children: + - file: ingest/logstash/kafka.md + - file: ingest/logstash/azure-event-hub.md + - file: ingest/logstash/health-report-pipelines.md + - file: ingest/logstash/contribute.md + - file: ingest/fleet/fleet-elastic-agent.md + children: + - file: ingest/fleet/common-problems.md + - file: ingest/fleet/frequently-asked-questions.md + - file: ingest/beats-loggingplugin/elastic-logging-plugin-for-docker.md + - file: deployments/elastic-cloud.md + children: + - file: deployments/serverless.md + children: + - file: deployments/serverless-status.md + - file: deployments/esf/elastic-serverless-forwarder.md + - file: deployments/elastic-cloud/sso.md + - file: monitoring/unavailable-nodes.md + - file: monitoring/unavailable-shards.md + - file: monitoring/performance.md + children: + - file: monitoring/high-memory-pressure.md + - file: monitoring/high-availability.md + - file: monitoring/cluster-response-time.md + - file: monitoring/node-moves-outages.md + - file: monitoring/deployment-health-warnings.md + - file: monitoring/node-bootlooping.md + - file: deployments/cloud-enterprise/cloud-enterprise.md + children: + - file: deployments/cloud-enterprise/common-issues.md + - file: deployments/cloud-enterprise/use-emergency-roles-token.md + - file: deployments/cloud-enterprise/remove-cloud-enterprise.md + - file: deployments/cloud-enterprise/troubleshooting-container-engines.md + - file: deployments/cloud-enterprise/verify-zookeeper-sync-status.md + - file: deployments/cloud-enterprise/rebuilding-broken-zookeeper-quorum.md + - file: deployments/cloud-enterprise/run-ece-diagnostics-tool.md + - file: deployments/cloud-enterprise/heap-dumps.md + - file: deployments/cloud-enterprise/thread-dumps.md + - file: deployments/cloud-enterprise/ask-for-help.md + - file: deployments/cloud-on-k8s/kubernetes.md + children: + - file: deployments/cloud-on-k8s/common-problems.md + - file: deployments/cloud-on-k8s/troubleshooting-methods.md + - file: deployments/cloud-on-k8s/run-eck-diagnostics.md + - file: deployments/cloud-on-k8s/jvm-heap-dumps.md \ No newline at end of file