Formerly known as AutoSteps Status
The AutoSteps Job Heat Map Widget monitors the conditions of the Scripts executed by AutoSteps. The widget together with the AutoSteps Chart Chart widget gives you an overview with a matrix stating the latest execution of the scripts as well as showing history in the graph. The AutoSteps Status widget provides overall status information for the jobs handled by AutoSteps as well as status information of individual jobs.
AutoSteps works by issuing automated, simulated transactions from a script client to your application. These testing scripts become "monitoring" tools by running at regular intervals providing you with a baseline. For more information view AutoSteps Setup.
AutoSteps will keep running, discover the error, alert you and provide detailed information about the problem where real user monitoring will not be able to comprehensively test for the functional correctness.
Alongside these scripted measurements AutoSteps will also keep track of how the scheduled jobs are doing. This information is what is presented in this widget.
Set up the Widget
| Note | ||
|---|---|---|
| ||
| You can only do this if you're a PerformanceGuard administrator. |
You simply need to add the widget to the dashboard by adding the required information in the widget setup dialog's menu.
| Tip | ||
|---|---|---|
| ||
| It will update the controller options only if configuration is set to "inherit". |
AutoSteps Status Matrix
AutoSteps Status matrix displays Script Category and Executor Groups.
Y-Axis
The Y-axis displays Script Category i.e. a list of scripts grouped by their respective categories.
The Scripts are a combination of a Script file, information about what program is to be used to execute the script and a set of execution parameters. Scripts are part of the definition of a Job together with Schedules and Executor Groups.
X-Axis
The X-axis displays Executor Groups i.e. a list of executor agents grouped by their respective executor groups.
The Executor groups are part of the definition of a Job together with Scripts and Schedules.
| Info | ||
|---|---|---|
| ||
Example: Click thumbnail to view image in full size.
|
The execution for scheduled jobs will be displayed on the AutoSteps status widget in different colors depending on their status i.e. red, green, yellow and white e.g. if a job failed it will be displayed as red. However, it will not provide you with enough information to diagnose what exactly failed and why.
Read more in AutoSteps Usage.
| Tip | ||
|---|---|---|
| ||
| Red: If the last execution has failed. |
| Tip | ||
|---|---|---|
| ||
| Yellow: If the last execution has been successful but a previous execution has failed. |
| Tip | ||
|---|---|---|
| ||
| Green: All executions have been successful. |
| Tip | ||
|---|---|---|
| ||
| White: It hasn't been configured or started the execution yet. |
Select what you Want to View
The AutoSteps status The widget displays an Overview of Script Category and Executor Groups on your dashboard. How to create these Script Category and Executor Groups, see Create a New Script Category or Executor Group.
| Note | ||
|---|---|---|
| ||
| The AutoSteps Status widget will display all the categories automatically when you will start the Widget. |
- Simply click on a category listed under Script Category or a group listed under Executor Group that you want to view on your dashboard to see the individual job results within those category and groups. Click
to come back to the default view. - Hovering over the Scripts will give you the exact time and date of the last execution of the Scripts.
AutoSteps Widget
The widget together with the AutoSteps Chart Widget gives you an overview with a matrix stating the latest execution of the scripts as well as showing history in the graph. You can measure a number of metrics such as response times, availability and requests from a number of different Executors.
For a detailed analysis of AutoSteps widget data with AutoSteps widget view Analyze AutoSteps data.
The two widgets together provides a great flexibility and allows you to retrieve data specific to their needs by creating/adding customs scripts.
AutoSteps can be run as frequently as needed, every few minutes if necessary allowing you to monitor availability and end-to-end performance 24/7.
History
The history functionality in the AutoSteps Status widget allows you to monitor the status of the scripts executions.
The navigation in the status tab reflects what you can view in the History e.g. if you have script category expanded and not the executor groups then in history you can view each individual script's status but not an individual executor. Updating the time period (zooming) also affects the status and history of the widget as well.
| Info | ||
|---|---|---|
| ||
Example: Click thumbnail to view image in full size. In this example you can see that by sub-categorizing the scripts in the status tab, you can view the history of each individual script.
|
You can view the history by two modes:
History by Executor Groups
This mode allows you to view the history by the default or by executor groups i.e. which ever view has been selected in the Status. It allows the user to identify the exact time in that executor group in which the problem has occurred which caused an unsuccessful execution.
History by Script Categories
This mode allows you to view the history by scripts or script categories i.e. which ever view has been selected in the Status. It allows the user to identify the exact time in that particular script in which the problem has occurred.
The history bubbles have two indicator colors:
| Tip | ||
|---|---|---|
| ||
| Red: If the last execution has failed. |
| Tip | ||
|---|---|---|
| ||
| Green: The last execution has been successful. |
| Info | ||
|---|---|---|
| ||
Example: Click thumbnail to view image in full size. In history each bubble gives an indication of the last execution seen in status i.e. the user is able to identify at what time an execution has been successful or failed in script / executor.
|
| Panel | ||||||
|---|---|---|---|---|---|---|
Search this documentation
On this page
In this section
|