Multi-Step

Detailed performance graphs for transactions that consist of several steps. Currently, the number of steps is restricted to 5. 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). You can add a step in a macro with the “STOPWATCH LABEL=name” command.

The graph displays the individual run time required for each of the steps.

When hovering over a data-point, exact temporal information is displayed.

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 run time.

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:

iMacros is Automation Delivered

SITE MENU

ABOUT ALERTFOX

A subscription-based uptime and web performance monitoring service, AlertFox makes it easy to find and resolve common web performance problems such as slow response times; failed transactions or time outs; bugs in Ajax, Flash or Silverlight front-end applets; and even user experience problems resulted from different locations or browsers. You name it, with AlertFox you can do it.