Open topic with navigation
The Detail report shows all monitor runs over the selected period, with the check status (success or error) and the response time breakdown for each run. It is similar to the Daily report, but includes the results of all monitor runs rather than daily averages.
The Detail report may cover a period up to 31 days. You can run reports for older data up to your data retention period, but the time span that each report covers cannot exceed 31 days. To collect data for larger time periods, you need to run multiple reports.
You can view the Detail report for a specific run, or run a cumulative report for a specific period. You can also generate the Detail report programmatically using AlertSite Report API (see below).
Do any of the following:
Note: Reports opened in this way include only the Report Details table with the response time breakdown and the drill-down links. To get a report with charts or other sections, create a custom report in Reports > Performance Reports, as explained below.
Once the report is ready, you can view, email or schedule it. For details, see Creating and Scheduling Reports.
The created report will automatically appear at the top of the Document Manager. By default, the report will disappear after 30 days, but you can preserve it indefinitely by clicking the Save icon to the left of the report. Saved reports can be viewed in the Documents Manager at any time.
Report contents depends on the options you selected when creating the report.
The top chart shows the monitor availability (OK/error) over time. The bottom chart shows the response time by location. The response time here is the base page response time, not the full page response time.
If this option is selected, the report will include two charts – a line/bar chart (the same as the one added by the Graphs option) and a scatter plot.
The scatter plot shows the monitor status (a green diamond for success, a red triangle for error) and response time over the selected time period. Clicking a data point opens a report with the run details.
Supported monitor types: website, real-browser (DéjàClick) and API monitors.
This section shows the average, minimum and maximum response times observed during the report period, and the standard deviation of the response times (measurement of how spread the numbers are). For a description of the response time components (DNS, Connect and others) see Web Page Load Time. Note that the Response column here shows the base page response time, not the full page response time.
Note: This data includes only successful tests (with status 0).
This section is included:
It groups the full-page response time of the monitor and its individual pages into nine ranges from 0 to 30+ seconds, so you can see the distribution across these ranges. Each range includes the starting value but not the ending value, that is, "min–max" means "min ≤ ... < max".
This section shows the distribution of the Fullpage Response Time of successful monitor runs (status 0) across various time ranges. A monitor’s full-page response time is the sum of the full-page response times of all monitor steps. This time includes all network components and content download times for all pages, images, scripts, CSS and other content loaded by the monitor.
To understand this section, first, let’s see what an “individual page” is. Real-browser (DéjàClick) monitors use the following terms:
Individual pages (or HTTP Steps in DéjàClick terms, not to be confused with HTTP requests) – These are network activities triggered by events. For example, a navigate event always loads a new page. A link click may also load a new page, or it may trigger an Ajax request to load some additional content into the current page. The new content being loaded as a result of the event is referred to as "individual pages" in the report.
In general, a single event may trigger several individual pages if that event makes different types of requests to different servers.
To see the individual pages of your monitor, expand the entries in the Report Details down to events. The individual pages are the immediate child items of events.
The Individual Page Time section breaks down the individual pages into ranges from 0 to 30+ seconds based on their full-page response time. This is calculated as follows:
This section shows how many times each monitor status code was received. Note that this does not include full page monitoring statuses (7xxx).
This table lists all monitor runs over the selected period, with the status code and response time breakdown for each run.
Error statuses 21, 90, 95 and 6061 indicate the times when a scheduled test could not be performed. However, they are not included in monitor availability calculation.
In reports for DéjàClick, SoapUI and Perfecto monitors, you can expand the runs to view results of individual test steps and HTTP requests.
For a description of the report columns, see Report Column Descriptions.
You can get the report data in XML or JSON format using AlertSite’s Report API. For example, the following URL returns XML data for customer ID C12345, device ID 76981, from Atlanta, Boston and Chicago (IDs 20, 72 and 50), for yesterday:
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/detail/C12345?&obj_device=76981&location=20,72,50&rdate=Yesterday"
For more information and examples, see Report API.