Update to new screenshot syntax (#681)

Updates images previously marked as screenshots with `:class:
screenshot` to the new syntax, `:screenshot:`, which was added in
elastic/docs-builder#665.

Note: Requires a new version of docs-builder to be released before the
preview will show any differences.

Author: bmorelli25

deploy-manage/api-keys/serverless-project-api-keys.md

@@ -16,7 +16,7 @@ You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-
 
 :::{image} ../../images/serverless-api-key-management.png
 :alt: API keys UI
-:class: screenshot
+:screenshot:
 :::
 
 
@@ -26,7 +26,7 @@ In **{{api-keys-app}}**, click **Create API key**:
 
 :::{image} ../../images/serverless-create-personal-api-key.png
 :alt: Create API key UI
-:class: screenshot
+:screenshot:
 :width: 50%
 :::
 

deploy-manage/autoscaling/trained-model-autoscaling.md

@@ -70,7 +70,7 @@ Refer to the tables in the [Model deployment resource matrix](#model-deployment-
 
 :::{image} ../../images/machine-learning-ml-nlp-deployment-id-elser-v2.png
 :alt: ELSER deployment with adaptive resources enabled.
-:class: screenshot
+:screenshot:
 :width: 500px
 :::
 

deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md

@@ -325,7 +325,7 @@ To avoid this, explicitly define the requests and limits mandated by your enviro
 
 :::{image} ../../../images/cloud-on-k8s-metrics-explorer-cpu.png
 :alt: cgroup CPU perforamce chart
-:class: screenshot
+:screenshot:
 :::
 
 
@@ -355,6 +355,6 @@ The **Cgroup usage** curve shows that the CPU usage of this container has been s
 
 :::{image} ../../../images/cloud-on-k8s-cgroups-cfs-stats.png
 :alt: cgroup CPU perforamce chart
-:class: screenshot
+:screenshot:
 :::
 

deploy-manage/manage-connectors.md

@@ -34,14 +34,14 @@ In **{{stack-manage-app}} > {{connectors-ui}}**, you can find a list of the conn
 
 :::{image} ../images/kibana-connector-filter-by-type.png
 :alt: Filtering the connector list by types of connectors
-:class: screenshot
+:screenshot:
 :::
 
 You can delete individual connectors using the trash icon. Alternatively, select multiple connectors and delete them in bulk using the **Delete** button.
 
 :::{image} ../images/kibana-connector-delete.png
 :alt: Deleting connectors individually or in bulk
-:class: screenshot
+:screenshot:
 :::
 
 ::::{note}
@@ -59,7 +59,7 @@ Some connector types are paid commercial features, while others are free. For a
 
 :::{image} ../images/kibana-connector-select-type.png
 :alt: Connector select type
-:class: screenshot
+:screenshot:
 :width: 75%
 :::
 
@@ -81,7 +81,7 @@ If a connector is missing sensitive information after the import, a **Fix** butt
 
 :::{image} ../images/kibana-connectors-with-missing-secrets.png
 :alt: Connectors with missing secrets
-:class: screenshot
+:screenshot:
 :::
 
 ## Monitoring connectors [monitoring-connectors]

deploy-manage/manage-spaces.md

@@ -19,7 +19,7 @@ mapped_urls:
 
 :::{image} ../images/kibana-change-space.png
 :alt: Change current space menu
-:class: screenshot
+:screenshot:
 :::
 
 To go to **Spaces**, find **Stack Management** in the navigation menu or use the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md).
@@ -133,5 +133,5 @@ To configure the landing page, use the default route setting in [Stack Managemen
 
 :::{image} ../images/kibana-spaces-configure-landing-page.png
 :alt: Configure space-level landing page
-:class: screenshot
+:screenshot:
 :::

deploy-manage/monitor/monitoring-data/beats-page.md

@@ -19,7 +19,7 @@ If you are monitoring Beats, the **Stack Monitoring** page in {{kib}} contains a
 
 :::{image} ../../../images/kibana-monitoring-beats.png
 :alt: Monitoring Beats
-:class: screenshot
+:screenshot:
 :::
 
 To view an overview of the Beats data in the cluster, click **Overview**. The overview page has a section for activity in the last day, which is a real-time sample of data. The summary bar and charts follow the typical paradigm of data in the Monitoring UI, which is bound to the span of the time filter. This overview page can therefore show up-to-date or historical information.
@@ -28,7 +28,7 @@ To view a listing of the individual Beat instances in the cluster, click **Beats
 
 :::{image} ../../../images/kibana-monitoring-beats-detail.png
 :alt: Monitoring details for Filebeat
-:class: screenshot
+:screenshot:
 :::
 
 The detail page contains a summary bar and charts. There are more charts on this page than the overview page and they are specific to a single Beat instance.

deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md

@@ -19,7 +19,7 @@ You can drill down into the status of your {{es}} cluster in {{kib}} by clicking
 
 :::{image} ../../../images/kibana-monitoring-elasticsearch.png
 :alt: Monitoring clusters
-:class: screenshot
+:screenshot:
 :::
 
 For more information, refer to [Monitor a cluster](../../monitor.md).
@@ -38,7 +38,7 @@ The panel at the top shows the current cluster statistics, the charts show the s
 
 :::{image} ../../../images/kibana-monitoring-overview.png
 :alt: Elasticsearch Cluster Overview
-:class: screenshot
+:screenshot:
 :::
 
 ::::{tip}

deploy-manage/monitor/monitoring-data/kibana-alerts.md

@@ -17,7 +17,7 @@ The {{stack}} {{monitor-features}} provide [Alerting rules](../../../explore-ana
 
 :::{image} ../../../images/kibana-monitoring-kibana-alerting-notification.png
 :alt: {{kib}} alerting notifications in {{stack-monitor-app}}
-:class: screenshot
+:screenshot:
 :::
 
 When you open **{{stack-monitor-app}}** for the first time, you will be asked to acknowledge the creation of these default rules. They are initially configured to detect and notify on various conditions across your monitored clusters. You can view notifications for: **Cluster health**, **Resource utilization**, and **Errors and exceptions** for {{es}} in real time.

deploy-manage/monitor/monitoring-data/kibana-page.md

@@ -19,7 +19,7 @@ To view the key metrics that indicate the overall health of {{kib}} itself, clic
 
 :::{image} ../../../images/kibana-monitoring-kibana-overview.png
 :alt: Kibana Overview
-:class: screenshot
+:screenshot:
 :::
 
 1. To view {{kib}} instance metrics, click **Instances**.

deploy-manage/monitor/monitoring-data/logstash-page.md

@@ -19,7 +19,7 @@ If you are monitoring Logstash nodes, click **Overview** in the Logstash section
 
 :::{image} ../../../images/kibana-monitoring-logstash-overview.png
 :alt: Logstash Overview
-:class: screenshot
+:screenshot:
 :::
 
 1. To view Logstash node metrics, click **Nodes**. The Nodes section shows the status of each Logstash node.

deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md

@@ -73,7 +73,7 @@ You’ll see cluster alerts that require your attention and a summary of the ava
 
 :::{image} ../../../images/kibana-monitoring-dashboard.png
 :alt: Monitoring dashboard
-:class: screenshot
+:screenshot:
 :::
 
 If you encounter problems, see [Troubleshooting monitoring](../monitoring-data/monitor-troubleshooting.md).

deploy-manage/remote-clusters/ec-migrate-ccs.md

@@ -27,7 +27,7 @@ You can use a PUT request to update your deployment, changing both the deploymen
 
    :::{image} ../../images/cloud-ec-migrate-deployment-template(2).png
    :alt: Deployment Template ID
-   :class: screenshot
+   :screenshot:
    :::
 
 2. Make a request to update your deployment with two changes:
@@ -273,7 +273,7 @@ You can make this change in the user [{{ecloud}} Console](https://cloud.elastic.
 
     :::{image} ../../images/cloud-ec-create-from-snapshot-updated.png
     :alt: Create a Deployment using a snapshot
-    :class: screenshot
+    :screenshot:
     :::
 
 

deploy-manage/remote-clusters/ec-remote-cluster-ece.md

@@ -209,7 +209,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md

@@ -147,7 +147,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md

@@ -85,7 +85,7 @@ By default, any deployment that you create trusts all other deployments in the s
 
 :::{image} ../../images/cloud-ec-account-trust-management.png
 :alt: Trust management at the account Level
-:class: screenshot
+:screenshot:
 :::
 
 ::::{note}
@@ -183,7 +183,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md

@@ -235,7 +235,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ece-migrate-ccs.md

@@ -24,7 +24,7 @@ You can make this change in the user Cloud UI. The only drawback of this method
 
    :::{image} ../../images/cloud-enterprise-ce-create-from-snapshot-updated.png
    :alt: Create a Deployment using a snapshot
-   :class: screenshot
+   :screenshot:
    :::
 
 4. Finally, [configure the remote clusters](/deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md).

deploy-manage/remote-clusters/ece-remote-cluster-ece-ess.md

@@ -154,7 +154,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md

@@ -226,7 +226,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md

@@ -84,7 +84,7 @@ By default, any deployment that you or your users create trusts all other deploy
 
 :::{image} ../../images/cloud-enterprise-ce-environment-trust-management.png
 :alt: Trust management at the environment Level
-:class: screenshot
+:screenshot:
 :::
 
 ::::{note}
@@ -182,7 +182,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/remote-clusters/ece-remote-cluster-self-managed.md

@@ -233,7 +233,7 @@ On the local cluster, add the remote cluster using {{kib}} or the {{es}} API.
 
       :::{image} ../../images/cloud-enterprise-ce-copy-remote-cluster-parameters.png
       :alt: Remote Cluster Parameters in Deployment
-      :class: screenshot
+      :screenshot:
       :::
 
       ::::{note}

deploy-manage/tools/cross-cluster-replication/ccr-getting-started-auto-follow.md

@@ -28,7 +28,7 @@ As new indices matching these patterns are created on the remote, {{es}} automat
 
 :::{image} ../../../images/elasticsearch-reference-auto-follow-patterns.png
 :alt: The Auto-follow patterns page in {{kib}}
-:class: screenshot
+:screenshot:
 :::
 
 ::::{dropdown} API example

deploy-manage/tools/cross-cluster-replication/ccr-getting-started-follower-index.md

@@ -27,7 +27,7 @@ When you index documents into your leader index, {{es}} replicates the documents
 
 :::{image} ../../../images/elasticsearch-reference-ccr-follower-index.png
 :alt: The Cross-Cluster Replication page in {{kib}}
-:class: screenshot
+:screenshot:
 :::
 
 ::::{dropdown} API example

deploy-manage/users-roles/cluster-or-deployment-auth/access-agreement.md

@@ -39,6 +39,6 @@ When you authenticate using `basic.basic1`, you’ll see the following agreement
 
 :::{image} ../../../images/kibana-access-agreement.png
 :alt: Access Agreement UI
-:class: screenshot
+:screenshot:
 :::
 

deploy-manage/users-roles/cluster-or-deployment-auth/kibana-authentication.md

@@ -68,7 +68,7 @@ xpack.security.authc.providers:
 
 :::{image} ../../../images/kibana-kibana-login.png
 :alt: Login Selector UI
-:class: screenshot
+:screenshot:
 :::
 
 For more information, refer to [authentication security settings](kibana://reference/configuration-reference/security-settings.md#authentication-security-settings).

deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md

@@ -33,7 +33,7 @@ From the role management screen:
 
 :::{image} ../../../images/kibana-assign-base-privilege.png
 :alt: Assign base privilege
-:class: screenshot
+:screenshot:
 :::
 
 Using the [role APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-roles):
@@ -78,7 +78,7 @@ From the role management screen:
 
 :::{image} ../../../images/kibana-assign-subfeature-privilege.png
 :alt: Assign feature privilege
-:class: screenshot
+:screenshot:
 :::
 
 Using the [role APIs](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-roles):