Whether you speak of an experience level or a service level depends on whether your focus is user experience or SLAs, but you configure both through the same XLM UI. What this section says about experience levels applies equally to service levels.

You can define experience levels for any kind of data that meets the following criteria:

1. The data must be numerical.

2. The data must be individual (per event) values, not aggregates.

Since data collectors provide individual values, they are a good basis for experience levels as long as the values are numeric. By contrast, metrics and information points cannot be used as the basis for experience levels, because they provide aggregate values.

The following are all good bases for defining experience levels:

• Sales in dollars per week during the time an ad campaign is running

• Application response times calculated from business transaction events

• End-user response times calculated from RUM and synthetic events

• Custom analytics such as login times for platinum customers or item checkout response times for London customers

Compliance against the configured thresholds is calculated in daily intervals from the specified start date. The local time zone starting time for each day is converted to midnight of the equivalent Greenwich Mean Time (GMT) date. For example, 07/30 means 12:00 am GMT on 07/30. The reporting job that calculates the XLM data runs every day at midnight and noon GMT. The results are updated the next time the reporting job runs.

XLM aggregates the results of reporting jobs into weekly or monthly periods, according to your choice of Compliance Period settings, including Time Zone.

When viewing XLM data for a week or month, you can drill down into daily granularity. XLM also allows you to

• Create XLM reports in the time zone of your choice
• Export reports of however many reporting periods you choose, in CSV format
• Add your XLM report to a custom dashboard for periodic generation and delivery

You can export XLM configurations, and migrate them from one environment to another. You can also view and export the XLM Audit Trail, which automatically records XLM configurations and changes to them.

If you revise the configuration, the new configuration takes effect the next time the XLM reporting job runs. Past data is immutable and configuration changes do not affect the values.

To see which configuration was in effect at a particular moment in a reporting period, view the XLM Audit Trail.