Open topic with navigation
This report is for monitors that have Service Level Agreement (SLA) objectives configured for availability, uptime, and response time. It compares the actual website performance with these objectives. The report includes only data collected during SLA operating periods to account for maintenance downtime and other factors.
Once the report is ready, you can view, email or schedule it. For details, see Creating and Scheduling Reports.
The report shows your SLA objectives for availability, uptime and response time and the actual results from your site. Actual results are calculated based on data from the SLA operating periods (default is 24×7, but you can change it in SLAs > Op. Periods / Exclusions).
Service level objectives are defined as follows:
For more information about these metrics, see About Service Level Agreements.
The Errors / Checks column shows the number of error occurrences out of all checks. An error means an availability error, downtime, or response time that exceeds the objective. For example, the above report shows Response Time Errors / Checks = 2/2631. This means that out of 2631 checks during the reporting period, response time was higher than the goal average 2 times. But the average response time, 2.4653 sec, is still lower than the objective, 3 sec, so the site is in SLA compliance.
The number of checks shown depends on the monitoring interval, number of locations used at each interval, SLA operating periods, and the monitor blackouts (if any). Note that the number of Uptime checks in the report is lower than the number of Availability and Response Time checks. This is because as long as one location can access the site successfully, that is all that is included in the statistics.
Click the links in the Errors / Checks column to view a list of availability errors and downtime periods, including the date/time, location and status code. You can add your comments about these errors – make sure to click Save Notes when you are finished.
You can get the report data in XML format using AlertSite’s Report API. For example, the following link generates a report for customer ID C12345, monitor ID 130705, from Charlotte, Boston, and Austin locations (IDs 22, 63 and 72), for the last week. You can open this link in the browser, and the XML report data will be displayed.
Make sure to replace the highlighted values with your actual values:
The monitor ID appears in the browser’s address bar if you go to Monitors > Summary and select your monitor.
To download the report using cURL or similar tools, include your AlertSite login and password for authentication:
curl -o report.xml -u firstname.lastname@example.org:password "https://www.alertsite.com/report-api/sla/C12345?&obj_device=130705&location=20,30,40&rdate=LastWeek"
For more information and examples, see Report API.
SLA Detail report shows more Uptime checks than should be
Q: We are monitoring every 15 minutes, which means 4 checks per hour, 96 checks per day and 672 checks per week. But the weekly report shows 690 checks – more than it should be. Where do the extra checks come from?
A: SLA (MultiPOP) monitors run tests from multiple locations simultaneously at each interval. When using rotated locations, the default behavior when one of the locations cannot be reached is to repeat the test from other locations that can be reached – to fulfill the SLA requirement of a simultaneous test from N locations. This is what causes extra checks.