---
title: Synthetic Monitoring & Testing Overview Page
description: >-
  Use the Synthetic Monitoring & Testing Overview page to see which tests are
  failing, where failures cluster, and which endpoints and views have no test
  coverage.
breadcrumbs: >-
  Docs > Synthetic Testing and Monitoring > Search and Manage Synthetic Tests >
  Synthetic Monitoring & Testing Overview Page
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Synthetic Monitoring & Testing Overview Page

The Synthetic Monitoring & Testing Overview page gives you a single view of the health and coverage of your Synthetic tests, helping you answer two questions:

- **What is failing?** Identify which tests are in alert, see where failures are concentrated, and take action on each failing test.
- **What is not tested yet?** Find the highest-traffic endpoints and views that no Synthetic test covers, and create tests for them.

Use this page as the starting point for triaging failures and for deciding where to add test coverage.

{% image
   source="https://docs.dd-static.net/images/synthetics/explore/overview/overview_page.a33199de6047c6e1345cf7ec8ebcf71e.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/synthetics/explore/overview/overview_page.a33199de6047c6e1345cf7ec8ebcf71e.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="The Synthetic Monitoring & Testing Overview page, showing the Test health section with a failure map grouped by location and a list of tests in alert, and the Coverage gaps section with service cards of tested and untested endpoints." /%}

## Prerequisites{% #prerequisites %}

- To see untested endpoints, enable [APM](https://docs.datadoghq.com/tracing.md) for your services.
- To see untested views, enable [RUM](https://docs.datadoghq.com/real_user_monitoring.md) for your web or mobile applications.

The Test Health section of the Overview page doesn't require APM or RUM.

## Test health{% #test-health %}

The Test Health section shows how many tests are in alert out of your total number of tests. Click View all alerting tests to open the full list.

### Filter tests{% #filter-tests %}

Use these filters to scope the map and the list of failing tests:

- Teams: Show tests owned by one or more teams.
- Environment: Show tests for one or more environments.
- Tags: Show tests with specific tags.
- Creator: Show tests created by specific users.

### Find concentrated failures{% #find-concentrated-failures %}

The map shows where failures concentrate. It first splits tests into OK and In alert. Each tile represents a group and shows how many tests it contains. Larger tiles contain more tests.

Use the Group by menu to choose how the map groups tests:

- Location
- Test type
- Priority
- Failure reason
- Environment
- Team

When you group by location, a test appears under every location it runs from. Each tile shows whether the test is failing in that location. As a result, the tile counts can add up to more than your total number of tests.

{% image
   source="https://docs.dd-static.net/images/synthetics/explore/overview/failure_map.593d59b715e2cf20380fcd90531a9066.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/synthetics/explore/overview/failure_map.593d59b715e2cf20380fcd90531a9066.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="The failure map grouped by location, split into OK and In alert sections, with tiles sized by the number of tests in each location." /%}

### Act on a failing test{% #act-on-a-failing-test %}

The list next to the map shows every test in alert. Each entry shows the test name, the URL or request it checks, and the locations where it fails.

Click a tile in the map to filter the list to the tests in that tile.

For each failing test, you can:

- Click Investigate with Bits to start an AI-assisted investigation of the failure.
- Click View Traces to see the backend traces for an API test.
- Click View Failing Step to open the step where a browser test failed.

Click the kebab menu (**⋮**) on a test to:

- Run test now: Trigger a test run outside its schedule.
- Pause scheduling: Stop scheduled runs for the test.
- Open in Results Explorer: See the test's results in the [Results Explorer](https://docs.datadoghq.com/synthetics/explore/results_explorer.md).

{% image
   source="https://docs.dd-static.net/images/synthetics/explore/overview/failing_test_actions.9af237a8f27e17240d55ada342181aa0.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/synthetics/explore/overview/failing_test_actions.9af237a8f27e17240d55ada342181aa0.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="The failure map filtered to one location, next to the list of tests in alert for that location. Investigate With Bits is highlighted on the first test, and its kebab menu is open with Run test now, Pause scheduling, and Open in Results Explorer." /%}

## Coverage gaps{% #coverage-gaps %}

The Coverage gaps section shows the endpoints and views that no Synthetic test covers. Datadog ranks them by traffic, which is the number of requests or views over the past week. Start with the items at the top of the list to cover your highest-traffic surfaces first.

Use the toggle in the upper-right corner of the section to switch between Endpoints and Views. Use the search bar to find a specific service, application, endpoint, or view.

### Read the coverage grid{% #read-the-coverage-grid %}

Each card represents a service or an application. Each square in a card represents one endpoint or view:

| Color  | Meaning                 |
| ------ | ----------------------- |
| Blue   | Tested                  |
| Orange | Untested, high traffic  |
| Gray   | Untested, lower traffic |

High traffic is defined as follows:

- **Endpoints**: Across the top 20 services, Datadog sorts endpoints by number of requests over the past week. The endpoints that together make up 90% of requests are high traffic.
- **Views**: Across the top 20 applications, Datadog sorts views by number of views over the past week. The views that together make up 90% of views are high traffic.

{% image
   source="https://docs.dd-static.net/images/synthetics/explore/overview/coverage_grid.90b580b13465124727bc0d531640d98f.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/synthetics/explore/overview/coverage_grid.90b580b13465124727bc0d531640d98f.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="The Coverage gaps section in the Endpoints view with Group by service on. Service cards show orange squares for high-traffic untested endpoints, gray squares for lower-traffic untested endpoints, and blue squares for tested endpoints. The selected service's untested endpoints are listed on the left, ranked by traffic." /%}

### Untested endpoints{% #untested-endpoints %}

The Endpoints view lists untested API endpoints from APM. It shows the top 20 services by traffic. Each entry shows the HTTP method, the path, and the service.

By default, Group by service is on, so the view shows one card per service, with the number of untested endpoints in each. Click a service card to filter the list to that service's endpoints, ranked by number of requests over the past week.

To create a test for an endpoint:

1. Click a service card to filter the list to that service.
1. Hover over the endpoint at the top of the list, which has the most requests over the past week.
1. Click Create an API Test.
1. In the new [API test](https://docs.datadoghq.com/synthetics/api_tests.md), which opens with the endpoint URL prefilled, complete the test configuration and click Save.

{% image
   source="https://docs.dd-static.net/images/synthetics/explore/overview/create_api_test.7cd8f6d94fb40428057574583cefbeb9.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/synthetics/explore/overview/create_api_test.7cd8f6d94fb40428057574583cefbeb9.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="An untested endpoint in the list on hover, showing the Create an API Test button, next to the selected service card in the coverage grid." /%}

### Untested views{% #untested-views %}

The Views view lists untested views from RUM for your web and mobile applications. It shows the top 20 applications by number of views over the past week. Each entry shows the view name and the application.

By default, Group by application is on, so the view shows one card per application, with the number of untested views in each.

To create a test for a view:

1. Hover over a view in the list.
1. Click Create a Browser Test for a web application view, or Create a Mobile Test for a mobile application view.
1. Configure the new test, which opens with no fields prefilled:
   - For a web application view, in the new [browser test](https://docs.datadoghq.com/synthetics/browser_tests.md), enter the starting URL, record your steps, and click Save.
   - For a mobile application view, in the new [mobile app test](https://docs.datadoghq.com/synthetics/mobile_app_testing.md), select your application, record your steps, and click Save.

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Synthetic Monitoring](https://docs.datadoghq.com/synthetics.md)
- [Synthetic Monitoring & Testing Results Explorer](https://docs.datadoghq.com/synthetics/explore/results_explorer.md)
- [API Testing](https://docs.datadoghq.com/synthetics/api_tests.md)
- [Browser Testing](https://docs.datadoghq.com/synthetics/browser_tests.md)
- [Mobile Application Testing](https://docs.datadoghq.com/synthetics/mobile_app_testing.md)