Configure an XLM report
- From the Controller UI, choose Analytics > Experience Levels and click Add.
- In the Properties section, name your XLM report uniquely. Select the event type and any filters necessary for isolating the data that you want to evaluate.
- Select the desired field, target value, and daily target thresholds. Choose a time zone, report start date, and reporting period. Past dates are not allowed.
- (Optional) Select Treat Errors as Critical Failures.
- (Optional) Specify Exclusion Periods using the time period of your choice to denote periods during which data should be not collected.
- Save the configuration. Data is collected and compliance is calculated in an automatic job that runs twice per day.
Treat Errors as Critical Failures
You can choose to treat events with errors as critical failures.
This enables you to identify instances where an event meets the compliance target but has a user experience status of Error.
For example, if you have defined Response Time of under 2000 milliseconds as the compliance target, an event with a response time of 100 milliseconds meets the compliance target, even if that event finished prematurely because of an error. In that case, XLM reporting that performance as Normal could be considered a false positive.
When you enable Treat Errors as Critical Failures, XLM will catch instances like this. Whether this option is optimal for your application is a subjective judgment for you to make.
Treat Errors as Critical Failures is only supported for event types that contain a user experience or similar field, as shown in the table below.
|Event Type||Experience Field|
|Mobile Snapshot (Network Request)|