applies to applies_to

bmorelli25 · bmorelli25 · commit 6d7c68fee965 · 2025-02-18T15:04:33.000-08:00
Signed-off-by: bmorelli25 &lt;brandon.morelli@elastic.co&gt;
diff --git a/deploy-manage/cloud-organization/billing/manage-subscription.md b/deploy-manage/cloud-organization/billing/manage-subscription.md
@@ -39,7 +39,7 @@ To change your subscription level:
 
 ### Feature usage notifications [ec_feature_usage_notifications]
 
-:::{applies}
+:::{applies_to}
 :hosted: all
 :::
 
diff --git a/deploy-manage/users-roles.md b/deploy-manage/users-roles.md
@@ -29,7 +29,7 @@ Preventing unauthorized access is only one element of a complete security strate
 
 ## Cloud organization level
 
-:::{applies}
+:::{applies_to}
 :hosted: all
 :serverless: all
 :::
@@ -50,7 +50,7 @@ For {{ech}} deployments, you can configure SSO at the organization level, the de
 
 ## Orchestrator level
 
-:::{applies}
+:::{applies_to}
 :ece: all
 :::
 
@@ -77,7 +77,7 @@ You can't manage users and roles for {{eck}} clusters at the orchestrator level.
 
 ## Project level
 
-:::{applies}
+:::{applies_to}
 :serverless: all
 :::
 
@@ -87,7 +87,7 @@ As an extension of the [predefined instance access roles](/deploy-manage/users-r
 
 ## Cluster or deployment level
 
-:::{applies}
+:::{applies_to}
 :ece: all
 :hosted: all
 :eck: all
diff --git a/deploy-manage/users-roles/cloud-organization.md b/deploy-manage/users-roles/cloud-organization.md
@@ -25,7 +25,7 @@ If you're using {{ech}}, then you can also manage users and control access [at t
 
 ## Should I use organization-level or deployment-level SSO? [organization-deployment-sso] 
 
-:::{applies}
+:::{applies_to}
 :hosted: all
 :::
 
diff --git a/explore-analyze/find-and-organize/data-views.md b/explore-analyze/find-and-organize/data-views.md
@@ -101,7 +101,7 @@ Temporary {{data-sources}} are not available in the **Management** menu.
 
 
 ### Use {{data-sources}} with rolled up data [rollup-data-view]
-::::{applies}
+::::{applies_to}
 :serverless: unavailable
 :stack: deprecated
 ::::
@@ -123,7 +123,7 @@ For an example, refer to [Create and visualize rolled up data](/manage-data/life
 
 
 ### Use {{data-sources}} with {{ccs}} [management-cross-cluster-search]
-::::{applies}
+::::{applies_to}
 :serverless: unavailable
 :stack: ga
 ::::
diff --git a/explore-analyze/find-and-organize/saved-objects.md b/explore-analyze/find-and-organize/saved-objects.md
@@ -126,7 +126,7 @@ However, saved objects can only be imported into the same version, a newer minor
 | 7.8.1 | 9.0.0 | No |
 
 ## Saved Object IDs [saved-object-ids]
-::::{applies}
+::::{applies_to}
 :stack:
 ::::
 
diff --git a/troubleshoot/observability/apm/common-problems.md b/troubleshoot/observability/apm/common-problems.md
@@ -26,7 +26,7 @@ This section describes common problems you might encounter when using APM Server
 
 
 ## No data is indexed [apm-no-data-indexed]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -83,7 +83,7 @@ APM Server currently relies on {{es}} to create indices that do not exist. As a
 :::::::
 
 ## Common SSL-related problems [apm-common-ssl-problems]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -134,7 +134,7 @@ A firewall is refusing the connection. Check if a firewall is blocking the traff
 
 
 ## I/O Timeout [apm-io-timeout]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -177,15 +177,15 @@ In the agent logs, you won’t see a sign of failures as the APM server asynchro
 
 
 ## Tail-based sampling causing high system memory usage and high disk IO [apm-tail-based-sampling-memory-disk-io]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
 Tail-based sampling requires minimal memory to run, and there should not be a noticeable increase in RSS memory usage. However, since tail-based sampling writes data to disk, it is possible to see a significant increase in OS page cache memory usage due to disk IO. If you see a drop in throughput and excessive disk activity after enabling tail-based sampling, please ensure that there is enough memory headroom in the system for OS page cache to perform disk IO efficiently.
 
 
 ## Too many unique transaction names [troubleshooting-too-many-transactions]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -231,7 +231,7 @@ If your problem is occurring in a different APM agent, the tips above still appl
 
 
 ## Unknown route [troubleshooting-unknown-route]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -245,7 +245,7 @@ To resolve this, you’ll need to head over to the relevant [APM agent documenta
 
 
 ## Fields are not searchable [troubleshooting-fields-unsearchable]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -262,7 +262,7 @@ As an example, some APM agents store cookie values in `http.request.cookies`. Si
 
 
 ## Service Maps: no connection between client and server [service-map-rum-connections]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -272,7 +272,7 @@ This setting is necessary, for example, for cross-origin requests. If you have a
 
 
 ## No data shown in the infrastructure tab [troubleshooting-apm-infra-data]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -292,7 +292,7 @@ For example, if the APM agent is not configured to use the correct host name, th
 
 
 ## Common response codes [observability-apm-troubleshooting-common-response-codes]
-:::{applies}
+:::{applies_to}
 :serverless: all
 :::
 
diff --git a/troubleshoot/observability/troubleshoot-logs.md b/troubleshoot/observability/troubleshoot-logs.md
@@ -63,7 +63,7 @@ You need to either:
 
 
 ### Failed to create API key [logs-troubleshooting-API-key-failed]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
diff --git a/troubleshoot/observability/troubleshoot-service-level-objectives-slos.md b/troubleshoot/observability/troubleshoot-service-level-objectives-slos.md
@@ -191,7 +191,7 @@ Refer to [SLO API calls](https://www.elastic.co/docs/api/doc/kibana/v8/operation
 
 
 ## Upgrade from beta to GA [slo-troubleshoot-beta]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
diff --git a/troubleshoot/observability/troubleshooting-synthetics.md b/troubleshoot/observability/troubleshooting-synthetics.md
@@ -18,7 +18,7 @@ For debugging synthetic tests locally, you can set an environment variable, `DEB
 
 
 ### Monitors stopped running after upgrading to 8.8.0 or above [synthetics-troubleshooting-missing-api-key]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
@@ -128,7 +128,7 @@ There are a few ways to fix this:
 ::::
 
 ### You do not have permission to use Elastic managed locations [synthetics-troubleshooting-public-locations-disabled]
-:::{applies}
+:::{applies_to}
 :stack: all
 :::
 
diff --git a/troubleshoot/security/detection-rules.md b/troubleshoot/security/detection-rules.md
@@ -182,7 +182,7 @@ For example, say an event occurred at 10:00 but wasn’t ingested into {{es}} un
 
 
 ### Troubleshoot missing alerts for {{ml}} jobs [ml-job-compatibility]
-:::{applies}
+:::{applies_to}
 :serverless: unavailable
 :::
 % doesn't apply to serverless 
