[DOCS-12756] add alerting to test suites (#33387)

* add alerting to test suites

* fix image

* rework page

* incorporating PM feedback

* Apply suggestions from olivia's review

Co-authored-by: Olivia Shoup <116908616+OliviaShoup@users.noreply.github.com>

* remove redundancy

---------

Co-authored-by: Olivia Shoup <116908616+OliviaShoup@users.noreply.github.com>

Author: git-thuerk-done

content/en/synthetics/test_suites/_index.md

@@ -16,13 +16,13 @@ further_reading:
   text: "Get organized, actionable insights from complex test environments"
 ---
 
-
 ## Overview
 
-Synthetic Monitoring Test Suites let you organize multiple tests into a single collection for simplified management and troubleshooting. Group tests by user journey, environment, location, service, team, or any other dimension that fits your workflow. View aggregated results, identify failing components, and understand application performance across related tests, all from a unified view. 
+Synthetic Monitoring Test Suites let you organize multiple tests into a single collection for simplified management and troubleshooting. Group tests by user journey, environment, location, service, team, or any other dimension that fits your workflow. View aggregated results, identify failing components, and understand application performance across related tests, all from a unified view. Configure suite-level alerting to receive a consolidated notification when a critical portion of your tests fail, helping you respond more efficiently to issues impacting important workflows. 
 
 ## Key features
 
+- **Impact-driven alerting**: Receive a consolidated alert when a critical portion of the test suite fails.
 - **Centralized visibility**: View all tests in a suite and their results in one place.
 - **Simplified management**: Create and run test groups instead of managing individual tests separately.
 - **Easier maintenance**: Identify which tests need updates when application changes are made.
@@ -42,26 +42,37 @@ To create a new Test Suite:
    - **Search** by name or tag.  
    - **Filter** by test type (such as Browser, API, Private Location, or Mobile).
    - **Select** one or more tests to include.
-3. Click **Add Selected Tests** to confirm.
-4. Optionally, remove tests using the **Remove Test from Suite** icon next to each entry.
-5. Click **Save suite** when finished.
+3. Click **Add Tests** to confirm.
+4. _Optionally, remove tests using the Remove Test from Suite icon next to each entry_.
+5. Configure alerting for the suite:
+   - By default, all tests are marked as **Critical**, and the alert triggers when any critical test fails. 
+
+     **Note**: Suite alerts are separate from individual test alerts. To avoid duplicate notifications, mute alerts on individual tests included in the suite.
+   - To exclude specific tests from triggering the suite-level alert, select them and mark them as **Ignored**.
+   - Adjust the alert threshold to trigger only when a specified percentage of critical tests fail.
+
+   {{< img src="synthetics/test_suites/suite_alerting.png" alt="Suite alerting creation page, with the suite alerting drop-down expanded. " style="width:80%;">}}
+
+   **Note**: For existing test suites, alerting is enabled with default settings. You can modify the configuration as needed.
+
+6. Configure [monitor settings][2] (notification message, recipients, renotification) the same way you would for a single test.
+7. Click **Save Suite** when finished.
 
-{{< img src="synthetics/test_suites/test_suite_creation.png" alt="Synthetic Monitoring Test Suite creation page" style="width:80%;">}}
+{{< img src="synthetics/test_suites/test_suite_creation_2.png" alt="Synthetic Monitoring Test Suite creation page" style="width:80%;">}}
 
 ## View and manage
 
-After creating your suite, it appears in the **Suites** tab on the [Synthetic Monitoring tests][1] page, or you can access test suites from **Digital Experience > Test Suites**. Click on a test suite to display the following:
+After creating your suite, it appears in the **Suites** tab on the [Synthetic Monitoring tests][1] page, or you can access test suites from **Digital Experience > Test Suites**. 
 
-- A **summary** of test results (success, failures, skipped).
-- **Execution details** such as timing, environment, and test type.
-- **Filters** to refine by location, time frame, or tag.
-- **Drill-down links** to individual test runs for deeper investigation.
+When viewing a test suite, three tabs are available:
 
-You can sort or search within the suite to focus on failing or recently updated tests. Use the **View All** option to visualize the aggregated performance of all included tests.
+- **Tests in the Suite**: Lists all tests included in the suite.
+- **Test Runs**: Displays global uptime metrics and related test runs.
+- **Attributes**: Shows suite attributes such as `team`, monitors, and who created the test suite.
 
 **Note**: Test runs appear in the suite only from the date the test was added. To view earlier results, check the individual test page. If you rename a test, previous runs remain listed under the original name. A maximum of 300 tests can be added per suite.
 
-{{< img src="synthetics/test_suites/test_suite_summary.png" alt="Synthetic Monitoring Test Suite summary page" style="width:100%;">}}
+{{< img src="synthetics/test_suites/test_suite_summary_2.png" alt="Synthetic Monitoring Test Suite summary page" style="width:100%;">}}
 
 ## Troubleshooting
 
@@ -82,3 +93,4 @@ If execution results look incomplete:
 {{< partial name="whats-next/whats-next.html" >}}
 
 [1]: https://app.datadoghq.com/synthetics/tests
+[2]: /synthetics/notifications/