Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

On this page:

Related pages:

Experience Level Management (XLM) enables you to configure and monitor compliance targets that impact your business and users. It also lets you service level agreements (SLAs) through application performance monitoring. 

How it Works

XLM measures compliance based on configured daily percentage thresholds. By defining a compliance policy, you can view compliance levels for all events in weekly or monthly periods, with the ability to drill-down into daily granularity. 

By adding your XLM report to a custom dashboard, you can create a scheduled report for periodic generation and delivery.

Examples of the type of data to which you can apply user experience level or service level reports include:

  • Application response times calculated from business transaction events
  • End user response times calculated from RUM and synthetic events
  • Custom analytics data such as login times for platinum customers or item checkout response times for London customers

XLM Monitoring

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

If you revise the configuration during a compliance period, the next time the job runs, compliance is computed with the configuration that is in effect at that time. Once time has passed over a compliance period, the past data is immutable and configuration changes do not affect the values.

Note that XLM data is calculated using UTC time zone for time-based calculations.

XLM Exclusion Periods

The XLM queries executed against your Analytics event data observe configured exclusion periods. Exclusion periods cover the UTC equivalent of the Controller's local time zone because exclusion periods are always resolved to UTC time, even though you configure the exclusion period as local time in the Controller UI. This means that some events may fall on a certain day in your local time zone, but a different day in UTC time.

For example, if you specify an exclusion period for Friday 1am to 11pm and you are in the Pacific time zone (which is GMT -7), the exclusion period is resolved to Friday 8AM - midnight and Saturday midnight - 6am.

XLM does not automatically recognize controller-level exclusion and maintenance periods. In such cases, you need to explicitly add those exclusion periods in XLM.

XLM Auditing

All changes to XLM configurations produce an immutable audit record.  The XLM audit reporting is completely separate and distinct from other reports available in the AppDynamics Controller UI, such as the Controller Audit Report.

The XLM audit records contain information about the operation that was performed and the fields that were changed. In the UI, the audit records are presented as a sequential timeline:

Audit History Size Constraints  

There islimit of 1000 updates to each XLM configuration. If that limit is reached, the oldest audit records are dropped as new ones are added.

Watch the Video

For full-screen viewing, click Experience Level Management.

  • No labels