---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Use metric rules for DEX

# Using metric rules for Digital End-User Experience {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Metric rules set criteria and thresholds, triggering alerts when performance metrics deviate from specified parameters and facilitating effective system monitoring and management. This comprehensive approach to generating
alerts enables you to identify and address potential issues, which helps enhance system reliability and operational efficiency.

To access the metric rules page, navigate to WorkspacesService Operations Workspace and, in the primary navigation, select the Administration icon (![Administration icon]()). Select the Metric rules card.  
Note:  
When you initially install Digital End-User Experience (DEX), a set of preconfigured metric rules is available with the base system. These rules remain inactive on installation. For more information on how to activate them, see [Activate or deactivate alert rules](https://servicenow-prod.fluidtopics.net/5NjLfjmUMgdgTwibd~yv4g "Activate or deactivate alert rules to streamline monitoring and adapt to changing needs, enhancing operational efficiency."). If you delete these rules, they're permanently removed and can't be retrieved.

If you installed the DEX
Proactive Engagement application and added an alert action for any of the rules, the Action field shows the added action.

For details about the fields and their descriptions on the metric rules page, see [Metric rules page](https://servicenow-prod.fluidtopics.net/j_JdncT831pYWkHam01ORQ "The metric rules page shows information about a specific rule, including its name, CI type, application name, alert severity, and alert status.").

*[\>]: and then