update screenshots of actions, update outdated ui references (#2089)

elastic · Aug 18, 2022 · 436b29e · 436b29e
1 parent 2350c5d
commit 436b29e
Show file tree

Hide file tree

Showing 7 changed files with 19 additions and 19 deletions.
diff --git a/docs/en/observability/images/alert-action-types.png b/docs/en/observability/images/alert-action-types.png
diff --git a/docs/en/observability/infrastructure-threshold-alert.asciidoc b/docs/en/observability/infrastructure-threshold-alert.asciidoc
@@ -8,8 +8,8 @@ resource or a group of resources within your infrastructure.
 Additionally, each rule can be defined using multiple
 conditions that combine metrics and thresholds to create precise notifications and reduce false positives.
 
-. To access this page, go to *{observability} > Metrics*.
-. On the *Inventory* page or the *Metrics Explorer* page, click *Alerts > Infrastructure*.
+. To access this page, go to **{observability}** -> **Metrics**.
+. On the *Inventory* page or the *Metrics Explorer* page, click **Alerts and rules** -> **Infrastructure**.
 . Select *Create inventory alert*.
 
 [TIP]

diff --git a/docs/en/observability/logs-threshold-alert.asciidoc b/docs/en/observability/logs-threshold-alert.asciidoc
@@ -1,8 +1,8 @@
 [[logs-threshold-alert]]
 = Create a logs threshold rule
 
-. To access this page, go to *{observability} > Logs*.
-. Click *Alerts > Create alert*.
+. To access this page, go to **{observability}** -> **Logs**.
+. Click **Alerts and rules** -> **Create alert**.
 
 [role="screenshot"]
 image::images/log-threshold-alert.png[Log threshold alert configuration]

diff --git a/docs/en/observability/metrics-threshold-alert.asciidoc b/docs/en/observability/metrics-threshold-alert.asciidoc
@@ -1,25 +1,25 @@
 [[metrics-threshold-alert]]
 = Create a metrics threshold rule
 
-Based on the metrics that are listed on the *Metrics Explorer* page within the {metrics-app},
+Based on the metrics that are listed on the **Metrics Explorer** page within the {metrics-app},
 you can create a threshold rule to notify you when a metric has reached or exceeded a value for a specific
 time period.
 
 Additionally, each rule can be defined using multiple
 conditions that combine metrics and thresholds to create precise notifications.
 
-. To access this page, go to *{observability} > Metrics*.
-. On the *Inventory* page or the *Metrics Explorer* page, click *Alerts > Metrics*.
-. Select *Create threshold alert*.
+. To access this page, go to **{observability}** -> **Metrics**.
+. On the **Inventory** page or the **Metrics Explorer** page, click **Alerts and rules** -> **Metrics**.
+. Select **Create threshold alert**.
 
 [TIP]
 =====
 When you select *Create threshold alert*, the rule is automatically populated with the same parameters
 you've configured on the *Metrics Explorer* page. If you've chosen a *graph per* value, your rule is
 preconfigured to monitor and notify about each individual graph displayed on the page.
 
-You can also create a rule based on a single graph. On the *Metrics Explorer* page,
-click *Actions > Create alert*. The condition and filter sections of the threshold rule
+You can also create a rule based on a single graph. On the **Metrics Explorer** page,
+click **Alerts and rules** -> **Create alert**. The condition and filter sections of the threshold rule
 are automatically populated.
 =====
 

diff --git a/docs/en/observability/monitor-status-alert.asciidoc b/docs/en/observability/monitor-status-alert.asciidoc
@@ -1,12 +1,12 @@
 [[monitor-status-alert]]
 = Create a monitor status rule
 
-Within the {uptime-app}, create a *Monitor Status* rule to receive notifications
+Within the {uptime-app}, create a **Monitor Status** rule to receive notifications
 based on errors and outages. 
 
-. To access this page, go to *{observability} > Uptime*.
-. At the top of the page, click *Alerts and rules > Create rule*.
-. Select *Monitor status rule*.
+. To access this page, go to **{observability}** -> **Uptime**.
+. At the top of the page, click **Alerts and rules** -> **Create rule**.
+. Select **Monitor status rule**.
 
 [TIP]
 ===============================

diff --git a/docs/en/observability/uptime-duration-anomaly-alert.asciidoc b/docs/en/observability/uptime-duration-anomaly-alert.asciidoc
@@ -7,8 +7,8 @@ monitor runs for an unusual amount of time, at a particular time, an anomaly is
 highlighted on the <<inspect-uptime-duration-anomalies,Monitor duration>> chart.
 
 // lint ignore anomaly-detection
-. To access this page, go to *{observability} > Uptime*.
-. On the *Monitors* page, select on a monitor, and then click *Enable anomaly detection*.
+. To access this page, go to **{observability}** -> **Uptime**.
+. On the *Monitors* page, select on a monitor, and then click **Enable anomaly detection**.
 
 [discrete]
 [[duration-alert-conditions]]

diff --git a/docs/en/observability/uptime-tls-alert.asciidoc b/docs/en/observability/uptime-tls-alert.asciidoc
@@ -5,9 +5,9 @@ Within the {uptime-app}, you can create a rule that notifies
 you when one or more of your monitors has a TLS certificate expiring
 within a specified threshold, or when it exceeds an age limit.
 
-. To access this page, go to *{observability} > Uptime*.
-. At the top of the page, click *Alerts and rules > Create rule*.
-. Select *TLS rule*.
+. To access this page, go to **{observability}** -> **Uptime**.
+. At the top of the page, click **Alerts and rules** -> **Create rule**.
+. Select **TLS rule**.
 
 [discrete]
 [[tls-alert-conditions]]