In the XLM UI, you configure Properties, Compliance Target Settings, and optional Exclusion Periods.

• Properties specify what type of event to measure and what filters to apply.
• Compliance Target Settings specify the performance criteria you want XLM to report, through
  • the Compliance Target, which defines the desired level of performance for the properties
  • Daily Target Thresholds which define Normal, Warning, and Critical performance as percentages of the compliance target
  • Treat Errors as Critical, an option helpful for applications where apparently normal performance thresholds tend to conceal errors
• Compliance Target Settings also specify how you want your XLM reports structured in terms of time, through
  • the Start Date: the date you want the compliance calculation to begin
  • the Compliance Period, which
    • you can think of as the reporting period
    • can be weekly or monthly; choose one or the other according to your SLA requirements
  • the Time Zone of your choice
• Exclusion Periods help you account for performance deviations caused by upgrades, maintenance, or usage patterns associated with weekends or holidays.

Here is how our e-retailer example might look:

• The properties have Transactions as the event type, filtered to exclude all but an Add to Cartbusiness transaction, for the relevant application
• The compliance target is Response Time (ms), set to 100
• Values for daily target thresholds are 95% to 100% for Normal, 90% to 95% for Warning, and 0% to 90% for Critical
• The compliance period is Weekly
• The time zone is GMT+02:00 for Amsterdam, where our hypothetical e-retailer has customers

Configured this way, XLM reports that performance is Normal for each week-long reporting period when the Add to Cart business transaction completes within 100 milliseconds greater than 95% of the time.

For periods when Add to Cart performance meets the target 95% of the time or less, but above 90% of the time, performance is at Warning level.

For periods when performance meets the target 90% of the time or less, performance is Critical.

This example configuration is illustrated below.