Set up page-level monitoring

---
title: Set up page-level monitoring
description: Set up monitoring of the application performance at a specific page level. After the data is collected, you can view the performance metrics in the Metrics analyzer and in the device or application view.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/digital-end-user-experience-dex/set-up-page-level-monitoring.html
release: australia
product: Digital End-User Experience \(DEX\)
classification: digital-end-user-experience-dex
topic_type: task
last_updated: "2026-10-23"
reading_time_minutes: 1
breadcrumb: [Application monitoring setup, Configure, Digital End-User Experience, IT Operations Management]
---

# Set up page-level monitoring

Set up monitoring of the application performance at a specific page level. After the data is collected, you can view the performance metrics in the Metrics analyzer and in the device or application view.

## Before you begin

The DEX browser extension must be installed on the end-user devices.

The application must already be in the list of monitored applications in **Application Management**.

Role required: admin, dex\_admin

## Procedure

1.  Navigate to **Workspaces** > **Service Operations Workspace**.

2.  In the primary navigation pane, select the DEX Administration icon \(\[Omitted image "icon-administration.png"\] Alt text:\).

3.  On the Application management card, select **Configure applications**.

    The list of monitored applications appears.

4.  On the DEX Application Management screen, select a web application from the list.

5.  In the Edit web application form, select **Configure** under **Enable page-level monitoring**.

6.  On the DEX Application Pages list, select **New**.

7.  Complete the new record form as follows:

<table id="table_cxh_rpx_zgc"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Page Name

</td><td>

Application page name.

</td></tr><tr><td>

Domain

</td><td>

Web address that is used to launch the application and access its features and functions.

</td></tr><tr><td>

Application

</td><td>

Name of the application being monitored.

</td></tr><tr><td>

Pattern Type

</td><td>

The page URL pattern type: **Exact** or **Wildcard**.Using a wildcard, you can include not just a specific page but also its nested pages. For example, `/github.com/pricing/*`. Use a single-segment wildcard \(`*`\) for predictable one-level variations, and a multi-segment wildcard \(`**`\) when the structure beneath a path can vary widely.

</td></tr><tr><td>

Page Path

</td><td>

The URL for the page or pages using exact path or single-segment or multi-segment wildcard.

</td></tr><tr><td>

Full URL

</td><td>

The full URL automatically populated from the **Domain** and **Page Path** fields.

</td></tr><tr><td>

Metric Monitoring

</td><td>

Option to monitor the page when selected.This check box is selected by default.

</td></tr></tbody>
</table>8.  Select **Submit**.


## Result

When the metrics for the page are collected, you can view them in the Metrics analyzer. For details about viewing metrics, see [View collected metrics with Metrics analyzer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/digital-end-user-experience-dex/view-dex-metrics.md).