View – Working with Left Menu
View menu is further categorized into the following sub menu/menu items:
- Dashboard: This displays the current Dashboard.
- Test Runs: Shows the test runs window.
- Scripts: To launch the script manager and create a script.
- Scenarios: To create scenarios.
- Run Time Progress: This shows the run time progress of the test. This is only available when the test is running currently. There are two further options within this – Scenario and Runlogic Progress.
- Virtual User Trace: This is used for tracing the users for different group(s).
- Transactions: This displays detailing of all transaction(s) in current test run.
- System Logs: To view system related logs, such as Kubernetes logs, RBU access logs, peripheral device logs, and system events.
- Test Output: This shows the test output in browser as well as on panel.
- Debug Trace Log: This displays debug trace logs if Debug feature is enabled in scenario.
- Pause Resume Log: This is used to view the logs for paused/resumed test schedule (if any).
- Execution Trace Log: This window displays total test cases along with number of executed, passed, and failed. This displays a table with having details for test cases and their corresponding results.
- Run Time Changes Logs: This window displays details for Runtime changes logs that include details, such as source, status, date / time, owner, applied by, and description.
- Stats: It shows the TCP connection information and is available if test is running currently.
- Health: This section displays the health of the appliance and Cavisson services.
- DB Monitoring: This is a powerful feature to measure the performance of each query contributing in a session execution. It provides complete monitoring of MSSQL queries with insights into SQL activity, wait statistics, databases, support services, Temp DB, and high availability. It enables a user to detect such queries, which are consuming more resources as compare to normal ones. Once identified, user can diagnose the issue and perform corrective measures
Clicking the Dashboard option displays the Dashboard with various sections. The detailed description of this window has already been provided.
Clicking the Test Run option displays the Test Run window. The detailed description of this window has already been provided.
Run Time Progress
This section is used to get the run time progress of scenario and run logic.
To view the runtime progress of scenario, go to View > Run Time Progress > Scenario.
This section is used to view the RunLogic runtime progress, which is configured via the script manager. To view RunLogic Progress, you need to enable the following option from Scenario > Group Based settings > Logs and Reports > Advanced.
It is enabled in Online Test Run:
On clicking this option, this displays the RunLogic RunTime Progress View.
This section displays two sub-sections, one is Scenario Group and other is RunLogic Tree. Scenario groups consist of group name, script used in the group, and number of users in that group. RunLogic Tree consists of blocks and flows inside that block. It also displays the pages inside the flow that are captured in the script. The details displayed with each page are – count, rate per second, and expected rate per second. User can user the check boxes to view/hide the details.
Following are the different fields, which are displayed in each flow:
On selecting this, all other checkboxes are selected automatically, such as Count, Rate, and Expected. The details are displayed in the RunLogic tree accordingly.
On selecting this, all flows are expanded and displayed in the RunLogic Tree.
Two types of views are present:
- Vertical view – For this, select the Show Vertical View check box.
- Block view – For this, do not select the Show Vertical View check box.
This displays the flows, which are not executing as per Expected rate, according to given percentage on the Highlight Threshold.
Virtual User Trace
This is used for tracing the users for different group(s). To view virtual user trace of a test run, go to View > Virtual User Trace. The Available Virtual User Trace window is displayed. It contains group name, user profile, type, script name/URL, and number of users.
Select a group and click the User Trace button. The User trace is displayed with information on session.
Any sequence of page clicks is grouped as a transaction. Transactions are added to measure the response time of a particular logical action performed by the user. User can see the detailed reports on click of a particular transaction link.
To view a transaction and its details, follow the below mentioned steps:
- Go to View menu and click the Transactions menu item. The Transactions Details page is displayed:
The Transaction Details page contains following information:
Transaction Criteria: A user can view All / Success / Failed transactions in this window by selecting the appropriate option from the list. Whenever the user performs drill-down by applying ‘Success’ filter, only the ‘Success’ column is displayed and ‘Fail’ or ‘Fail %’ columns are not displayed. In addition, whenever the user performs drill-down by applying ‘Failure’ filter, only the ‘Fail’ and ‘Fail %’ columns are displayed and ‘Success’ column is not displayed.
On applying ‘Success’ filter, the ‘Success’ column in displayed:
On applying ‘Failure’ filter, the ‘Fail’ and ‘%Fail’ columns are displayed.
Time Period: User can fetch the transactions for a specified duration, such as last 1/2/4/6/12 hours, days, week, months and so on. User can also apply custom time on selecting the Custom option from the drop-down list. On selecting Custom, two options are displayed – Absolute and Elapsed. Absolute time is the exact time. Elapsed time is simply the amount of time that passes from the beginning of an event to its end. In case of Absolute, enter start date, start time, end date and end time. In case of Elapsed, enter start time and end time. The specified date/time should be in range with current session. Click the Apply button post specifications.
The transaction details section contains following columns:
- Transaction Group: This contains a group of transactions executed on a page. A page is considered as a group. Each group contains a number of transaction inside brackets (). To view the transaction details, click the icon corresponding to a group. All the transactions inside that group is displayed. After clicking, the icon is changed to . To view all the transactions of all the groups, click the icon on the header.
- Transaction Name: It is the name of executed Transaction in Test Run. To view the transaction summary report, click the transaction name link.
- Min: This field shows the minimum time (sec) taken by the transaction in a sample period/ cumulative.
- Avg: This field shows the average time (sec) taken by the transactions in a sample period/ cumulative. Click the link to open the transaction detail report.
- Max: This field shows the maximum time (sec) taken by the transaction in a sample period/ cumulative.
- Std Dev: This field shows the standard deviation in the data (sec) in a sample period/ cumulative.
- Completed: This field specifies number of completed transactions in a sample period/ cumulative. Click the link to open the transaction instance report.
- Success: This field specifies number of success transactions in a sample period/ cumulative. Click the link to open the successful transaction instance report.
- Failure (%): This field shows the transaction failure percent in a sample period/ cumulative.
- TPS: This field shows the transaction completed per sec in a sample period/ cumulative.
- TPS (%): This field shown the percentage of transactions per second in a sample period/cumulative.
- Think time: This field shows the added page think time in transaction.
- Percentile: This field shows the percentile value of the transaction. For example – 50th, 90th , 95th and 100th.
|Enable transaction drill down report links check box at the bottom is for enabling/disabling drill down reports links.|
User can stop auto-refreshing of data in the transaction detail table by using the Pause button. To enable auto-refreshing of transaction data, click the Refresh button. User can also refresh the transaction data at any point of time by using the Refresh button.
- While opening Transaction Details, a pop up message is displayed “Transaction details loaded successfully”.
- While clicking the ‘Pause’ button, a pop up message is displayed “Transaction Auto refreshing stopped successfully”.
- While clicking the ‘Refresh’ button, a pop message is displayed “Transaction details data refreshed successfully”.
Filters in Transaction Details
To enable filters on transactions, user needs to click the Enable Filters button and click the Apply button. Once enabled, user can click the Disable Filters button to disable the filters.
There are following options for filtering transaction details:
- Transaction Name: User can filter the records based on the transaction name.
- Average Response time: User can specify a range of average response time and can get the filtered result.
- Failure percentage: User can specify failure percentage. Transactions falling in more that the specified failure percentage are displayed.
- TPS: User can specify minimum and maximum TPS value and can get filtered results based on that.
Downloading Transaction Details
User can download the transaction details in PDF, Word, and Excel format using the icons on the bottom left corner of the window.
Show Pie/Donut chart for Failed Transactions
User can view the pie/donut chart for all the failed transactions as well as individual failed transaction by using theicon on the top-right corner of the window.
The pie chart displays two sections. In one section, all transactions errors percentage are displayed. In another section, the specific transaction errors percentage are displayed.
User can perform following operation on the chart by clicking the icon.
- Change Chart: User can change the chart type to donut using the drop-down list.
- Show Chart: User can view various error results, such as overall, top 5, top 10, or top N. On selecting Top N, user needs to specify the number of top failure transactions to view.
Drill-Down Report from Transaction Detail Report
To see drill-down report of a particular transaction, click the Transaction Name link, and to see the drill-down report of all transactions, click the All Transactions link. When a user clicks the All Transactions link, the Transaction Summary report for all transactions is displayed.
There are following details on the transaction summary report page:
- Transaction name: Name of the transaction
- Script Count: Number of scripts in the transaction
- Tried: Total number of tries for the transaction
- Success: Number of success tries for the transaction
- Fail: Number of fail tries for the transaction
- % Fail: Percentage of fail tries for the transaction
- Min: Minimum duration of the transaction
- Average: Average duration of the transaction
- Max: Maximum duration of the transaction
- Median: Median of the overall duration of the transaction
- 80%tile: 80th percentile of the transaction duration
- 90%tile: 90th percentile of the transaction duration
- 95%tile: 95th percentile of the transaction duration
- 99%tile: 99th percentile of the transaction duration
In the Transaction Stats group, if a user opens the Transaction Summary Report from any graph of a transaction, and then applies UI filter, the results are displayed only for that transaction instead of all transactions.
Below is an example:
Applying Filter as Last 10 Minutes
The result is displayed only for that transaction.
Comparison in Transactions
User can view the comparison of various sets of transactions. To do this, the user first needs to apply comparison using the compare feature of the Web dashboard. Follow the below-mentioned steps to perform a comparison between transactions:
- Go to Analytics > Compare > Enable Compare.
- Enter the Measurement options and click Add. User can add multiple measurements, here we have added only one i.e. M1.
- Click Apply. The comparison is displayed on the graph panel.
- Go to View menu and click the Transactions menu item. The Transactions window is displayed.
- On the Compare Settings section, click Apply. The comparison details are displayed.
This section provides system logs, such as Kubernetes Logs, RBU Access logs, and peripheral devices logs.
This section displays the kubernetes logs that are captured by Kubernetes monitors. The details include – timestamp of the log, name, kind (such as Pod), reason, region, type, and message.
The description of the fields are as below:
- Name: It represents the name of the POD/Node. (the basic scheduling unit in Kubernetes).
- Kind: It represents the category of that particular Kubernetes attached.
- Reason: It represents the Status of the Kubernetes Kind. (If Healthy – Status is Active and vice-versa.)
- Region: Name of the particular Cluster group/Tier attached in the Monitor.
- Type: It represents the Alert Rule type.
- Message: Information attached with that particular Kubernetes data along with their URL.
RBU Access Logs
This section displays the details of RBU access logs.
Note: This reports failures of RBU. As there is no error, so it is displayed as blank.
Peripheral Device Logs
This displays the logs of peripheral devices. The details include – category, device name, timestamp, status, and description.
This shows all event(s) generated in current test run.
User can apply filters on the events. User can also pause/resume and refresh the event logs.
User can view logs, such as test output, debug trace logs, and pause/resume logs.
This shows the test output in browser as well as on panel. To view the test output, go to View > Logs > Test Output. The Test Output window is displayed.
This section displays the logs of user activities for pausing and resuming the test.
The following data is displayed in tabular format:
- Elapsed Time: The time since the test was running.
- User: The user who has performed the pause/resume operation.
- Action: Action performed, such as Pause / Resume.
- Duration: The pause test schedule, such as ‘till resumed’, ‘stopped’, or specified duration.
- Total Pause Time: The total cumulative time after each pause/resume operation.
- Current Schedule Phases: The current phase when the pause/resume was applied.
The user can perform following operations in this window:
- Pause Test Schedule
- Resume Test Schedule
- Close this Window
- Refresh the records
Debug Trace Log
This displays debug trace logs if Debug feature is enabled in the scenario. To view stats of the debug trace log, go to View > Logs > Debug Trace Log. The Debug Trace Log window is displayed.
This window displays the debug trace details, such as Script name, Time, User ID, Session, and message. From this window, the user can view the report, page detail reports, output, and script execution logs.
Execution Trace Logs
This window displays total test cases along with the number of executed, passed and failed. This displays a table with having details for test cases and their corresponding results.
Runtime Changes Logs
This window displays details for Runtime changes logs that include details, such as source, status, date/time, owner, applied by, and description.
This section displays the health of the appliance and Cavisson services.
To view appliance health, such as tomcat heap memory, CPU utilization vs load average, available memory, disk space utilization, and so on.
In this section, the user can see the details of all processes running on the server and can perform various actions. Apart from this, this section enables a user to run commands from UI (which earlier was limited to run from backend only.)
In Cavisson Services section, the details of running and stopped processes is displayed.
Name of the process. Click to view the details of the process.
Running (Green), Stopped (Red), Sleep (Grey)
Parent Process ID
Date and Time since the process is running
Elapsed time in format – Days hh mm ss
Number of threads
Number of child processes
Virtual memory in KB
Resident memory in KB
Percentage of CPU utilization
Number of open files
Note: In the All Processes section, the details of all the processes are displayed.
There are the following options:
To start a stopped service (Status: Red)
To stop a running service (Status: Green)
To view logs by file
To view logs by directory
To restart a service
To view the configuration of a service. The user can download the configuration file.
Using this section, the user can execute a command from UI, which earlier was limited from backend only. To do this, select the command from the Appliance Services drop-down list and click Execute.
Example: On selecting the ‘top’ command from the Appliance Services drop-down list and clicking the Execute button displays the command output in a window.