Using this section, a user can configure the following:

  • Derived Metrics
  • Monitors
  • Topology
  • Batch Jobs
  • Tier Group
  • Agent Config
  • Configuration Settings
    • Dashboard Settings
    • Multi Node Configuration
    • Show Vector in Title
    • Graph Tree
  • Color Management
  • Catalog Management

Derived Metrics

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 text area.
  • Vector name comes in square brackets [ ]
  • Vector name is optional as scalar graph doesn’t have vector names.
  • Format: {Group Name}{Graph Name}[Vector Name]
  • Example, for scalar graphs, user can enter group name and graph name in following format: {Vusers Info}{Running Vusers}

Derived Graph Rules

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


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

Add a Derived Graph

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

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


2. Specify the following derived graph details:

    • Report Group Name
    • Report Name
    • Report Description

If user selects graphs of scalar group, then All and Specified option is disabled. All and Specified options are enabled in case of vector graphs.

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.


Repeat steps 4 and 5 for more operations if required.

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.



If user selects 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/Update 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:

  1. 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.

2. This displays the Derived metrics in edit mode.

3. 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.


Using this section, a user can configure monitors and apply in an application to get the monitoring stats. It contains a list of monitor categories from where user can configure monitors (by expanding a monitor category) and add in the monitor group for monitoring an application. User can apply monitors for all tiers or for specific tiers.

Cavisson Product Suite has numerous monitors to measure metrics at both the system level as well as the application level. Cavisson has developed hundreds of monitors that are commonly and very heavily used by many of our customers.

Below is a list that provides high-level insight into the richness of our monitoring capabilities. Within each stat, numerous metrics are monitored and measured. Cavisson is by no means restricted to providing following mentioned monitors. We have worked with customers in past and have very rapidly developed required monitors on demand.

Monitors for Application Stats

Application Monitors



JDBC Pool Stats, JMS Queue Stats, JVM Stats, Thread Pool Data, Min Thread Constraint Data, Server Health Stats, Sessions Stats, Transaction Name Data


Cache Stats, Cached Connection Manager Stats, Global Request Processor, Server Info, Managed Connection Pool, Manager Stats, RAR Deployment, Request Processor, Servlet, Thread Pool, Work Manager Thread Pool


EAP JDBC Connection Pool, EAP Servlet Stats, EAP Sessions Stats, EAP Thread Pool


JDBC Stats, Servlet Data, Thread Pool Data, Session Stats, Liberty Monitor, Liberty JDBC Connection Pool Stats, Liberty Thread Pool Stats, Liberty Session Stats, Liberty JVM Stats, Liberty Servlet Data


Redis Activity Stats, Performance Stats, Cache Stats, System Stats, GC Monitor, GC Stats, DB Stats, Redis Latency stats, Redis Replication Stats, Slave Stats, RedisCacheStatsV2, RedisPerformanceStatsV2, RedisActivityStatsV2

Apigee  API

Deployment Stats, Services Stats by API, Services Stats by HTTP status


Map Stats, MultiMap Stats, Replicated Map Stats, Queue Stats, Cache Stats, Executor Service Stats, Topic Stats

HA Proxy

Frontend Stats, Backend Stats


Cache Stats, Cluster Stats, Cluster Node Stats, Service Stats, Storage Cache Stats


Thread Pool Stats


HDFS Cluster Stats, Data Node Stats, HBase Cluster Stats, HBase Region Server Stats, Resource Manager Service Stats, Resource Manager Queue Stats, HistoryServerJvm Stats, HistoryServerRpc Stats, HistoryServerUgi Stats

Giga Space DB Monitor

Gauges Stats, Histogram Stats, DB Stats, Log Stats, Timers Stats,

FCC Application

FCC Stats


Follower Stats, Node Stats, Store Stats

Elastic Search

Cluster Stats, Index Stats, Node Stats, Thread Pool Stats

Elastic Search Generic

Cluster Stats, Index Stats, Node Stats, Thread Pool Stats

Apache Solr

Solr Cache, Query Handler, Solr Update Handler Stats


Request Stats

GlassFish Application Server

JDBC Pool, Thread Pool


Queue Stats, Topic Stats, Service Time Stats


TcpStatesCount, TcpStats, SystemStatsExtended, ProcessDataEx, System Stats, Application Stats (MasheryClientConnectionData, MasheryDataSource


Jboss Data Grid

JDBC Pool Stats, Servlet Stats, Session Stats, Thread Pool Stats


ehCache Stats, JCache Stats


EC2, RedShift


Broker Stats, Consumer Stats, Producer Topic Stats, Broker Topic Stats, Producer Stats, Latency stats, and Topic Stats

Kafka Topic Replication

Kafka Topic Replication Stats

Apache Nifi

Connection Stats, Port Stats, Processor Stats, Controller Stats, Process Group Stats, System Stats, Counters Stats, Processor Stats, Flow Stats


Cluster Stats, Node Stats, Queue Stats

Spring Boot

Actuator Stats, Spring Boot Services Stats, Server Stats, Request Stats, Spectator Stats, Extended Actuator Stats


Nginx Plus Cache Stats, Nginx Plus Server Zone Stats, Nginx Server Stats, Nginx Plus Server Stats, Nginx Plus Upstream Server Stats 


Cache Stats, Serverzone Stats, Upstream Stats


Zookeeper Node Stats

Async Server

Async Server Message Stats, Async Server Service Stats

Spark Server

Spark Server Message Stats, Spark Server Service Stats

Camel Server

Camel Server Message Stats, Camel Server Service Stats

Windows based HTTP Service

HTTP Service Request Queue Stats Monitor, HTTP Service URL Groups Stats Monitor, IP HTTPS Global Stats Monitor

.Net CLR

.Net CLR Exceptions Stats Monitor, .Net CLR Interrop Stats Monitor, .Net CLR Jit Stats Monitor, .Net CLR Class Loading Stats Monitor, .Net CLR Locks and Threads Stats Monitor, .Net CLR Memory Stats Monitor, .Net CLR Remoting Stats Monitor, .Net CLR Security Stats Monitor, .Net Data Provider for SQL Server Stats Monitor

Other Windows based Monitors

App Pool WAS Stats Monitor, ASP .Net Active Server Pages Stats Monitor

Node JS Heap-GC

Heap used, Heap allocated, types of GC (SCAVENGE, MARKSWEEPCOMPACT), time taken by GC, different types of Heap Space Information (New, old, code, large object, and map space) 

Node JS Event loop

Latency of all events running in event loop, average/min/max time taken by event loop

Node JS Asynchronous Event Monitor

Events per sec for each category of event invocation (Ex. TCP connection, TCP read/write, Timer, File system read/write etc.), Event Execution Time, Delay in Event Execution

Node Server

Total requests, response time of all requests, time taken by all requests in network, time taken by server to respond on requests, input throughput (number of bytes read), output throughput (number of bytes write), status code count of all requests, request method type count (get/put/post)

Jetty Web Server Monitors

Jetty Thread Pool stats (Busy, Idle, Total, Min, Max thread counts Queue size) and Jetty Session stats (Current sessions, Max sessions, and Session rate)

GCP storage bucket permission monitor

Bucket Read Permission, Bucket Write Permission

Cloud Foundry

Cloud Foundry App Instances Stats and Cloud Foundry App Stats

Instance Health

Instance port status and instance ping response time


Used disk space, Free disk space, Key:value pairs emitted per second from map functions, Documents per second through map functions, 2xx, 3xx, 4xx, 5xx, GET, POST, PUT, DELETE, COPY, HEAD, Response Time (ms), Document Reads Per Second, Document Writes Per Second

Spring DM

ThreadPool, JDBCProvider


Service stats

GCP BigTable

bigtable table stats, bigtable cluster stats

GCP BigQuery

bigquery global, bigquery dataset

GCP Storage

Storage stats

GCP PubSub

Pubsub Subscription stats, pubsub Topic stats

GCP DataProc

Hdfs yarn stats, jobs stats


GCP Cloud SQL Stats – Reserved Cores, Reserved CPU Utilization (Pct), Disk Quota (GB), Bytes Used, Read Operations/Sec, Write Operations/Sec etc.

GCP Cloud Engine

GCP Compute Engine Stats – Dropped Bytes/Sec, Dropped Packets/Sec, Average CPU Utilization, Disk Read Bytes/Sec, Throttled Read Bytes/Sec etc.

GCP Data flow

GCP Dataflow Stats – Current Active vCPUs, Job Data Watermark Age (Sec), Job Elapsed Time (Min), Job Estimated Element Size (KB), Job System Lag (Sec) etc.

GCP Data Store

GCP Datastore Stats – API Request/sec, Index Writes/sec, 5th, 50th, 95th and 99th Percentile Read/Write Size Entities (Bytes) etc.

Monitoring Component Using Promethus

Kubernetes container stats, Overall summary stats, name space summary stats, Node Summary Stats

Hikari CP

Thread Pool Stats

Apache Active MQ

Broker stats, Destination queue stats, Destination queue topic stats

JBoss AS 7

Transaction stats,
Service Stats,  Prepared Statement Stats , Thread Pool Stats

JBOSS AS (JMX) Endpoint

JBOSS AS (JMX) Endpoint Stats

Azkaban  JMX

jobExecutor, executorManager, jobCallback, webExecutorManager, webTriggerManager, coordinator, executorContainer, webContainer


Source Stats, Sink Stats, Channel Stats


Kubernetes Container Stats


System Stats, Network Stats, Application Stats, Battery Stats, Process Stats, System Stats, WiFi Stats

Windows Peripheral Device Monitor

Monitor Stats, Report Stats

ASP.Net Monitors



Cache Stats


Akamai Transaction Stats


Apigee Transaction Stats

Alert REST Monitor

Level – 1 (Tier), Level – 2 (Server)

Mosaic Cart

Mosaic Cart Order Stats

Server Health Extended

Overall Stats, Server Stats


Jira Server Stats

Oracle Tuxedo

BBStats, Servers stats, Services stats


PS Stats, Memory Heap Stats, Threads Stats


Buffer Stats, Client Connection Stats, Client Request Stats, GC Stats, Memory Stats, Thread Stats

Kafka Burrow

Burrow Lag Stats

AWS Lambda

ACEC2Stats, ACLambdaStats

Data Power Extensions

IBM Data Power File, IBM Data Power System, IBM Data Power Network

Monitors for Database Stats

Database Monitors



SQL Stats, Time Model Stats, System Stats, Load Profile, Efficiency Percentages, Shared Pool Stats, Cache Sizes, Memory Stats

Postgres Database

Background Writer Stats, Database Activity Stats, I/O Activity Stats

ATG Oracle DB

ATG Order Stats (Driver Information and query are configured from JSON Configuration file)


Compaction Stats, Thread Pool Stats, Column Family Stats, Node Stats, Messages Dropped Stats


Buffer Pool Stats, Connection Stats, LOG Stats, Cache Stats, IO Activity Stats, Transaction Stats


Collection Stats, Server Stats, Database Stats, MongoDB Replication Info


Activity Stats, Efficiency Stats, Resource Usage Stats, Replication Stats


Server Stats, Perf Stats, IO Stats, Hardware Resource Stats, KPI Stats, Query Report

Windows based MS SQL DB (Non-Java based)

Microsoft SQL DB Access Methods Stats Monitor, Microsoft SQL DB Buffer Manager Stats Monitor, Microsoft SQL DB General Statistics Stats Monitor, Microsoft SQL DB Latches Stats Monitor, Microsoft SQL DB Locks Stats Monitor, Microsoft SQL DB Memory Manager Stats Monitor, Microsoft SQL DB Plan Cache Stats Monitor, Microsoft SQL Databases Stats Monitor, Microsoft SQL DB Wait Stats Monitor

Windows based SQL Server

SQL Server Access Methods Stats Monitor, SQL Server Buffer Manager Stats Monitor, SQL Server CLR Stats Monitor, SQL Server Databases Stats Monitor, SQL Server Executions Stats Monitor, SQL Server General Statistics Stats Monitor, SQL Server Latches Stats Monitor, SQL Server Locks Stats Monitor, SQL Server Memory Manager Stats Monitor, SQL Server Plan Cache Stats Monitor, SQL Server Resource Pool Stats Monitor, SQL Server Error Stats Monitor, SQL Server Statistics Stats Monitor, SQL Server Wait Stats Monitor

Couchbase DB Cluster Monitors

Couchbase cluster stats (Cluster memory stats and Cluster Disk stats)

Couchbase Node Monitors

Couchbase node stats (Node CPU stats, Node Memory stats, Node Disk stats, and Node Operations stats)

Couchbase Bucket Monitor

Couchbase bucket stats (Bucket disk stats, Bucket memory stats, Bucket Operation stats)

MySql Replication Group Monitor


Spanner DB

Spanner API Request/sec,  Spanner Uncompressed Request Bytes Received/Sec,

Spanner Uncompressed Response Bytes Sent/Sec, Spanner Request Latency (Sec), Spanner 5’th Percentile Request Latency, Spanner 50’th Percentile Request Latency,  Spanner 95’th Percentile Request Latency, Spanner 99’th Percentile Request Latency, Spanner Nodes,  Spanner CPU Utilization(PCT),  Spanner Session Count,  Spanner Used Size (MB), SpannerMethodStats, SpannerNodeStats, SpannerSystemStats


SAP HANA Users, SAP HANA Schema Memory, SAP HANA Peak Memory, SAP HANA Resident Memory, SAP HANA Memory Allocation, SAP HANA SavePoints, SAP HANA Backup, SAP HANA Memory Component, SAP HANA Network, SAP HANA Active Connection, SAP HANA Disk Usage.

Monitors for System Stats

System Monitors


Linux based System Monitors

Network Traffic, Memory Stats, UDP, System Load Stats, Stystem Stats AIX, IOStat, TCP States Count, TCP Stats, Process Stats, Process States Count, Socket Queue Stats, MPStat Linux, Network Delay, Open Files Stats, TCP Listen Queue Stats

Windows based System Monitors

Processor Stats Monitor, Window System Stats Monitor, Processor Information Stats Monitor, Logical Disk Stats Monitor, File System Cache Stats Monitor, Physical Disk Stats Monitor, Memory Stats Monitor, TCP IPv4 Stats Monitor, Paging Stats Monitor, Process Stats Monitor, Server Stats Monitor, TCP IP Network Interface Stats Monitor, Web Services Stats Monitor, CPU Load Monitor, Thread Stats Monitor

Monitors for Network Stats

Network Monitors


Store Uptime

Store POS Uptime(Minutes)

Network Interface

Operational Status, Current Bandwidth(Mbps), Received Throughput(Kbps), Transmitted Throughput(Kbps), Received Pkts Error/Sec, Transmitted Pkts Error/Sec, Received Pkts Discarded/Sec, Transmitted Pkts Discarded/Sec, Incoming Link Utilization(Pct), Incoming Link Utilization(Pct)

Network Delay

Network Delay (ms), Network Packet Loss (pct),  Network Delay Max Min Ratio

Network Device Env

Device Temperature(Celsius), Fan Status

Network Device Health

Uptime (Hours),  CPU Utilization (pct),  Memory Utilization (pct)

Fortinet Firewall

Up Time(sec), Active Sessions Count, CPU Usage (pct), Memory Utilization (pct), Total Hard Disk Capacity (MB), Current Hard Disk Usage (MB), Hard Disk Usage (pct), Network Bandwidth Usage (kbps)

Monitors for Other Technologies / Infrastructure

Other Monitors



Container CPU Stats, Container Stats, Container Disk IO Stats, Container Memory Stats, Container Network Stats, Container System Stats


F5 System Stats


ESXi Host CPU Stats, Host ESXi Host Disk Stats, EXSi Host Network Stats, ESXi VM CPU Stats, ESXi Host Memory Stats, ESXi VM Disk Stats, ESXi VM Memory Stats


Netty Server Monitor, Netty Access Log Stats

Access Logs

Access Log Stats, Log Pattern, Get Log File, Average Service Time Stats

Windows based Logs Monitors

Access Log Stats Monitor, Access Log Extended Stats Monitor, Access Log Extended v2 Stats Monitor, GetLog Monitors


Message Queue Stats, MQ Queue Stats, Channel Stats, Listener Stats, Manager Stats


Cluster Stats, File System Stats, Host CPU Stats, Host Network Stats, Container CPU Stats, Container Memory Stats, Host Memory Stats, Host IO, Host Device Stats, POD Network Stats, POD per name space, Pods per node, Service Stats and Status, Autoscale Config Stats, Container IO


Vault Storage Backend Stats, Vault Secret Engine Stats,  Vault Policy and Token Stats, Vault Auth Method Stats, Vault Internal Stats

Android Device Monitor

Android Battery Stats, Android Memory Stats, Android CPU Stats

To know the detailed description about Monitors, kindly refer the Monitors User manual.

For Cavisson monitoring capabilities, please refer the below link.


Topology is the arrangement of various elements (Tier, server, and instance) of an application. User can view the NetStorm topology (hierarchy of Tier, Server, and Instance) and only admin user can perform certain operation, such as add, delete, and update a topology. To do this, login as admin user, go to Configurations > Topology.

This page is divided into two sections – left and right. On the left section, topology is displayed in a hierarchical view of Tier, server, and instances. On the right pane, details of tier, server, and instance is displayed as per the selection.

Admin user can perform following operation in topology:

Add Topology

To add a topology, follow the below mentioned steps:

  1. Go to Topology on the left pane, right-click on the topology and click the Add Topology option.

2. The Topology Configuration section is displayed.

3. Specify the Topology name and click the Add button. The topology gets added and displayed in the topology list.

Tier (Cavisson) is added successfully in Topology (NS_Topology).

Server (NSAppliance) is added successfully in Tier (Cavisson) of Topology (NS_Topology).

4. User can edit the server configuration details and save them by clicking the Update button.

Delete All Topology

To delete all topologies, go to Topology section on the left pane, right-click on the topology, and click the Delete All Topology option.

A confirmation message is displayed. Click OK to confirm the deletion.

Add Tier

To add a tier, right-click on the topology and click the Add Tier option.

The Tier Configuration window is displayed. Enter the tier name, its description, and depth. Click Add to add the tier. The tier gets added. To update the tier information, edit the details, and click the Update button.

Delete All Tier

To delete all tiers, right-click the topology, and click the Delete All Tier option.

A confirmation message is displayed. Click OK to confirm the deletion.

Delete Topology

To delete a topology, right-click the topology, and click the Delete Topology option.

A confirmation message is displayed. Click OK to confirm the deletion.

Copy Topology

To copy a topology, right-click the topology, and click the Copy Topology option.

The Copy Topology section is displayed. Specify where to copy the topology, and click the Copy button.

The topology gets copied and displayed in the list of topologies on the left pane.

Rename Topology

To rename a topology, right-click on the topology, and click the Rename Topology option.

The topology name is displayed in editable mode. Rename the topology name from there.

Add Server

To add a server, right-click on a tier, and click the Add Server option.

The Server Configuration section is displayed. Specify the following details and click the Add button:

  • Server Properties: Enter server name and server display name.
  • CMON Properties: Specify the CMON installation status. Test and populate if installed. Specify the CMON home path, server OS type, and Java home path.
  • Advanced Properties: Specify SSH enable status. If enables, specify username and password.

Delete All Server

To delete all servers, right-click on a tier, click Delete All Server option.

A confirmation message is displayed, click OK to confirm the deletion.

Delete Tier

To delete a tier, right-click on a tier, click Delete Tier option.

A confirmation message is displayed, click OK to confirm the deletion.

Add Instance

User can add instance to a server. To do this, right-click on the server and click the Add Instance option.

The Instance Configuration section is displayed.

Specify the following details in the instance configuration section and click the Add button.

  • Instance Property: Provide instance name, its display name, and description.
  • Java Property: Select the instance type. In case of instance type as Java, select the JVM type, Java version, and GC log file path. User can specify the search pattern and can run command to get process based on given search pattern. User can also add/remove the search boxes.
  • JMX Property: It is enabled in case of instance type as Java. Specify the JMX port, user name, password, and connector URL.
  • Application Property: Specify the application name and BCI port. 

Add DB Instance

User can add database instance to a server. To do this right-click on the server and click the Add DB Instance option.

The DB Instance Configuration section is displayed:

The sub-sections displayed under DB Instance Configuration section is similar to the sections displayed under Instance Configuration section. Post specifying the details, click the Add button.

Delete All DB Instance

This section is used to delete all DB instance of a server. To perform this operation, use similar steps as used to delete all tier/server.

Delete All Instance

This section is used to delete all instances of a server. To perform this operation, use similar steps as used to delete all tier/server/DB instance.

Delete Server

This section is used to delete server of a tier. To perform this operation, use similar steps as used to delete a tier.

Batch Jobs

Batch Jobs are used to execute some jobs before test, during test is running or after test is over. It uses Check Monitor framework of NetStorm and CMON.

  • Batch Group is used to specify one or more batch jobs
  • Batch jobs may be run on different server machines
  • Batch Jobs run in pre-test run, during test run, and post-test run
  • Batch Jobs which runs during test have the option to repeat

Run Batch Job Event

NetStorm run Batch Jobs before, during and after test run. Following events are supported:


  • Before test is started


  • Start of the test
  • Start of the phase

After Test is over:

  • Completion of test

Before Test Run Starts (Pre Test Jobs)

In this case, batch jobs are started before start phase of the test. These batch jobs run along with other check monitors which are to be started before test. All are run together (parallel, not sequentially). All batch jobs and check monitors must pass for test to continue.

Timeout for batch jobs

NetStorm waits for the reply for batch job for a time defined. This is same as used by Check Monitors:

 Note User can set Timeout for running pre-test Batch Jobs and post-test Batch Jobs from Global Settings > Monitors tab.

Go to the Batch Jobs section under Monitors link on Scenario Setting window, the Batch Jobs section is displayed.

Select the scenario associated batch job group from the list.

Retry on failure

  • Retry count, retry interval of Batch Jobs are only valid if test is running from scheduler.
  • If user is starting test from command line or GUI to run now, then retry cannot be done.
  • Retry count is for all Batch Jobs used in a scenario. It is not per Batch Jobs, it is global.
  • Default Batch Jobs retry count is 0 means no retry.
  • Default Batch Jobs retry interval is 60 seconds.

These are set from Scheduler GUI. For access, click the Scenarios icon, and then click the Schedule Management option.

At Test Run

  • These monitors run while test is running.
  • It can run periodically or run once.
  • At Start of the Phase, batch job runs for specified Phase.

After Test Run is over

In case if after test run is over,

  • It runs only once.
  • NetStorm needs to wait for some time to collect data from Batch Jobs.
  • After that time, kill the monitors which are still running. Timeout is defined using some settings. Default is 600 seconds (10 minutes). For example, POST_TEST_CHECK_TIMEOUT <timeout>

Batch Job Group Management

It has the following options:

  • Batch Group Name
  • Batch Group Description
  • Modified Date
  • Number of Batch Jobs

Adding a Batch Group

  1. Click the Add button.
  2. Enter the Batch Group Name and Batch Group Description.
  3. Click the Save button.

Editing a Batch Group

  1. Click the Batch Group Name. All batch Jobs of the selected batch group is displayed.
  2. User can update the description of the Batch Group and can also add, update, and delete the batch jobs under that Batch Group.

Adding a Batch Job

  1. Click the Add button in the Edit Batch Group window.
  2. Enter the following Batch Job details:
    • Tier name
    • Server name
    • Batch job name
    • Batch program name
    • When to run the batch job
    • Repeat criteria of batch job
    • End event criteria
    • Success criteria mode

  1. Click OK to add the batch job to a batch group.

Input Parameters for a Batch Job

Run Batch Job Phase Name Repeat


Batch Job

Periodicity End Event End


Phase Name

Before Start Of Test NA Never NA NA NA NA
At StartOf Test NA Never NA NA NA NA
-do- NA Run Periodic <HH:MM:SS> Till test is over NA NA
-do- NA -do- -do- Till Specified phase is complete <value> NA
-do- NA -do- -do- Continue specified no of Execution NA <value>
OnStartOfPhase <PhaseNam> Never NA NA NA NA
-do- <PhaseNam> Run Periodic <HH:MM:SS> Till test is over NA NA
-do- <PhaseNam> -do- -do- Till Specified phase is complete <value> NA
-do- <PhaseNam> -do- -do- Continue specified no of Execution NA <value>
At End Of Phase <PhaseNam> Never NA NA NA NA

Input Parameters for a Batch Job

Editing a Batch Job

  1. Click the Batch job in the Batch Group window.
  2. Edit the Batch job details and click OK.

Tier Group

Clicking the Tier group option displays the Tier Group window. The tier groups are displayed after selecting the topology from the list.

This section lists all the created groups within the selected topology and provides following information about those groups:

  • Group Name: Name of the Tier group.
  • Group Define For: The module for which the group is defined. It could be – NDConfig, Monitors, or both.
  • Type: It is the method used to identify the tier groups. It could be ‘list’ or ‘pattern’.
  • Definition: It is the list of tiers (separated by comma), which are part of tier group.
  • User Name: Logged in user name.
  • Last Modified: Date and time when the group was created or last modified.

Creating a Tier Group

To create a tier group, follow the below mentioned steps:

  1. On the tier group window, click the Add Tier Group icon . This displays the Add Tier Group window.

2. Specify the name of the group.

3. Specify whether the group is defined for NDConfig, Monitors, or both.

4. Select the type either list or pattern. In case of ‘list’, user needs to select the tier(s) from the list. In case of pattern, user needs to define a pattern of regular expression. Upon clicking the Test button, this displays all the matching tiers in the list and applies as part of tier group.

5. Click the Save button, this adds the tier group in the list.


  • Once a tier group is created, user can modify it using the Edit icon . To delete a tier group, select the tier group from the list and click the Delete icon .
  • Only admin user is authorized to add/edit and delete Tier groups.
  • ND Config UI and Monitor UI uses tier groups.
  • If any tier is grouped for a module either NDConfig or Monitors, that particular tier cannot be included in another tier group for same module. However, it will be available for other module.

Agent Config

ND Configuration window is divided into two panes – left pane and right pane. Left pane consists of a menu from where, on clicking it, the corresponding details are displayed on the right pane. From right pane, user can configure the application, profile, and instrumentation profile. User can also view the complete list or top five topologies from the Topology list section. Application list, profile list, and topology list is displayed on right pane by default. This can also be achieved by clicking the Home menu on the left pane.

Left Pane/Menu

  • Home
  • Application
  • Profile
  • Topology
  • Instrumentation Profile Maker
  • Instrumentation Finder
  • NDE Cluster Configuration
  • User Configured Settings
  • Audit log

Right Pane

  • Application list
  • Profile list
  • Topology list

To view detailed description of Agent Config, refer the NetDiagnostics – Configuration Interface User Manual.

Configuration Settings

Using this section, a user can configure the following:

  • Dashboard Settings
  • Multi Node Configuration
  • Show Vector in Title
  • Graph Tree
  • Log Monitoring Settings

Dashboard Settings

Dashboard settings is used to configure the following dashboard settings:

  • Logs
  • Percentile
  • Transaction Details
  • Favorite Settings
  • Graph Settings
  • Graph Tree Settings
  • DB Settings

To open the dashboard settings window, go to Configuration > Configuration Settings > Dashboard Settings.

Using the Dashboard Settings window, the user can configure the debug level via Logs tab, percentile settings for percentile graphs via Percentile tab, percentile settings for transactions via Transaction Details tab, favorite settings via Favorite Settings tab, graphs gradient settings via Graph Settings tab, and graph tree refresh settings via Graph Tree Settings tab.


This tab is used to configure the debug levels for logs. User can select the debug level from 0 to 4. This defines information level to be stored at trace level. The default level is 0, which contains the most basic information. Further levels (i.e. 1, 2, 3, and 4) contain more verbose information as the level increases.

To configure the debug level of server logs and dashboard server logs, select the debug level from the debug level section. For module level debug, first select the module name and then select the debug level for that module.

To save the configuration in config file, select the Save in Config File check box and click OK. This makes the settings permanent and applicable for every session. To apply the settings for the current session only, click the OK button (without selecting the Save in Config File check box). To cancel the settings, click the Cancel button. In the similar way, this operation can be performed for other tabs also, such as Percentile, Transaction details, Favorite settings, and so on.


A percentile is the value of a variable below which a certain percent of observations fall. So the 20th percentile is the value (or score) below which 20 percent of the observations may be found. The pth percentile is a value so that roughly p% of the data is smaller and (100-p) % of the data is larger. Percentiles can be computed for ordinal, interval, or ratio data.

To configure the percentile view for a percentile graph, click the Percentile tab on the Configuration Settings window. The Percentile setting section is displayed.

The default percentile views are displayed. Select the percentile to view from the drop-down list. To select all percentile views, select the select All check box. To view default percentile, select the Select Default Percentiles button. To save the configuration setting in the Config file, select the Save In Config File check box. Apply the settings by clicking the OK button. To cancel the settings, click the Cancel button.


In case user selects 90, 85, 80, and 70 as percentile view and apply the settings.

The percentile graph is displayed with the selected percentile views.


To view the percentile views, open a graph and change the graph type to percentile graph from the widget settings. Once the percentile graph is displayed, double-click on the graph to view the lower pane. The percentile views configured are displayed in the lower pane.

Transaction Details

User can also configure percentile views for transaction as configured for graphs in the above section. To configure percentile view for transactions, click the Transaction Details tab on the Configuration Settings window. The Transaction Details section is displayed.

Provide the following inputs:

  • To view the transaction details in Auto mode, select the Transaction Details in Auto Mode check box.
  • Select the Allow Percentile Data Creation for Transactions check box to enable the percentile data creation for transactions.
  • To view the default percentiles, click the Select Default Percentiles User can select the percentile to view from the drop-down list.
  • User can also select all percentiles to view by using the Select All check box.
  • User can also provide refresh time interval for transaction percentile and threshold for transaction details pagination in the respective input areas.
  • To save the configuration setting in the Config file, select the Save In Config File check box.
  • Apply the settings by clicking the OK button. To cancel the settings, click the Cancel button.


In case user selects 99, 95, 90, and 80 as percentile view for transactions and apply the settings.

The selected percentile views are displayed in the Transaction summary report.


To view the Transaction summary report, go to View menu, click the Transactions menu item. Then, click the All Transactions link or a particular transaction link.

Favorite Settings

User can specify whether to apply the default time of favorite or the time specified in the current view. User can also specify whether to load favorite with compare settings. It also provides a feature to enable dynamic web dashboard. For these settings, user needs to click the Favorite Settings tab on the Configuration Settings window. The Favorite Settings section is displayed.

If user selects the Load Graph Time Settings From Favorite check box, the graph time settings are loaded from favorite. If user does not select this check box, no time of the favorite is saved and system considers the last saved value (default value). For example, if the current view of the favorite is last 1 hour and default view is last 4 hours. Then, on selecting this check box, the favorite current value i.e. last 1 hour is saved and on not selecting this check box, no value of the favorite is saved and system takes the last specified value (default value) i.e. last 4 hours on loading the favorite.

If user applies comparison and save it as favorite, then, on selecting the Load Favorite with Compare Setting check box, the favorite is loaded with compare settings.

Dynamic Web dashboard feature allows a user to view the most recent updates in the graphs. User can enable dynamic web dashboard by selecting the Enable Dynamic WebDashboard check box. On enabling this, the graphs are displayed based on the runtime changes.

User can also specify Refresh Interval For Dynamic WebDashboard in minutes.

To save this setting in configuration file, select the Save in Config File check box. Click OK to apply the settings.

Graph Settings

User can also specify whether to apply gradient color on chart types and up to how many decimals the value to be displayed on y-axis. For this, user needs to click the Graph Settings tab on the Configuration Settings window. The Graph Settings section is displayed.

Here, user can apply gradient color settings for the graphs, configure the decimal digits, and can enable/disable crosshair and gridline settings.

In the Advanced Settings section, the user can configure the following settings:

  • Shared Tooltip Threshold: To enable multiple tooltips for different graphs in a single widget.

  • Series Boost Threshold: To decrease the width of graphs when given threshold for number of graphs is crossed.

  • Graph Scaling: To enable the scaling on widgets so that the most lower value graphs become visible in front of higher value graphs.

  • Lower Panel Pagination and Threshold: To enable the pagination in lower panel of Dashboard and threshold of the pagination.

  • Scaling Threshold: To define the graphs on which scaling is applied. It allows to scale graph using different threshold value.

Example: If scaling threshold is 20 and consider max value of graph is 100 then all the graphs having values lesser than 100/20 are scaled. All the graphs having values greater than 100*20 are scaled.

Scaling threshold value in Dashboard:

  • Inter-widget Delay Time (ms): Whenever a new sample is arrived on a production test, then graphs are updated one by one with the given delay.
  • Enable Monochromatic Color: To enable monochromatic colours in Advance settings.

Example: Applied gradient color on Donut chart.

To configure the decimal digits to be displayed with graphs, specify the value in the Show Decimal Digits text box.

Example: Crosshair and Gridlines

To enable crosshair and gridlines, select the respective options. On mouse hover, crosshair is displayed.

In the below figure, decimal digits (3), grid lines, and crosshair is displayed.

Graph Tree Settings

User can specify whether to refresh graph tree on the occurrence of run time changes. For this, user needs to click the Graph Tree Settings tab on the Configuration Settings window. The Graph Tree Settings section is displayed.

DB Settings

In this section, the user can configure the query timeout (in seconds).

Multi-Node Configuration

The user can configure Multi DC environment through UI and can start node server from there. The user can add, edit, delete, update, and configure multiple slaves and can change master DC. By using the Apply button, the user can start the node server.

The user can perform the following action on the Multi-Node Configuration window:

Add a Node

To add a node, the user needs to provide the following details and click the Add button:

  • Node Name: This is the name of the node. It must start with an alphabet. Maximum length is 32 characters.
  • Session Number: This is the number of the session. It is a numeric and maximum length allowed is 32.
  • IP Address: It is the IP address of the machine. It is a numeric field with allowed characters are 11.
  • Port: It is the port of the machine. It is a numeric field with allowed characters are 7.
  • Protocol: Select the protocol either HTTP / HTTPs from the drop-down list.
  • Master: If this is a master node, select the ‘Master’ check box.
  • Product Type: Select the product type, such as NetDiagnostics, NetStorm, NetVision, and so on from the list.

Delete a Node

The user can delete master and slave DC by clicking the Delete button. However, if user deletes the master DC information, then it must make at least one DC information from table as master before using the Apply button.

Edit a Node

The user can edit the DC information by clicking the Edit button and can update DC information as per the requirements.

Save the Node Details

On clicking the Save button, the DC details are saved in the records.

Apply the Configurations

On clicking the Apply button, the node-server starts running on the port as provided by the user.

Run Aggregator on Same Machine

With this option, if the user clicks the Apply button, the node server runs at the backend for the machine on which it is logged in. This option is displayed on selecting the Master check box.

Run Aggregator on Other Machine

When user clicks this option, there will be additional option to specify the machine on which we need to run node server.

Show Vector in Title

This feature is used to view graph with breadcrumb, such as last 1, 2…5. To view an example of this, first select a graph form the graph tree view. By default, graphs are displayed last 2 breadcrumb. For example – NSAppliance>Tomcat-Appliance.

Now, go to Configuration > Configuration Settings > Show Vector in Title, and select the level of Breadcrumb, such as Last 3.

Then, the selected graph is displayed with last 3 breadcrumb. For example – Cavisson>NSAppliance>Tomcat-Appliance.

Graph Tree

This feature is used to specify the position of the group in the graph tree. To use this feature, go to Configuration > Configuration Settings > Graph Tree. There are three options available there:

Group at Beginning

Upon selecting this option, group position is at the beginning in the graph tree. This is the default option selected.

Group at End

Upon selecting this option, group is positioned at the end. Below is an illustration:

Group at N Level

Upon selecting this option, user can specify at which level to position the group. For example, if user specify the group level as two.

The groups are positioned at level 2 in the graph tree. Below is an illustration:

Color Management

Color Management feature enables a user to have specific color of the graphs using the hierarchy structure of the graphs. Using this feature, the graphs assigned in a particular hierarchy are displayed with different colors. To use this functionality, follow the below mentioned steps:

  1. Go to Configuration menu and click the Color Management menu item. The Color Management window is displayed.

  1. Select the hierarchy levels. Here, user needs to define the color by hierarchy level. There are drop-downs based on the maximum number of hierarchical levels in the test. Each drop-down is having “Any” and meta data name of that level in whole Test. In case “Any” is selected at any level, then next drop-down displays all options available on that level otherwise it displays specific to previous selection.

3. Select whether to include graphs in color management. On selecting this, different graphs are displayed with different colors. For example, if user selects Any > Any > Instance in the hierarchy level then all graphs of same instance is displayed with same color. However, on selecting the Include Graphs option, different graphs of the same tier are displayed with different colors.


Case 1: Hierarchy Level – Any > Any > Instance (without selecting include graph option)

In this case, Elapsed time and CPU graphs of same instance is displayed with same color.

Case 2: Hierarchy Level – Any > Any > Instance (with selecting include graph option)

In this case, all graphs of same instance are displayed with different colors.

Catalog Management

Catalogue management provides a common platform for the selection of graphs and storing them as a catalogue. Catalogue means the collection of items in a systematic manner. Here, collection of items is the collection of graphs. This catalogue is saved at a common place, so that it can be used with different modules of Web Dashboard, such as Favorites, Alert, Template, and Pattern Matching by just importing the catalogue as per requirements.

Key Features:

  • User is able to save any type of graph (Normal / Derived).
  • User is able to save any series type (Simple / Percentile / Slab Count).
  • User is able to select any chart type (Line / Bar / Pie / Area / Stacked Area / Stacked Bar).
  • User is able to add / delete a catalogue.

Accessing Catalogue Management UI

To access the catalog management UI, follow the below mentioned steps:

  1. Go to Configuration menu and click the Manage Catalogue

  1. This displays the Catalogue Management window. It contains two tabs – Manage Catalogue and Add / Edit Catalogue.

Manage Catalogue

This section contains a list of catalogues with details, such as catalogue name, graph type, description, created by, created on, and actions.

From the actions column, user can Edit or Delete a catalogue. Upon clicking the Edit icon, the created catalogue is displayed in edit mode where user can make changes and overwrite the catalogue settings.

Add / Edit Catalogue

To add a catalogue, go to the Add /Edit Catalogue section and provide the following details:

Catalogue Detail

It contains catalogue information, such as Catalogue Name and Catalogue Description:

Chart Detail

The Chart details includes the Selected Metric type provided by the user. By default, it is selected to be as Normal while adding a new Catalogue.

Metric Types:

  1. Normal
  2. Derived
Normal Metric Type

Derived Metric Type

Here, another option of Derived Metric Name under Select Graphs is displayed where user needs to provide the Derived Name of the added derived Graphs.

Select Graphs

It contains the area to select graphs. If graph type is Normal, then following window is displayed where user can select graphs in normal mode (without performing any mathematical operation unlike derived graphs).

If graph type is Derived, then user can apply some mathematical operations to get the Derived Graph as required.

If the selected group is vector based, there are two options as follows:

  1. All
  2. Specified

For “Specified”, a new window is displayed with following tabs:

  1. Specified Indices Selection
  2. Advanced Indices Selection

In case of “Specified” Indices selection:

In case of “Advanced” Indices selection, user needs to select the Tier, Server, and Instance:

Tabular View

This displays the graph data in tabular format. We select the normal or derived graph from the above graph area and then on clicking this button, that graph is added in the table. It contains following fields:

  1. Graph/Derived Name
  2. Metrics/Indices_Derived_Formula
  3. Metric Type
  4. Action

Table row also has the option to delete the graph, inside the Action.

In case of Normal graph type:

In case of Derived graph type: