Analytics

In this section, the user can access the following features of Dashboard:

• Compare
  • Enable Compare
  • Disable Compare
  • Update Compare
  • Scenario Difference
  • Script Difference
  • Server Signature Difference
• Derived Metrics

Compare

Compare option is used to compare values of two test runs/sessions. Using compare feature of Dashboard, current running test/session can be compared with existing baseline test run/session. Graphs can be compared both in online and offline modes. In online mode, two graphs are displayed, one static baseline graph and one current running test run/session graph. Compare is allowed only for single graphs. User can set a baseline test run/session number from the existing sessions. User can change or remove baseline test run/session number.

Key Points in Comparing Test Runs/Sessions

There are following key points in comparing test runs/sessions:

• Current test run/session can be compared with other test runs/sessions respectively.
• Different instances of current test run/session can be compared.
• User can compare same or different instances of different test runs/sessions.
• Current test run/session is always included in compare. No need to select current test run/session in compare window.
• If compare is done and user changes the time from Graph Time or View by phase, then data changes in all graph panels for current test run/session only.

Enable Compare

User needs to follow the below mentioned steps for comparing test runs/sessions:

1. Go to Analytics > Compare > Enable Compare. The Compare Settings window is displayed.

1. In the Advance Settings, section, specify whether to include current test run/session or not using the Include Current Test Run check box or Include Current Session It is used to include/exclude current test run/session in compare. The current test run/session is included by default.
2. Enter the Measurement Name in the specified box. Measurement Name is a unique name which is assigned for the test run measurement. It is an alias of one compare settings. Measurement name can be maximum of 25 characters. All characters are allowed except ‘|’ as it is used as separator between fields. Also it can’t be duplicated.
3. In case of NetStorm, select the Scenario and Test run.
4. Select the time duration from Preset. On selecting Custom, two options are displayed – Absolute and Elapsed. 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.
5. Next, select the Color by clicking on it. By default, there are colors defined for each compare setting but user can change the color of any compare setting.
6. Then, click This button adds values of compare settings from input fields to table. Delete button, at right side, is used for deleting the data added regarding a particular session.
7. Click the Apply After comparison, graphs are displayed.

Operation on Compared Graphs

Following operations can be performed on compared graphs in Dashboard GUI:

• Zoom: User can apply zoom on the compared graph panel.
• Drag single graph: If user drags single graph on compared graph, then that graph is compared if graph is present in both test run. If graph is not present in baseline test run, then an alert message is displayed “Graph is not present in Baseline Test Run. So cannot perform comparison”.
• Drag multiple graphs: If user drags multiple graphs (All graphs of a group) on compared graph then only first graph is compared.
• Load Favorite: If favorite is loaded on compared graph then only first graph of each panel of favorite is compared with baseline Test Run.
• Change Color: User can change color of Baseline from lower panel.

Compare Changes for Auto Scaling

This feature allows a user to compare test runs even if the indices are not available in measurements. In this case, indices are mapped with indices of other measurements.

To use this feature, we are representing an example.

Graphs of first test run

In this test run, Indices for Sys Stats Linux Extended are:

• Cavisson>Ubuntu54
• Cavisson>NSAppliance
• GUIDevTier>Ubuntu52
• GUIDevTier>Ubuntu51

Graphs of second test run

In this test run, Indices for Sys Stats Linux Extended are:

• Cavisson>Ubuntu54
• Cavisson>NSAppliance
• QATier>Ubuntu47
• QATier>Ubuntu48

Now, on applying compare between these two test runs, the following window is displayed:

In the highlighted section, it can be seen that if indices are not available in measurements then system maps it to other indices.

Post Compare Actions

User can perform following actions post compare operation:

• Disable Compare
• Update Compare
• View Scenario difference
• View Script Difference
• View Server Signature Difference

Disable Compare

This feature is used to disable the comparison applied in the test runs. On clicking Disable Compare menu-item, the graphs in the panel is displayed in its original form (without comparison).

Update Compare

This feature is used to update the comparison parameters, such as time, addition/removal of measurements, and so on.

Scenario Difference

This displays scenario difference between current and baseline test run. To view the scenario difference, the user first needs to compare two test runs via Analytics > Compare. Once compared, go to Analytics > Compare Scenario Difference. The Scenario Difference window is displayed that provides the scenario difference between two test runs. Click the Close button to close the window.

Script Difference

This displays script difference between current and baseline test run. To view the script difference, first user needs to compare two test runs via Analytics > Compare. Once compared, go to Analytics > Compare > Script Difference. The Script Manager window is displayed that provides the script difference between two test runs.

Server Signature Difference

This displays server signature used in current test. To view the server signature difference, go to Analytics > Compare > Server Signature Difference. A window is displayed showing the Server Signature Difference.

Derived Graph

Derived graphs are those graphs that are derived from two or more graphs by applying some formulas provided by user. Sometimes, there is a requirement to do some analysis on reports, and for that, some calculations need to be done on reports data to get some derived data. For example, if average of 3 reports is needed, in that case, derived data is required by adding results of 3 reports and divide it by 3. So, derived data is something like extracting new information from existing one by performing some calculations on existing data.

Before adding a derived graph, in custom metrics, user should be aware about options in derived graph window, format of expressions, and derived graph rules.

Options in “Add Derived Graph” window

There are following options in “Add Derived Graph” window.

• Operators like +, -, /, *, () are used in formula to add derived graph.
• On the lower side, a text-area is shown where complete formula is shown and it is editable to that user can modify the formula as per requirements.
• User can manually type the formula or copy paste in a given format. This format is explained in separate section.
• User can add the derived graphs in new group or in existing group by defining the Report Group Name.
• All Derived Graphs nodes are added under custom metrics node.

Format of Expression

• Group name and graph name comes in between curly brackets { } in the text area.
• Vector name comes in square brackets [ ]
• The vector name is optional as the scalar graph doesn’t have vector names.
• Format: {Group Name}{Graph Name}[Vector Name]
• Example, for scalar graphs

User can enter the group name and graph name in the following format: {Vusers Info}{Running Vusers}

Derived Graph Rules

If all graphs included in an expression are scalar, then the output of this expression is scalar. Means, it creates one derived graph.

Example:

{Vusers Info}{Running Vusers} + {Vusers Info}{Active Vusers Info}

Add a Derived Graph from Menu

User needs to follow the below-mentioned steps for adding a derived graph:

1. Go to Analytics > Derived Metrics. The Add Derived Graph(s) window is displayed.

2. Specify the following derived graph details:

1. • Derived Group Name: Must start with alpha. Max length is 32. Allowed characters are alpha and numeric.
   • Derived Metric Name: Must start with alpha. Max length is 32. Allowed characters are alpha and numeric.
   • Derived Metric Description: Must start with alpha. Max length is 128. Allowed characters are alpha and numeric.

3. Select the Group Name and Graph Name from the drop-down list and click Add Graph button.

4. Select the operator from the list of operators based on the operations performed on the derived graph. The basic operators are displayed on the left side and advanced operators are displayed on the right side of the window.

5. Again, add some more graphs required for calculation. For this, select the Group Name and Graph Name from the drop-down list and click Add Graph button.

6. After adding the required graph information and operators, the expression would look like as displayed below.

7. Click the Add button. The derived graph is displayed on the widget and is also added in the custom metrics. Expand the graph to have a better view.

Specified

If the user selects the Specified option, the Specified Indices Selection window is displayed. There are two tabs displayed – Specified and Advanced. User can select the specified graphs from this section using the Add button.

On clicking Advanced tab, user can add some advanced options for adding graphs.

Select All or other options (Tier, Server, Instance, and Business Transactions). Specify a pattern for the graphs to be added and click Test. A list of tiers is displayed.

Click Apply to apply the settings. The specified pattern is displayed in the Specified text box.

Click the Add Graph button. The graph string is displayed. Click the Add button to generate the derived graph.

The derived graph is displayed. The derived graph is added in the custom metrics with the following options:

• Open All Members
• Merge with Selected panel
• Open Derived Members
• Merge Derived Members
• Edit Derived Graph

Edit a Derived Graph

User can also edit a derived graph to make further modifications. To do this, follow the below mentioned steps:

• Go to Custom metrics section, then go to Metrics > Group > Report level. Right-click at the report level and click the Edit Derived Graph option.

• This displays the Derived metrics in edit mode.

• Update the details as per requirements and click the Update button.

Open all Members

Using this option, it opens all the individual nodes at individual panels:

Merge with Selected Panel

Using this option, all the members are merged in a selected panel.

Open Derived Members

Using this option, all the indices of members that are involved in the creation of derived graph are displayed on the graph panel in separate widgets:

Merge Derived Members

Using this option, all the derived members are merged on the selected panel.

The options – Merge with selected panel, Open derived members, and Merge derived members are also available at graph level.

Global ‘View By’

A user can apply Global ‘View By’ in case of derived graph in Multi DC.

Adding a Derived Graph from Standard Tree

The user can also create a derived graph from a standard tree. When a user right-clicks a metrics from the standard tree (on the left) and selects the ‘Add Derived Graph’ option, the group name and the graph name is automatically displayed in a drop-down menu as selected and the user can create derived graph from there.

Selecting ‘Add Derived Graph’ option

Auto Filled ‘Group Name’ and ‘Graph Name’