From ca41db3021bc474dd82b3a5805bfbd6cbd8cca9b Mon Sep 17 00:00:00 2001 From: Colleen McGinnis Date: Tue, 15 Oct 2024 09:55:26 -0500 Subject: [PATCH] address feedback --- .../filter-and-search/cross-cluster-search.asciidoc | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/docs/en/observability/apm/view-and-analyze/filter-and-search/cross-cluster-search.asciidoc b/docs/en/observability/apm/view-and-analyze/filter-and-search/cross-cluster-search.asciidoc index 463ee1cf4b..208329e25a 100644 --- a/docs/en/observability/apm/view-and-analyze/filter-and-search/cross-cluster-search.asciidoc +++ b/docs/en/observability/apm/view-and-analyze/filter-and-search/cross-cluster-search.asciidoc @@ -49,9 +49,6 @@ include remote clusters. * In `kibana.yml` -- Update the {kibana-ref}/apm-settings-kb.html[`xpack.apm.indices.*`] configuration values to include remote clusters. -// I'm not sure if this is better presented as a troubleshooting topic (i.e. reactive) -// or a best practice (i.e. preventative). For now I've added it as a tip, but it could -// be more integrated into the content on this page. [TIP] .Exclude data tiers from search ==== @@ -59,9 +56,7 @@ In a cross-cluster search (CCS) environment, it's possible for different cluster If one of the requested clusters responds slowly, it can cause a timeout at the proxy after 320 and 502 responses presented as failure toast messages in the UI with no data loaded. -// Fix or prevent? -To fix/prevent this, you can exclude {ref}/data-tiers.html[data tiers] that might slow down responses from search -(for example, the `data_frozen` tier). To exclude data tiers from search in the APM UI: +To prevent this, you can exclude {ref}/data-tiers.html[data tiers] that might slow down responses from search: the `data_frozen` and `data_cold` tiers. To exclude data tiers from search in the APM UI: . In {kib}, go to *Stack Management* → *Advanced Settings*. . In the *Observability* section, update the *Excluded data tiers from search* option with a list of data tiers.