docs: nav updates for alerting (#65300)

* navigation related updates - text only

* navigation related updates

* navigation related text updates

* navigation related text updates

* navigation related text and image updates

docs/sources/alerting/alerting-rules/create-grafana-managed-rule.md

@@ -20,31 +20,32 @@ Watch this video to learn more about creating alerts: {{< vimeo 720001934 >}}
 
 ## Add Grafana managed rule
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-1. Click **Create alert rule**. The new alerting rule page opens where the Grafana managed alerts option is selected by default.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules**.
+1. Click **+ Create alert rule**. The new alerting rule page opens where the **Grafana managed alerts** option is selected by default.
 1. In Step 1, add the rule name.
    - In **Rule name**, add a descriptive name. This name is displayed in the alert rule list. It is also the `alertname` label for every alert instance that is created from this rule.
 1. In Step 2, add queries and expressions to evaluate, and then select the alert condition.
-   - For queries, select a data source from the drop-down.
+   - For queries, select a data source from the dropdown.
    - Add one or more [queries]({{< relref "/docs/grafana/latest/panels-visualizations/query-transform-data#add-a-query" >}}) or [expressions]({{< relref "/docs/grafana/latest/panels-visualizations/query-transform-data/expression-queries" >}}).
-   - For each expression, select either **Classic condition** to create a single alert rule, or choose from **Math**, **Reduce**, **Resample** options to generate separate alert for each series. For details on these options, see [Single and multi dimensional rule](#single-and-multi-dimensional-rule).
+   - For each expression, select either **Classic condition** to create a single alert rule, or choose from the **Math**, **Reduce**, and **Resample** options to generate separate alert for each series. For details on these options, see [Single and multi dimensional rule](#single-and-multi-dimensional-rule).
    - Click **Run queries** to verify that the query is successful.
    - Next, select the query or expression for your alert condition.
 1. In Step 3, specify the alert evaluation interval.
 
-   - From the **Condition** drop-down, select the query or expression to trigger the alert rule.
+   - From the **Condition** dropdown, select the query or expression to trigger the alert rule.
    - For **Evaluate every**, specify the frequency of evaluation. Must be a multiple of 10 seconds. For examples, `1m`, `30s`.
    - For **Evaluate for**, specify the duration for which the condition must be true before an alert fires.
      > **Note:** Once a condition is breached, the alert goes into the Pending state. If the condition remains breached for the duration specified, the alert transitions to the `Firing` state, otherwise it reverts back to the `Normal` state.
    - In **Configure no data and error handling**, configure alerting behavior in the absence of data. Use the guidelines in [No data and error handling](#no-data-and-error-handling).
-   - Click **Preview alerts** to check the result of running the query at this moment. Preview excludes no data and error handling.
+   - Click **Preview** to check the result of running the query at this moment. Preview excludes no data and error handling.
 
      **Note:**
 
      You can pause alert rule evaluation to prevent noisy alerting while tuning your alerts. Pausing stops alert rule evaluation and does not create any alert instances. This is different to mute timings, which stop notifications from being delivered, but still allow for alert rule evaluation and the creation of alert instances.
 
 1. In Step 4, add the storage location, rule group, as well as additional metadata associated with the rule.
-   - From the **Folder** drop-down, select the folder where you want to store the rule.
+   - From the **Folder** dropdown, select the folder where you want to store the rule.
    - For **Group**, specify a pre-defined group. Newly created rules are appended to the end of the group. Rules within a group are run sequentially at a regular interval, with the same evaluation time.
    - Add a description and summary to customize alert messages. Use the guidelines in [Annotations and labels for alerting]({{< relref "../fundamentals/annotation-label/" >}}).
    - Add Runbook URL, panel, dashboard, and alert IDs.

docs/sources/alerting/alerting-rules/create-mimir-loki-managed-recording-rule.md

@@ -34,33 +34,37 @@ You can create and manage recording rules for an external Grafana Mimir or Loki
 
 To create a Grafana Mimir or Loki managed recording rule
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-1. Click **Create alert rule**. The new alerting rule page opens where the **Grafana managed alert** option is selected by default.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules**.
+1. Click **+ Create alert rule**. The new alerting rule page opens where the **Grafana managed alert** option is selected by default.
 1. In Step 1, add the rule name. The recording name must be a Prometheus metric name and contain no whitespace.
    - In **Rule name**, add a descriptive name.
 1. In Step 2, select **Mimir or Loki recording rule** option.
    - Select your Loki or Prometheus data source.
    - Enter a PromQL or LogQL query.
 1. In Step 3, add the namespace and the group.
-   - From the **Namespace** drop-down, select an existing rule namespace. Otherwise, click Add new and enter a name to create a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. For more information, see [Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}}).
-   - From the **Group** drop-down, select an existing group within the selected namespace. Otherwise, click **Add new** and enter a name to create a new one.
+   - From the **Namespace** dropdown, select an existing rule namespace. Otherwise, click Add new and enter a name to create a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. For more information, see [Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}}).
+   - From the **Group** dropdown, select an existing group within the selected namespace. Otherwise, click **Add new** and enter a name to create a new one.
 1. In Step 4, add the custom labels.
    - Add custom labels selecting existing key-value pairs from the drop down, or add new labels by entering the new key or value.
 1. Click **Save** to save the recording rule or **Save and exit** to save the recording rule and go back to the Alerting page.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-1. Click **Create alert rule**.
+<!-- delete next steps? -->
+
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules**.
+1. Click **+ Create alert rule**.
 1. In Step 1, add the rule name.
    - In **Rule name**, add a descriptive name. This name is displayed in the alert rule list. It is also the `alertname` label for every alert instance that is created from this rule.
 1. In Step 2, add the type, and storage location.
-   - From the **Rule type** drop-down, select **Mimir / Loki managed alert**.
-   - From the **Select data source** drop-down, select an external Prometheus, an external Loki, or a Grafana Cloud data source.
+   - From the **Rule type** dropdown, select **Mimir / Loki managed alert**.
+   - From the **Select data source** dropdown, select an external Prometheus, an external Loki, or a Grafana Cloud data source.
    - Enter a PromQL or LogQL expression. The rule fires if the evaluation result has at least one series with a value that is greater than 0. An alert is created for each series.
 1. In Step 3, add evaluation behavior.
    - Enter a valid **For** duration. The expression has to be true for this long for the alert to be fired.
 1. In Step 4, add additional metadata associated with the rule.
-   - From the **Namespace** drop-down, select an existing rule namespace. Otherwise, click Add new and enter a name to create a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. For more information, see [Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}}).
-   - From the **Group** drop-down, select an existing group within the selected namespace. Otherwise, click **Add new** and enter a name to create a new one. Newly created rules are appended to the end of the group. Rules within a group are run sequentially at a regular interval, with the same evaluation time.
+   - From the **Namespace** dropdown, select an existing rule namespace. Otherwise, click Add new and enter a name to create a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. For more information, see [Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}}).
+   - From the **Group** dropdown, select an existing group within the selected namespace. Otherwise, click **Add new** and enter a name to create a new one. Newly created rules are appended to the end of the group. Rules within a group are run sequentially at a regular interval, with the same evaluation time.
    - Add a description and summary to customize alert messages. Use the guidelines in [Annotations and labels for alerting]({{< relref "../fundamentals/annotation-label/" >}}).
    - Add Runbook URL, panel, dashboard, and alert IDs.
 1. In Step 5, add custom labels.

docs/sources/alerting/alerting-rules/create-mimir-loki-managed-rule.md

@@ -34,8 +34,9 @@ Watch this video to learn more about how to create a Mimir managed alert rule: {
 
 ## Add a Grafana Mimir or Loki managed alerting rule
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-1. Click **Create alert rule**. The new alerting rule page opens where the Grafana managed alerts option is selected by default.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules**.
+1. Click **+ Create alert rule**. The new alerting rule page opens where the **Grafana managed alerts** option is selected by default.
 1. In Step 1, add the rule name.
    - In **Rule name**, add a descriptive name. This name is displayed in the alert rule list. It is also the `alertname` label for every alert instance that is created from this rule.
 1. In Step 2, select **Mimir or Loki alert** option.
@@ -45,8 +46,8 @@ Watch this video to learn more about how to create a Mimir managed alert rule: {
    - In the **For** text box, specify the duration for which the condition must be true before an alert fires. If you specify `5m`, the condition must be true for 5 minutes before the alert fires.
      > **Note:** Once a condition is met, the alert goes into the `Pending` state. If the condition remains active for the duration specified, the alert transitions to the `Firing` state, else it reverts to the `Normal` state.
 1. In Step 4, add the namespace, rule group, as well as additional metadata associated with the rule.
-   - From the **Namespace** drop-down, select an existing rule namespace. Otherwise, click **Add new** and enter a name to create a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. For more information, see [Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}}).
-   - From the **Group** drop-down, select an existing group within the selected namespace. Otherwise, click **Add new** and enter a name to create a new one. Newly created rules are appended to the end of the group. Rules within a group are run sequentially at a regular interval, with the same evaluation time.
+   - From the **Namespace** dropdown, select an existing rule namespace. Otherwise, click **Add new** and enter a name to create a new one. Namespaces can contain one or more rule groups and only have an organizational purpose. For more information, see [Grafana Mimir or Loki rule groups and namespaces]({{< relref "edit-mimir-loki-namespace-group/" >}}).
+   - From the **Group** dropdown, select an existing group within the selected namespace. Otherwise, click **Add new** and enter a name to create a new one. Newly created rules are appended to the end of the group. Rules within a group are run sequentially at a regular interval, with the same evaluation time.
    - Add a description and summary to customize alert messages. Use the guidelines in [Annotations and labels for alerting]({{< relref "../fundamentals/annotation-label/" >}}).
    - Add Runbook URL, panel, dashboard, and alert IDs.
 1. In Step 5, add custom labels.

docs/sources/alerting/alerting-rules/edit-mimir-loki-namespace-group.md

@@ -19,15 +19,18 @@ weight: 405
 
 A namespace contains one or more groups. The rules within a group are run sequentially at a regular interval. The default interval is one (1) minute. You can rename Grafana Mimir or Loki rule namespaces and groups, and edit group evaluation intervals.
 
-![Group list](/static/img/docs/alerting/unified/rule-list-edit-mimir-loki-icon-8-2.png 'Rule group list screenshot')
+{{< figure src="/static/img/docs/alerting/unified/rule-list-edit-mimir-loki-icon-8-2.png" caption="Rule group list" alt="Group list" >}}
 
+<!-- image is the same as above
 {{< figure src="/static/img/docs/alerting/unified/rule-list-edit-mimir-loki-icon-8-2.png" max-width="550px" caption="Alert details" >}}
+-->
 
 ## Rename a namespace
 
 To rename a namespace:
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules** to view the list of existing alerts.
 1. Find a Grafana Mimir or Loki managed rule with the group that belongs to the namespace you want to edit.
 1. Click the **Edit** (pen) icon.
 1. Enter a new name in the **Namespace** field, then click **Save changes**.
@@ -38,7 +41,8 @@ A new namespace is created and all groups are copied into this namespace from th
 
 The rules within a group are run sequentially at a regular interval, the default interval is one (1) minute. You can modify this interval using the following instructions.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the left-side menu, click the **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules** to view the list of existing alerts.
 1. Find a Grafana Mimir or Loki managed rule with the group you want to edit.
 1. Click **Edit** (pen) icon.
 1. Modify the **Rule group** and **Rule group evaluation interval** information as necessary.
@@ -47,3 +51,7 @@ The rules within a group are run sequentially at a regular interval, the default
 When you rename the group, a new group with all the rules from the old group is created. The old group is deleted.
 
 ![Group edit modal](/static/img/docs/alerting/unified/rule-list-mimir-loki-edit-ns-group-8-2.png 'Rule group edit modal screenshot')
+
+<!-- new image that displays current 9.4 state of modal below
+{{< figure src="/media/docs/grafana/alerting/screenshot-rule-list-mimir-loki-edit-ns-group-9-4.png" max-width="550px" caption="Rule group edit modal" alt="Group edit modal" >}}
+-->

docs/sources/alerting/alerting-rules/view-state-health.md

@@ -22,8 +22,9 @@ There are three key components: [alert rule state](#alert-rule-state), [alert in
 
 To view the state and health of your alert rules:
 
-1. Navigate to Alerting > Alert rules.
-2. Click an alert rule to view its state, health and state history.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Alert rules** to view the list of existing alerts.
+1. Click an alert rule to view its state, health, and state history.
 
 ## Alert rule state
 

docs/sources/alerting/manage-notifications/create-contact-point.md

@@ -22,10 +22,10 @@ Use contact points to define how your contacts are notified when an alert rule f
 
 Complete the following steps to add a contact point.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-1. Click **Contact points** to open the page listing existing contact points.
-1. Click **Add contact point**.
-1. From the **Alertmanager** dropdown, select an Alertmanager. By default, Grafana Alertmanager is selected.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Contact points**.
+1. Click **+ Add contact point**.
+1. From the **Alertmanager** dropdown, select an Alertmanager. By default, **Grafana Alertmanager** is selected.
 1. In **Name**, enter a descriptive name for the contact point.
 1. From **Contact point integration**, select a type and fill out mandatory fields. For example, if you choose email, enter the email addresses. Or if you choose Slack, enter the Slack channel(s) and users who should be contacted.
 1. Some contact point integrations, like email or webhook, have optional settings. In **Optional settings**, specify additional settings for the selected contact point integration.
@@ -37,16 +37,18 @@ Complete the following steps to add a contact point.
 
 Complete the following steps to edit a contact point.
 
-1. In the Alerting page, click **Contact points** to open the page listing existing contact points.
-1. Find the contact point to edit, then click **Edit** (pen icon).
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Contact points** to view a list of existing contact points.
+1. Find the contact point to edit, and then click **Edit** (pen icon).
 1. Make any changes and click **Save contact point**.
 
 ## Delete a contact point
 
 Complete the following steps to delete a contact point.
 
-1. In the Alerting page, click **Contact points** to open the page listing existing contact points.
-1. Find the contact point to delete, then click **Delete** (trash icon).
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Contact points** to view a list of existing contact points.
+1. Find the contact point to delete, and then click **Delete** (trash icon).
 1. In the confirmation dialog, click **Yes, delete**.
 
 > **Note:** You cannot delete contact points that are in use by a notification policy. You will have to either delete the notification policy or update it to use another contact point.
@@ -55,8 +57,9 @@ Complete the following steps to delete a contact point.
 
 Complete the following steps to test a contact point.
 
-1. In the Grafana side bar, hover your cursor over the **Alerting** (bell) icon and then click **Contact** points.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Contact points** to view a list of existing contact points.
 1. Find the contact point to test, then click **Edit** (pen icon). You can also create a new contact point if needed.
-1. Click **Test** (paper airplane icon) to open the contact point testing modal.
+1. Click **Test** to open the contact point testing modal.
 1. Choose whether to send a predefined test notification or choose custom to add your own custom annotations and labels to include in the notification.
 1. Click **Send test notification** to fire the alert.

docs/sources/alerting/manage-notifications/create-notification-policy.md

@@ -16,7 +16,7 @@ weight: 300
 
 # Manage notification policies
 
-Notification policies determine how alerts are routed to contact points. Policies have a tree structure, where each policy can have one or more nested policies. Each policy, except for the default policy, can also match specific alert labels. Each alert is evaluated by the default policy and subsequently by each nested policy. If the `Continue matching subsequent sibling nodes` option is enabled for a nested policy, then evaluation continues even after one or more matches. A parent policy’s configuration settings and contact point information govern the behavior of an alert that does not match any of the nested policies. A default policy governs any alert that does not match a nested policy.
+Notification policies determine how alerts are routed to contact points. Policies have a tree structure, where each policy can have one or more nested policies. Each policy, except for the default policy, can also match specific alert labels. Each alert is evaluated by the default policy and subsequently by each nested policy. If the **Continue matching subsequent sibling nodes** option is enabled for a nested policy, then evaluation continues even after one or more matches. A parent policy’s configuration settings and contact point information govern the behavior of an alert that does not match any of the nested policies. A default policy governs any alert that does not match a nested policy.
 
 You can configure Grafana managed notification policies as well as notification policies for an external Alertmanager data source.
 
@@ -36,10 +36,10 @@ You can configure grouping to be `group_by: [alertname]` (take note that the `en
 
 > **Note:** Before Grafana v8.2, the configuration of the embedded Alertmanager was shared across organizations. Users of Grafana 8.0 and 8.1 are advised to use the new Grafana 8 Alerts only if they have one organization. Otherwise, silences for the Grafana managed alerts will be visible by all organizations.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
 1. Click **Notification policies**.
-1. From the **Alertmanager** dropdown, select an external Alertmanager. By default, the Grafana Alertmanager is selected.
-1. In the Default policy section, click **...** › **Edit** (pen icon).
+1. From the **Choose Alertmanager** dropdown, select an external Alertmanager. By default, the **Grafana Alertmanager** is selected.
+1. In the Root policy section, click **Edit**.
 1. In **Default contact point**, update the contact point to whom notifications should be sent for rules when alert rules do not match any specific policy.
 1. In **Group by**, choose labels to group alerts by. If multiple alerts are matched for this policy, then they are grouped by these labels. A notification is sent per group. If the field is empty (default), then all notifications are sent in a single group. Use a special label `...` to group alerts by all labels (which effectively disables grouping).
 1. In **Timing options**, select from the following options:
@@ -50,12 +50,12 @@ You can configure grouping to be `group_by: [alertname]` (take note that the `en
 
 ## Add new nested policy
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
 1. Click **Notification policies**.
-1. From the **Alertmanager** dropdown, select an Alertmanager. By default, the Grafana Alertmanager is selected.
-1. To add a top level specific policy, go to the **Specific routing** section and click **New specific policy**.
-1. In **Matching labels** section, add one or more rules for matching alert labels.
-1. In **Contact point**, add the contact point to send notification to if alert matches only this specific policy and not any of the nested policies.
+1. From the **Choose Alertmanager** dropdown, select an Alertmanager. By default, the **Grafana Alertmanager** is selected.
+1. To add a top level specific policy, go to the Specific routing section and click **+ New specific policy**.
+1. In the Matching labels section, add one or more rules for matching alert labels.
+1. In the **Contact point** dropdown, select the contact point to send notification to if alert matches only this specific policy and not any of the nested policies.
 1. Optionally, enable **Continue matching subsequent sibling nodes** to continue matching sibling policies even after the alert matched the current policy. When this option is enabled, you can get more than one notification for one alert.
 1. Optionally, enable **Override grouping** to specify the same grouping as the default policy. If this option is not enabled, the default policy grouping is used.
 1. Optionally, enable **Override general timings** to override the timing options configured in the group notification policy.
@@ -63,14 +63,17 @@ You can configure grouping to be `group_by: [alertname]` (take note that the `en
 
 ## Add nested policy
 
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Notification policies**.
 1. Expand the specific policy you want to update.
-1. Click **Add nested policy**, then add the details using information in [Add new specific policy](#add-new-specific-policy).
+1. Click **+ Add nested policy**, then add the details using information in [Add new specific policy](#add-new-specific-policy).
 1. Click **Save policy** to save your changes.
 
 ## Edit specific policy
 
-1. In the Alerting page, click **Notification policies** to open the page listing existing policies.
-1. Find the policy you want to edit, then click **Edit** (pen icon).
+1. In the left-side menu, click **Alerts & incidents**, and then **Alerting**.
+1. Click **Notification policies**.
+1. Find the policy you want to edit, then click **Edit**.
 1. Make any changes using instructions in [Add new specific policy](#add-new-specific-policy).
 1. Click **Save policy**.
 

docs/sources/alerting/manage-notifications/create-silence.md

@@ -25,25 +25,24 @@ Silences stop notifications from getting created and last for only a specified w
 
 To add a silence, complete the following steps.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-2. On the Alerting page, click **Silences** to open the page listing existing silences.
-3. From Alertmanager drop-down, select an external Alertmanager to create and manage silences for the external data source. Otherwise, keep the default option of Grafana.
-4. Click **Add Silence** to open the Create silence page.
-5. In **Silence start and end**, select the start and end date to indicate when the silence should go into effect and expire.
-6. Optionally, in **Duration**, specify how long the silence is enforced. This automatically updates the end time in the **Silence start and end** field.
-7. In the **Name** and **Value** fields, enter one or more _Matching Labels_. Matchers determine which rules the silence will apply to.
-8. In **Comment**, add details about the silence.
-9. In **Creator**, enter the name of the silence owner or keep the default owner.
-10. Click **Create**.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Silences**.
+1. From the **Alertmanager** dropdown, select an external Alertmanager to create and manage silences for the external data source. Otherwise, keep the default option of Grafana.
+1. Click **Create silence** to open the Create silence page.
+1. In **Silence start and end**, select the start and end date to indicate when the silence should go into effect and expire.
+1. Optionally, in **Duration**, specify how long the silence is enforced. This automatically updates the end time in the **Silence start and end** field.
+1. In the **Label** and **Value** fields, enter one or more _Matching Labels_. Matchers determine which rules the silence will apply to.
+1. In **Comment**, add details about the silence.
+1. Click **Submit**.
 
 ## Edit silences
 
 To edit a silence, complete the following steps.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-2. Click **Silences** to view the list of existing silences.
-3. Find the silence you want to edit, then click **Edit** (pen icon).
-4. Make the desired changes, then click **Submit** to save your changes.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Silences** to view the list of existing silences.
+1. Find the silence you want to edit, then click **Edit** (pen icon).
+1. Make the desired changes, then click **Submit** to save your changes.
 
 ## Create a URL to link to a silence form
 
@@ -57,7 +56,7 @@ To link to a new silence page for an external Alertmanager, add a `alertmanager`
 
 To remove a silence, complete the following steps.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
 1. Click **Silences** to view the list of existing silences.
 1. Select the silence you want to end, then click **Unsilence**.
 

docs/sources/alerting/manage-notifications/mute-timings.md

@@ -33,19 +33,21 @@ The following table highlights the key differences between mute timings and sile
 
 ## Create a mute timing
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
+1. In the left-side menu, click **Alerts & incidents**, and then **Alerting**.
 1. Click **Notification policies**.
-1. From the **Alertmanager** dropdown, select an external Alertmanager. By default, the Grafana Alertmanager is selected.
-1. Click the **Mute Timings** tab.
-1. Click **Add mute timing**.
-1. You will be redirected to a form to create a [time interval](#time-intervals) to match against for your mute timing.
+1. From the **Alertmanager** dropdown, select an external Alertmanager. By default, the **Grafana Alertmanager** is selected.
+1. Scroll down to the Mute timings section.
+1. Click **+ Add mute timing**.
+1. Fill out the form to create a [time interval](#time-intervals) to match against for your mute timing.
 1. Click **Submit** to create the mute timing.
 
 ## Add mute timing to a notification policy
 
+1. In the left-side menu, click **Alerts & incidents**, and then **Alerting**.
+1. Click **Notification policies**.
 1. Identify the notification policy you would like to add the mute timing to and click the **Edit** button for that policy.
-1. From the Mute Timings dropdown select the mute timings you would like to add to the route.
-1. Click the **Save policy** button to save.
+1. In the Specific routing section, from the **Mute timings** dropdown, select the mute timings you would like to add to the route.
+1. Click **Save policy**.
 
 ## Time intervals
 

docs/sources/alerting/manage-notifications/view-alert-groups.md

@@ -25,10 +25,10 @@ You can view alert groups and also filter for alert rules that match specific cr
 
 To view alert groups, complete the following steps.
 
-1. In the Grafana menu, click the **Alerting** (bell) icon to open the Alerting page listing existing alerts.
-1. Click **Alert groups** to open the page listing existing groups.
-1. From the **Alertmanager** drop-down, select an external Alertmanager as your data source. By default, the `Grafana` Alertmanager is selected.
-1. From **custom group by** drop-down, select a combination of labels to view a grouping other than the default. This is useful for debugging and verifying your grouping of notification policies.
+1. In the left-side menu, click **Alerts & incidents** and then **Alerting**.
+1. Click **Groups** to view the list of existing groups.
+1. From the **Alertmanager** dropdown, select an external Alertmanager as your data source. By default, the `Grafana` Alertmanager is selected.
+1. From **Custom group by** dropdown, select a combination of labels to view a grouping other than the default. This is useful for debugging and verifying your grouping of notification policies.
 
 If an alert does not contain labels specified either in the grouping of the default policy or the custom grouping, then the alert is added to a catch all group with a header of `No grouping`.
 

docs/sources/alerting/set-up/configure-alertmanager/index.md

@@ -25,12 +25,16 @@ External alertmanagers should now be configured as data sources using Grafana Co
 
 To add an external Alertmanager, complete the following steps.
 
-1. Click Configuration and then Data sources.
-1. Search for Alertmanager.
-1. Choose your Implementation and fill out the fields on the page, as required.
+1. Click **Connections** in the left-side menu.
+1. On the Connections page, search for `Alertmanager`.
+1. Click the **Create a new data source** button.
+
+   If you don't see this button, you may need to install the plugin, relaunch your Cloud instance, and then repeat steps 1 and 2.
+
+1. Fill out the fields on the page, as required.
 
    If you are provisioning your data source, set the flag `handleGrafanaManagedAlerts` in the `jsonData` field to `true` to send Grafana-managed alerts to this Alertmanager.
 
    **Note:**: Prometheus, Grafana Mimir, and Cortex implementations of Alertmanager are supported. For Prometheus, contact points and notification policies are read-only in the Grafana Alerting UI.
 
-1. Click Save & test.
+1. Click **Save & test**.