SLA Reports sla-reporting
Learn how to see the performance of your production AEM environment relative to the contracted SLA (Service Level Agreement).
View an SLA report introduction
SLA report data tracks performance metrics for two production tiers: Author Tier and Publish Tier.
The line graph of a selected year includes data points for each month from January to December. The following metrics are tracked.
To view an SLA report:
-
Log into Cloud Manager at and select the appropriate organization.
-
On the My Programs console, select the program.
-
From the Program Overview page, in the left side menu, click Reports.
-
Click SLA Reports.
-
Click the year desired to see a line graph of SLA data.
-
(Optional) Do any of the following:
- Roll your cursor over a data point in the line graph to show the specific values for that point.
- Below the line graph’s year, click the Download icon to save a PNG image file of the line graph.
- Click a metric name to see just that metric’s data. Or, press
Shifton the keyboard while selecting or deselecting one or more metric names.
Event Analysis event-analysis
The Event Analysis section under the graph shows the set of incidents that occurred for the program during the selected year.
Each of the incidents has a time range, a cause, and a set of comments.
Refresh interval of SLA reports refresh
SLA reporting gives you insight into the performance of your AEM production environment and is up-to-date, but not instantaneous. SLA report generation happens monthly and it is generated for new programs that are marked as Production previous month. It is not instant. Because of this delay, keep the following in mind as you review your SLA report:
- The reported SLA is the one that existed at the start of the month, even if SLA changed during that month.
- If there was no SLA at the start of the month because the program did not exist, the SLA that existed at the date the program was created applies.
Preview environments preview
The preview environment is intended as a tool for content authors to verify the content’s final experience before publishing. Because of this functionality, preview environments are not designed with high-availability and do not have an associated SLA.