Deprecated Site!

The new AlertFox Help Pages have replaced
this wiki as the primary place of AlertFox documentation.

Information on this site will no longer be
updated and will be taken offline, eventually.

Reporting

From AlertFox Website Monitoring
Jump to: navigation, search

This page has been changed. Please refer to http://alertfox.com/help/reporting/ for the latest changes

AlertFox offers various online and email reporting options. In addition, you can download all sensor data to create our own customized reports.

Performance Reporting

Performance Overview

This page has been changed. Please refer to http://alertfox.com/help/performance/ for the latest changes.

Dashboard with uptime & performance overview chart

AlertFox Performance Report - This report shows the uptime and a performance overview (green, orange, red, brown) of all monitored sites and services on one page. White indicates no data (i.e., sensor turned off) and brown indicates an error. The black bars show up if not 100% of the test in one hour (= one box) are successful. So if you have 4 tests/hour and 3 are ok and one fails you will have a 75% success rate => The black bar will be 25% of the square. The logfile contains the details (e. g. what error happened).

Sensor Performance

This page has been changed. Please refer to http://alertfox.com/help/performance/ for the latest changes.

Detailed performance graphs and error logs for each sensor

Detailed Sensor Performance over time for all global locations. Errors are annotated in the diagram and a screenshot can be viewed (click [S] to view the screenshot). All raw data can be exported in CSV for further processing by you (e.g., with Excel).

Multi-Step Performance

This page has been changed. Please refer to http://alertfox.com/help/multi-step/ for the latest changes.

Detailed performance graphs for transactions that consist of several steps. (Currently, the number of steps is restricted to 5.)

Stacked runtime graph for the steps within a single transaction.

In order to use this feature, the relevant steps need to be marked within the macro. There is no limitation on the number of macro commands a step may contain (within the general limits for a single sensor).

As you see in the following example, it is the "STOPWATCH LABEL=name" command that defines the steps:

'Test: Fill web form, submit it and test the result
VERSION BUILD=6210317 RECORDER=FX
URL GOTO=http://www.iopus.com/imacros/demo/v6/f1/form.asp
STOPWATCH LABEL="Load URL"
TAG POS=1 TYPE=TEXTAREA FORM=NAME:TestForm ATTR=NAME:Remarks CONTENT=AlertFox<SP>Demo
STOPWATCH LABEL="Fill field"
TAG POS=1 TYPE=INPUT:SUBMIT FORM=ID:TestForm ATTR=NAME:SendButton&&VALUE:Click<SP>to<SP>order<SP>now
STOPWATCH LABEL="Submit"
'Checkpoint: Test the submission result
TAG POS=1 TYPE=B ATTR=TXT:*AlertFox<SP>Demo*
' (Note that there may be more than one macro command within a step. This is just a short example.)

Getting more information from the graph.

The graph displays the runtimes that each of the steps adds to the total. When hovering over a data-point, exact temporal information is displayed.

Hovering over a data-point shows detailed information.

Toggling the display of certain steps from the graph (by clicking the corresponding colored boxes below the graph) is very helpful in order to analyze a certain step's influence on the total runtime.

Not easy to see which step did add to the peak? Try toggling certain steps.
This step does add an extra second to the peak.
This step does not add a relevant amount of time. Note that "remaining lines" is an artificial step we add in order to show the total runtime even if there is no STOPWATCH command used at the very end of the macro.

Changing, adding, or deleting labels in an existing sensor.

Changing the labels in an existing sensor poses a particular problem: how is the historical data with the old labels and current data with the new labels supposed to be displayed in the same graph? The system handles this by effectively creating a new set of labels and keeping, but renaming, the old set and displaying both in the graph.

In this example, a new step labeled "LOAD IMACROS.NET" was added to the sensor after it had already been running for some time.

This happens whenever the following occurs:

  1. You delete a label
  2. You rename a label
  3. You add a label
  4. You swap labels

Root Cause Analysis

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

AlertFox error reports include detailed information to diagnose and fix website uptime and performance problems.

Root cause analysis - each error message contains in-depth information on the error, down to each byte that was sent and received before the problem.

Browser Screenshots

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

Each error message includes a screenshot of the test browser at the time of the issue - you see the website exactly like a real human tester would have seen it.

Waterfall Diagrams

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

Get a grip on the load time of each and every element of your site. Perhaps there’s a certain external image slowing it down? AlertFox returns waterfall diagrams on each error.

Web Traffic Protocols (HAR)

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

Extending the idea of Waterfall Diagrams to a whole browser session is what HAR files (HTTP Archives) are about: the complete HTTP traffic in one protocol file including requests, responses and detailed timing information. So if you need to check how much load time your payment provider adds to your streamlined web shop, HAR files are the way to go!

HTTP traffic performance trace of a browser-based transaction check.

We support them for all browsers: iMacros Browser, Internet Explorer and Firefox.

HAR reports need to be enabled in the Advanced Settings section of for each sensor:

How to enable web traffic logs (HAR): Go to the Edit Sensor page, expand the Advanced Section and check the box to create waterfall diagrams on error.

See also: Common HAR Findings Explained

Test Waterfall Chart Creation

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

Once you have enabled waterfall creation, you can use the Test Now button to test it. A test run includes a waterfall chart even if there was no error in the test run.

View Waterfall Charts

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

To view the waterfall chart, go the to Sensor Log Report. In lines (measurments) that show an error you find the symbols

  • [SCR] = View screenshot
  • [PERF] = Performance Report
  • [WF] = Waterfall Report

Performance Profiler

This page has been changed. Please refer to http://alertfox.com/help/sensor-log/ for the latest changes.

Interested in how fast each step of your transaction (macro) sensors is performed by the browser instance you selected? Then have a look at the performance logs, marked as [[PERF] in your log. For now, these are supported by the iMacros Browser and Internet Explorer. Firefox will follow soon.

Here is an example. You see the status and duration for each step of the transaction. The data is provided as XML file, thus it can easily parsed and processed further. The data is also available via our API.

Email Reports

This page has been changed. Please refer to http://alertfox.com/help/summary/ for the latest changes.

You can opt to receive daily, weekly, monthly and yearly reports by email. On the same panel you can also opt-in/out of the AlertFox Newsletter.

Daily, weekly, monthly and yearly reports inform you about your websites' performance.

How to read the reports?

This page has been changed. Please refer to http://alertfox.com/help/summary/ for the latest changes.

The report in split into two parts: the "classic" sensors that cover HTTP/DNS tests and the "iMacros" sensors where your macros are run on some site. The columns of these two parts, however, have the same meaning.

  1. Uptime/Downtime:
    • Internally, we track each time there is a sensor state change (from Up to Down and vice versa). For each state change we record the start and end time. Then to compute the times for a given period, we calculate:
      • Total Time = sum of all state durations (End Time - Start Time)
      • Total Uptime = sum of all state durations where State is Up
      • Total Downtime = Total Time - Uptime
    • These values are then used to calculate the corresponding percentages.
  2. Average (time):
    • How long did the test take?
    • Given in milliseconds
    • E.g. "98.27" means that on average, the site responded in ~98ms
  3. OK:
    • Total number of successful tests
    • E.g. "1800" means that 1800 tests had a positive result
  4. NOK (not OK):
    • Total number of failed tests
    • E.g. "200" means that 200 tests failed (which, together with the 1800 "OK" from above would result in an "Uptime" of 90%)
  5. Finally, you will find a row called "Total Average" in both parts of the report, which gives the "average of averages", i.e. the average of the column above.

Enable/Disable Reporting

This page has been changed. Please refer to http://alertfox.com/help/summary/ for the latest changes.

To enable or disable the email reports, go to Reports > Email:

Select which user account receives alerts (notifications), reports and the AlertFox Newsletter.

Data Export

This page has been changed. Please refer to http://alertfox.com/help/summary/ for the latest changes.

All measurement data can be exported in CSV format. See the "Export to CSV" button below each diagram.


AlertFox Data Export

AlertFox API

This page has been changed. Please refer to http://alertfox.com/help/alertfox-api/ for the latest changes.

We are currently developing a new Web API (Application Programming Interface) as the ideal solution to interface our service directly with your monitoring infrastructure.

If you want to access AlertFox data via the API please contact support to let us know you are interested and tell us your requirements!

Read-Only User Accounts

This page has been changed. Please refer to http://alertfox.com/help/account-logins/ for the latest changes.

You can choose to create a read-only account for your team members. This allows them to view the reports and logs, but prevents them from editing the monitoring sensors. Go to Settings -> Logins -> Add New User -> and select "Read Only" for the User Type.


Public Reports

This page has been changed. Please refer to http://alertfox.com/help/public-graphs/ for the latest changes.

You can make certain sensors graphical reports public. To do this, check the "public" checkbox on the sensor settings. The sensor list will then contain a link to the public report website.

Example: http://status-dashboard.com/32226/44295

See also: Status Dashboard and this blog post.


Make the graphical performance report public.


Get the link to the public graphical performance report.

Data Retention

AlertFox sensor data is retained for a period of 60 days, therefore all reports will be limited to this time frame.