Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[APM] Adds information on excluding data tiers from searches #4327

Merged
merged 5 commits into from
Oct 21, 2024
Merged

[APM] Adds information on excluding data tiers from searches #4327

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3c73e58
initial draft
colleenmcginnis Oct 1, 2024
3ab6530
Merge branch 'main' into issue-4311
colleenmcginnis Oct 7, 2024
ca41db3
address feedback
colleenmcginnis Oct 15, 2024
9085ac1
Merge branch 'main' into issue-4311
bmorelli25 Oct 19, 2024
5346d61
add feedback
bmorelli25 Oct 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions ...ervability/apm/view-and-analyze/filter-and-search/cross-cluster-search.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ and allowing for better performance while managing multiple observability use ca
If you're using the Hosted {ess}, see {cloud}/ec-enable-ccs.html[Enable cross-cluster search].

// lint ignore elasticsearch
You can add remote clusters directly in {kib}, under *Management* > *Elasticsearch* > *Remote clusters*.
You can add remote clusters directly in {kib}, under *Management* → *Elasticsearch* → *Remote clusters*.
All you need is a name for the remote cluster and the seed node(s).
Remember the names of your remote clusters, you'll need them in step two.
See {ref}/ccr-getting-started.html[managing remote clusters] for detailed information on the setup process.
Expand All @@ -44,7 +44,20 @@ You can also specify certain clusters to display data from, for example,

There are two ways to edit the default {data-source}:

* In the APM UI -- Navigate to *APM* > *Settings* > *Indices*, and change all `xpack.apm.indices.*` values to
* In the APM UI -- Navigate to *APM* → *Settings* → *Indices*, and change all `xpack.apm.indices.*` values to
include remote clusters.
* In `kibana.yml` -- Update the {kibana-ref}/apm-settings-kb.html[`xpack.apm.indices.*`] configuration values to
include remote clusters.

[TIP]
.Exclude data tiers from search
====
In a cross-cluster search (CCS) environment, it's possible for different clusters to serve different data tiers in responses.
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.
colleenmcginnis marked this conversation as resolved.
Show resolved Hide resolved
bmorelli25 marked this conversation as resolved.
Show resolved Hide resolved

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:
bmorelli25 marked this conversation as resolved.
Show resolved Hide resolved

. 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.
====