remove destination creation

Author: wojcik-dorota

docs/products/opensearch/dashboards/howto/opensearch-alerting-dashboard.md

@@ -6,16 +6,15 @@ sidebar_label: Create alerts
 import RelatedPages from "@site/src/components/RelatedPages";
 
 OpenSearch® alerting feature sends notifications when data from one or more indices meets certain conditions that can be customized.
-Use case
-examples are such as monitoring for HTTP status code 503, CPU load
-average above certain percentage or watch for counts of a specific
-keyword in logs for a specific amount of interval, notification to be
-configured to be sent via email, slack or custom webhooks and other
-destination.
-
-In the following example we are using Slack as the destination and a
+Use case examples include monitoring for HTTP status code 503, CPU load
+average above a certain percentage, or watching for counts of a specific
+keyword in logs for a specific interval. Notifications can be
+configured to be sent via email, Slack, or custom webhooks and other
+channels.
+
+In the following example, we use Slack as the notification channel and a
 `sample-host-health` index as datasource to create a simple alert to
-check cpu load. An action will be triggered when average of
+check CPU load. An action will be triggered when the average of
 `cpu_usage_percentage` over `3` minutes is above `75%`.
 
 ## Create using Dashboards UI
@@ -26,54 +25,62 @@ To create an alert via OpenSearch Dashboards interface:
     your OpenSearch service.
 
 1.  On the service's **Overview** screen, in the **Connection
-    information** section and select the **OpenSearch Dashboards** tab.
+    information** section, select the **OpenSearch Dashboards** tab.
 
-    This opens the OpenSearch Dashboard
+    This opens the OpenSearch Dashboard.
 
 1.  Within the OpenSearch Dashboard, access the left side panel and
     select **Alerting** under the OpenSearch Plugins section.
 
-To configure each alert the following needs to be created, we will
-walk-through configuration of each section.
+To configure each alert, the following needs to be created. We will
+walk through the configuration of each section:
 
--   `Destination`
+-   `Notification channel`
 -   `Monitor`
 -   `Data source`
 -   `Query`
 -   `Trigger`
 
-## Create a destination
+## Create a notification channel
 
-Destination is a location for notifications to be delivered when an
+A notification channel is a location for notifications to be delivered when an
 action is triggered.
 
-1.  Open the **Destination** tab and click **Add destination**
+1.  In the OpenSearch Dashboard, select **Notifications** from the left side panel.
+
+1.  Select the **Channels** tab and click **Create channel**.
+
+1.  Fill in the fields under **Channel details**.
 
-1.  Fill in the fields under **Destination**.
     Fill `slack-test` as the **Name**.
-    Select `Slack` under **Type**.
 
-    Paste your slack webhook `https://your_slack_webhook_URL` under
+    Provide a description (optional).
+
+    Select `Slack` under **Channel type**.
+
+    Paste your Slack webhook URL `https://your_slack_webhook_URL` under
     **Webhook URL**.
 
+1.  Click **Create**.
+
 :::note
-Destination Type can be: `Amazon Chime`, `Slack`, `Custom webhook` or
-`Email`
+Channel types can be: `Amazon Chime`, `Amazon SNS`, `Slack`, `Custom webhook`, `Email`,
+or `Microsoft Teams`.
 :::
 
 :::important
 When using email, ensure you have an SMTP server configured for a
 valid domain to deliver email notifications.
 :::
 
-## Configure authentication for email destination
+## Configure authentication for email channel
 
 This section shows how to authenticate the sender account before sending
 email messages. To authenticate when sending emails, the credentials
 need to be added first to the OpenSearch keystore. Perform this step
-before configuring an email destination that requires authentication.
+before configuring an email channel that requires authentication.
 
-1.  In **Overview** screen of your OpenSearch service, scroll to the
+1.  In the **Overview** screen of your OpenSearch service, scroll to the
     **Advanced configuration** section.
 
 1.  Select **Change** and **+Add configuration option**.
@@ -85,36 +92,40 @@ before configuring an email destination that requires authentication.
     -   `email_sender_username`
     -   `email_sender_password`
 
-    At the end of this step the email account credentials will be added
+    At the end of this step, the email account credentials will be added
     to the OpenSearch keystore.
 
+1.  Select **Save advanced configuration**.
+
 In OpenSearch Dashboards:
 
-1.  Select **Save advanced configuration**.
+1.  Select **Notifications** from the left side panel.
 
-1.  Open the **Destination** tab in the OpenSearch Dashboard and select
-    **Add destination**.
+1.  Select the **Channels** tab and click **Create channel**.
 
-1.  Fill in the fields under **Destination**.
+1.  Fill in the fields under **Channel details**.
 
     Fill `email-test` as the **Name**.
 
-    Select `Email` under **Type**.
+    Select `Email` under **Channel type**.
 
-    We assume that no senders exist yet. Click **Manage Senders** > **New sender**.
+    Under **Email settings**, click **Manage senders** if no senders exist yet, then
+    select **Create sender**.
 
     Assign a name to the sender. This name should match the property `email_sender_name`
-    from step 1.
+    from the keystore configuration.
 
     Fill in the information required by the form and select SSL or TLS
     in **Encryption method**.
 
-1.  Complete the form with the recipients, by
-    creating email groups in **Manage email groups** if necessary.
+1.  Complete the form with the recipients. You can create email groups in
+    **Manage email groups** if necessary.
+
+1.  Click **Create**.
 
 ## Create a monitor
 
-Monitor is a job that runs on a defined schedule and queries OpenSearch
+A monitor is a job that runs on a defined schedule and queries OpenSearch
 indices.
 
 1.  Open the **Monitors** tab and click **Create monitor**.
@@ -129,36 +140,36 @@ indices.
 
     Select `By interval` under **Schedule** **Frequency**.
 
-    Under **Run every**, select `1` `Minutes`,
+    Under **Run every**, select `1` `Minutes`.
 
 :::note
-Schedule Frequency can be `By internal`, `Daily` `Weekly` `Monthly`,
+Schedule Frequency can be `By interval`, `Daily`, `Weekly`, `Monthly`, or
 `Custom CRON expression`.
 :::
 
 1.  Fill in the fields under **Data source**.
 
     Data source is the OpenSearch indices to query.
 
-    Fill `sample-host-health` into **index**.
+    Fill `sample-host-health` into **Index**.
 
     Fill `timestamp` into **Time field**.
 
-1.  **Query**
+1.  Configure the **Query**.
 
     Query defines the fields to query from indices and how to evaluate
     the results.
 
-    Under **Metrics** click **Add metric**.
+    Under **Metrics**, click **Add metric**.
 
     Select `average()` under **Aggregation** and `cpu_usage_percentage`
-    under **Field**, click **Save**.
+    under **Field**, then click **Save**.
 
     Fill `3` under **Time range for the last** and select `minutes`.
 
 ## Create a trigger
 
-Triggers is a defined conditions from the queries results from monitor.
+A trigger is a defined condition from the query results from the monitor.
 If conditions are met, alerts are generated.
 
 1.  Select **Add trigger**.
@@ -167,38 +178,39 @@ If conditions are met, alerts are generated.
 
     Select `1 (Highest)` for **Severity level**.
 
-    Under **Trigger condition** select `IS ABOVE` from the drop-down
+    Under **Trigger condition**, select `IS ABOVE` from the drop-down
     menu and fill `75` into the number field.
 
 :::note
-You can see a visual graph below trigger with the index data and the
+You can see a visual graph below the trigger with the index data and the
 trigger condition you have defined as a red line.
 :::
 
-1.  Fill in the fields under **Actions**
+1.  Fill in the fields under **Actions**.
 
-    Actions defines the destination for notification alerts when trigger
+    Actions define the notification channel for alerts when trigger
     conditions are met.
 
     Fill in `slack` as **Action name**.
 
-    Select `slack-test` under **Destination**.
+    Select `slack-test` under **Notification channel**.
 
     Fill in `High CPU Test Alert` as **Message subject**.
 
 :::note
-Multiple Actions can be defined, in this example we will define one
-action to send notification to destination we have defined in step 4
+Multiple actions can be defined. In this example, we define one
+action to send notifications to the channel we created earlier.
 :::
 
 ## Alert message
 
-**Message** can be adjusted as needed, check **Message Preview** to see
-the sample and use **Send test message** to validate notification
-delivery
+The **Message** can be adjusted as needed. Check **Message Preview** to see
+a sample and use **Send test message** to validate notification
+delivery.
 
 Select **Create**.
 
 <RelatedPages/>
 
 - [Alerting monitors configuration](https://opensearch.org/docs/latest/monitoring-plugins/alerting/monitors/)
+- [Notifications plugin](https://opensearch.org/docs/latest/observing-your-data/notifications/index/)