From 8f26f9a280103299209b4fe8a805f2888479be4e Mon Sep 17 00:00:00 2001 From: alicejw Date: Fri, 20 May 2022 16:12:49 -0700 Subject: [PATCH] last clarity rewrite Signed-off-by: alicejw --- _dashboards/search-telemetry.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/_dashboards/search-telemetry.md b/_dashboards/search-telemetry.md index ab0e72ec..ead9b249 100644 --- a/_dashboards/search-telemetry.md +++ b/_dashboards/search-telemetry.md @@ -11,8 +11,6 @@ You can use search telemetry to analyze performance for success or failed search Because there are thousands of concurrent search request from OpenSearch Dashboards, the large traffic causes significant load in an OpenSearch cluster. -By default it is disabled, so you need to do some configuration changes to enable it. - OpenSearch clusters perform better with search telemetry turned off. {: .tip } @@ -26,7 +24,7 @@ When you enable telemetry in the OpenSearch Dashboards YAML file, this overrides {: .note } ### To opt-in or opt-out of search telemetry data -The following table shows the values to opt-in or opt-out of search telemetry data in the OpenSearch Dashboards YAML file setting `data.search.usageTelemetry.enabled`. +The following table shows the OpenSearch Dashboards YAML file setting `data.search.usageTelemetry.enabled` values you can choose to opt-in or opt-out of search telemetry. OpenSearch Dashboards YAML value | Opt-in or Opt-out of search telemetry :--- | :---