Release Notes 4.1.15.34

8th July, 2019 – Release Notes 4.1.15.34

Acronym List

Below is the list of acronyms used in this document.

File Size Specifications

Below is the list of file sizes for each component required for installation in this release.

New and Enhanced Features in 4.1.15

Common Implementation

Unified Dashboard / Single UI Dashboard

Cavisson has provided end-to-end capability within a single Dashboard where the performance users can navigate issues faced on the browser and can navigate to method level issues and corresponding logs.  This enhancement takes care of integrated UI for various Cavisson Products, such as NetDiagnostics, NetVision, and NetForest. All the menu options are restructured and seamless integration of multiple products have been done.

Re-engineered NetHavoc

The NetHavoc feature has undergone multiple changes. Most importantly, the look and feel of the UI is changed. Other changes include the following:

1. The feature gets its own separate window and has a Report section in which a user can view usage, types, and summary of the havocs at one place.
2. The multiple menu items are more comprehensive and include detailed and organized options.
3. A user can now view the historical triggered injections that include details, such as how many time commands are triggered, how many failed, how many passed, how many are in waiting state, and so on.
4. An option is provided to stop the running faults on the Server.
5. The fill up disk fault is more accurate now and does not include the space consumed by background processes. Suppose, if the user has injected fault to increase disk space up to 80% and some other processes get started while the fault duration, then the total accumulated value is ‘80’ without adding the disk space consumed by the background processes.
6. An option is provided where the user can see the fault values along with added fault type.

NetStorm

Script

Stopping a Test with Un-Executed Breakpoints: If a user applies multiple breakpoints in a script and stops the debug trace by clicking the ‘Stop Debug Test’ button before execution of all the breakpoints, the test is stopped immediately and further breakpoints are not executed. The same is reflected in debug trace logs.

Search Option While Adding a C API: While adding a C API, a user can search the API name in the dropdown list by typing instead of manually searching for the same.

ProtoBuf: Response Body in XML Format: Protobuf Response body is now decoded in xml format, which earlier was printed in plain format.

ProtoBuf: Encode and Decode APIs: ProtoBuf APIs to encode and decode data is provided that helps a user to:

• Encode data into protobuf format
• Decode data from protobuf encoded data

Java Message Service (JMS) API (IBMMQ, Kafka, and Tibco): Java Message Service (JMS) is an API that provides the facility to create, send, and read messages from one application to other. Cavisson supports JMS APIs (IBMMQ, Kafka, and Tibco) producer and consumer scripts through NetStorm Script Manager. The configuration set via JMS API window is reflected in the flow file of the script.

The user can add IBMMQ, Kafka, and Tibco APIs by selecting the same from JMS type drop-down list. Each JMS type is further categorized into Producer and Consumer type script. Producer / Consumers are the virtual users, which produces or consumes the messages by using a queue.

Scenario

Display of Message after Pausing a Test: Now, in ‘Schedule By’ scenario, if any user is in ramp-up or ramp-down phase and wants to pause the test, then a message is displayed as:
Pausing test run for ‘<time>/<indefinite_time>’ at <time> …
“Please wait for some time as some users are in initializing stage and it will take time to pause”
In addition, if no user is in ramp-up or ramp-down phase, then a message is displayed as:
Pausing test run for ‘<time>/<indefinite_time>’ at <time> …
Any additional message is not displayed if these is no user(s) in ramp-up or ramp-down phase.

‘Add Recorded Host’ Feature: Support for ‘Add Recorded Host’ setting is provided from Scenario UI in Server Mapping within Advanced Setting. The user can enter a Recorded Host in a text box and select Scheme type from drop-down list. Then, those entries are reflected in a table.

GIT Versioning: Option in GIT Settings to Disable GIT Configurations: A check box is provided in Git Setting window from where the user can enable / disable Git configurations.

When Git configuration is enabled, then Version Control, Git Pull, Git Commit, and Git Refresh is displayed in GUI else, Version commit and Version log is displayed.

‘Mark and Measure’ Feature: Support for ‘Mark and Measure’ feature is provided in NVSM (within the ‘Advanced’ tab in ‘Global Settings’ window) and in Scenario (within the ‘Advanced Settings’ in ‘RBU’ Settings). This feature enables a user to decide which parts of scripts are to optimize, and instrument those parts of scripts with the User Timing API. From there, the user can access the results from JavaScript using the API, or view them on Chrome DevTools Timeline Recordings.

User Defined Access: A user can now edit or update a user-defined access. Along with this, the user can now edit or delete Upload BW (kbps), Download BW (kbps), V.42 Compression and Access Name from Access in User Profile.

‘Default’ option in Script Parameter of Group Based Settings: The ‘default’ option in Script Parameter of Group Based Settings is provided. In default option, attributes of all the groups are present. The value provided to attributes in default option are applied to all groups, which are added after providing the value in Default option.

UI Improvement in Correlation ID Window: Few enhancements are implemented in Correlation ID window (Scenario > APM Integration > General Settings). A tooltip of all the labels are provided, which helps a user to understand the feature and input values accordingly.

Status of the File in Version Log for Scenario and Script after Revert: An option ‘Modified Files’ is provided in drop-down of version control window. On selecting this, the user can see which files are in modified and conflicted state.

Conversion of IP Management in Angular 7: For better look and feel, IP management window is now converted to Angular 7.

Test Initialization

Display of Logs when Test is killed: Whenever any error occurs on any stage of either controller or any generator, the test is killed and a pop-up message is displayed “Test is not initialized successfully” and the screen is not directed further to dashboard.

TestSuite

Include Discontinued Metrics: An option to include discontinued metrics is provided in Check Profile rule. The user can now fetch the list of vectors according to the specified time duration rather than from the current partition.

New Rule in Check Profile: A new rule is added in check profile to define the Unexecuted and transaction failure percentage for test status in test report. By using this option, the user can define the rule or percentage for transaction, which is used in check profile through which test status is displayed as ‘Pass’ or ‘Fail’.

Option in Jenkins to Pass the Check Profiles and SLA of Metrics to NetStorm: The user can now upload JSON file in case of NetStorm too. The user can define the rules in form of JSON file and the report are generated according to these rules.

Real Browser User (RBU)

Page Speed Report: A new tool is embedded to get Page Scores and recommendations based on har file input. It provides recommendations in more categories and at much precision level.

JSProfiler

1. Now, on clicking the ‘Enable JS Profiler’ checkbox, a popup message is displayed if the selected browser version is less than Chrome 68 and prompts the user if still wants to use JS profiler with the older version.
2. An option ‘Capture Trace till Network become Idle’ is added within JS Profiler Settings to capture Performance Trace until page load time.

Bandwidth Simulation in Lighthouse: Earlier, the user was not able to simulate bandwidth in lighthouse. The user can now get exact stats from RBU and recommended network bandwidth simulation from lighthouse. This helps the user to simulate lighthouse to the same bandwidth as RBU.

Real Device Testing (RDT)

Display of Debug Trace Log when RDT Test is in Execution: When debug trace is enabled, then instead of dashboard, debug trace is displayed in a new window as a pop-up. However, if browser blocks the pop-up, the user needs to allow / enable that pop-up. In addition, alert is generated as, “Pop-up may be blocked by browser. Please enable pop-up to open Debug Trace Window.”

Implementation of Click and Script type Scripts: Click and Script type script is implemented in RDT (Browser-based as well as NativeApp).

Monitors

‘Active Logged in Users’ Graphs in Cavisson Metrics: Now, the ‘Active Session’ graph is displayed in Cavisson Metrics. This helps a user to correlated active user with other metrics, such as CPU utilization, Memory utilization, and so on.

Alert for Peripheral Device: A new feature is introduced in Windows Device Health Stats monitor. Now, the monitor can hold the vector for configured count, as default is five. The user can configure it by providing /maxVecPersistCount argument in monitor configuration. For example: /maxVecPersistCount:3

Using Service Account (SA) Instead of Kube Token for GKE Monitoring: A user can use Service Account instead of Kube Token to access Kubernetes / API data. Project based SA is provided which is having access to all the clusters inside the Project. The SA is bound with all required roles / permissions. Using that SA, the user can fetch data of all the clusters.

Key Benefits:

1. The user is directly having the token.
2. The user can get a token from the file.
3. The user can generate the token with the Service Account file (JSON file).
4. Supported version (-v) in Monitor UI.

Test Option for ‘Health Check’ Monitor: A user can now test a health check monitor to check if the monitor will work as expected or not (after monitor configuration) by using the ‘Test’ button in ‘Health Check Monitor’ window.

Monitoring Metrics for Spanner DB: Following Spanner monitors have been added in the GCP group of monitors:

1. SpannerMethodStats
2. SpannerNodeStats
3. SpannerSystemStats

% Availability vs Planned Downtime vs Unplanned Downtime in Case of Agentless Monitoring: Earlier, for a server, there were only two states for monitor, such as ‘available’ and ‘unavailable’. Now, all the unavailable servers are further categorized in two states, such as server, which are in ‘maintenance’ and ‘unavailable’.

In the Health Check Monitor UI, an option is provided in Health Check Settings tab for maintenance settings where the user can provide maintenance URL. By default, host and port argument are added in the ‘options’ in health check monitor JSON for maintenance.

Monitor Metrics on Fusion Server: Following stats are supported for Fusion Monitor:

1. FusionClientConnectionStats
2. FusionMemoryStats
3. FusionClientRequestStats
4. FusionBufferPoolStats
5. FusionGCStats
6. FusionThreadStats

SA Token File Path Option: Support for SA token file path option (-A) is provided from monitors UI for Kubernetes monitors.

Key Benefits:

1. The user can have a token.
2. The user can get a token from the file.
3. The user can generate a token from JSON file.

New Message Queue (MQ) Graphs in Cavisson Dashboard: Two new ‘Sum’ type graphs are added in the queue stats of IBM MQ monitor.

1. Total Message Dequeues
2. Total Message Enqueues

Special Character (-) in Tier Name: Support for special character (-) is provided in tier name if using pattern on tier level. A user can now create a tier with ‘-‘ in Server Health Monitor window. For example, Cavisson-QA*.

Additional Graphs in MongoDB Replica Stats: Following metrics are added in MongoDB Replica Stats:

1. MongoDB Replica Insert/Sec
2. MongoDB Replica Queries/Sec
3. MongoDB Replica Updates/Sec
4. MongoDB Replica Deletes/Sec
5. MongoDB Replica Commands/Sec

Monitor for Redis DB Size: To get Redis DB size means currently how much database exists and in that database how much keys are there. A new monitor ‘RedisDatabaseStatsV1’ is added to capture the Redis DB Size.

MSSQL: Server Configuration, Memory Utilization, Connection User per DB Monitor: Four new monitors are implemented in MSSQL to capture the following stats:

1. Server memory utilization [RTG Monitor]
2. MSSQL server configuration setting [Real Time only]
3. Connection established per database based on database name & login name [RTG Monitor].
4. Detailed information about the connection established per database [Data is stored in CSV]

Option to View Alias Queue and Only Non-Zero Enqueue Count Queues: Earlier, while passing JAR path in UI, monitor was not working. To support this, alternate options are also available by providing classpath and JAVA_HOME from UI.

AWS Lambda Application Monitoring: A new monitor (Amazon Cloudwatch) is added for monitoring of a new stack application having Serverless (lambda) environment. The stats are as follows:

• ACEC2Stats
• ACLambdaStats

Amazon CloudWatch monitors Amazon Web Services (AWS) resources and the applications run on AWS in real time. CloudWatch used to collect and track metrics, which are variables that can measure for resources and applications.

Database Monitor to Read MongoDB at a Specified Period: A generic NoSQL monitor is provided read MongoDB at a specified period and trigger the alert when the value changes.

Android Device Monitor: Android device monitors are added to capture the following stats:

• Android Battery Stats
• Android Memory Stats
• Android CPU Stats

NiFi Metrics for NetDiagnostics: Following stats are provided to capture the NiFi Metrics for NetDiagnostics:

• Mbean NiFi System Stats
• Mbean NiFi Counters Stats
• Mbean NiFi Processor Stats

Monitoring of ‘Data Power Extensions’: Following monitors are added:

• IBM Data Power File
• IBM Data Power System
• IBM Data Power Network

New API for NginxPlus: Support for below statstype of nginxPlus monitors through generic JSON monitor is provided:

1. cache
2. serverzone
3. upstream

Kafka Lag Capturing to Support New OCF Design: Kafka is a distributed, partitioned, replicated log service. It provides the functionality of a messaging system, but with a unique design. It was created to provide a unified platform for handling all the real-time data feeds.

Fetching SecA Metrics from OpenTSDB: A user can now fetch SecA metrics from OpenTSDB. OpenTSDB is a time series database. A time series is a series of numeric data points of some particular metric over time. Each time series consists of a metric plus one or more tags associated with this metric.

Integration Point Stats Ex Monitor: Integration endpoint URL is passed as an option in monitor (to avoid dependency of .txt file, as environment is dynamic). This monitor takes all the inputs from file as well as through JSON UI.

LPS Health Metrics: LPS health metrics are implemented with the following details:

• Number of owner thread
• Number of worker threads
• Data Throughput received
• CMON connection failures
• NS Connection close
• Number of accesslog monitors
• Number of log monitors
• Number of getlogfile monitors

LPS Related Logs in Individual TestRun Partition-Wise: LPS related logs are now present in individual Test-Run partition wise. Now, the Test-Run is found in the following directory:
TR > partition id > nd > logs > lps_trace_logs

Dataflow Metrics in ND: For Dataflow monitor, below metrics are supported:

• Billable Shuffle Data Processed
• Total Memory Usage Time
• Total PD Usage Time
• Total Shuffle Data Processed
• Total Streaming Data processed

Monitor Logs per TestRun Number: With this enhancement, agent creates logs per Testrun. In addition, logs are enabled only if debugLevel setting is provided in monitor configuration (mprof/json).

SAP Support: Following new monitors are provided in support of this:

1. HANA Users
2. HANA Networks
3. Hana Schema Memory
4. Hana Memory Allocation
5. Hana Component Memory
6. Hana Resident Memory
7. Hana Peak Memory
8. Hana Save Points
9. Hana Backup

Dashboard

Graphs

Group ID and Graph ID Using REST API Service: Group ID and Graph ID are always numeric. Graphs are belong to a specific group. The user must know the group name to obtain Group ID and Graph ID. A graph ID is the exact name of a graph, which is already mapped in generic REST service.
To obtain Group ID and Graph ID, the user needs to make an ND REST call. For example:
http://10.10.50.17/DashboardServer/web/dev/getGroupIdGraphIdFromGroupNameAndGraphName?testRun=11170&groupName=SysStatsLinuxExt&graphName=CPU%20Utilisation
The output of above REST call is 10108,18 where Group ID is 10108 and Graph ID is 18 (these are separated by a comma in the output).

Sample URL covering Group ID and Graph ID
http://10.10.50.17/DashboardServer/web/dev/checkGraphDatav3?startTime=04/25/2018%2020:00:00&endTime=04/25/2018%2021:00:00&groupId=10108&graphId=18&vectorName=WebTier*&mode=2&isPattern=true&derFormula=AVG&isAggr=true&token=H4IlsSDuZJdc1bBnAaGVvq5zpMm0lLm0O1NKUS3

Selected (by default) ‘Show Discontinued Metrics’ Check box: The default status of ‘Show Discontinued Metrics’ check box is enabled/selected in Excel report. This enables a user to get the data of discontinued metrics too (by default) while generating an Excel report.

Disabled Graph Sample Filter Option: When a user selects graph type other than ‘Normal’ graph type, the ‘Graph Sample Filter’ option is disabled.

Graph Sample Filter Configuration: A user can now edit filter configuration of a graph sample by using the ‘Edit’ option in the ‘Action’ column. In addition, a confirmation message is displayed while deleting any configuration.

Capability Tooltip in Multi-DC: Now, the list of capabilities is displayed in Multi-DC environment in the tooltip of the logged in user button.

Derived Graph Chart Type Conversion: A user can now convert a derived graph widget into a ‘Data’ type widget and can change panel caption from ‘Edit’ option in ‘Widget Settings’ window.

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

Template to Provide Graph Data: A user can now generate sample-wise stats report.

Scaling Threshold Value: With this new feature, the user can select the scaling threshold value in terms of 2X, 5X, and so on when scaling is enabled in Web Dashboard. It helps the user to calculate the Scale Factor based on the scaling threshold value.

‘Success’ and ‘Fail’ Columns in Transaction Details: Whenever a 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.

Alerts

Instance Name in ‘Service Now’ Alert: The instance name is added in node field of SNMP trap. User can now get instance name for alert generated for graphs with ‘Data Not Available’ status.

Option to Select Prediction Alert in Alert Policy: An option ‘Applicable Only for Predictive Alert’ in Alert Policy window is provided. On enabling this option, the policy works for only prediction alert.

Source Appliance IP in SNMP Trap Field: Now in SNMPTrap, IDCName field holds the following:

1. IDCName_SourceIP (Appliance IP) if IDCName already configured.
2. Source_IP if IDCName is not configured.

Addition of ‘Alert ID’ Field in ‘Alert History’ Table: A new field ‘Alert ID’ is added in the ‘Alert History’ table as the first field. The user can apply filters on this field too likewise other fields in the table. By default, this column is not visible.

Active Alert Values: Earlier, only the alert value that contains the value responsible to generate the alert is displayed. Now, the baseline value / previous window value and load metric value (if present) is also displayed.

Charts in Alert Mail: Now, the support has been added for showing charts for the metrics on which alert has been generated, as well as user can also see the metrics, which are matching the same pattern as the alert metric, to find out some clue about the root cause. A user can now provide a maximum of 150 charts in alert email and graph duration can be added up to 1440 minutes. If user tries to provide inputs beyond the specified limits, an alert message is displayed on saving and do not allow to save the values.

Advanced Email Setting of Alert Policy: When a user applies pattern matching, the Alert Mail, which is generated contains the following information:

• Pattern Matching Threshold
• Catalogue Used
• Maximum number of Graphs

Indices Column in Alert History: On clicking, the value of Indices in the Indices column is displayed in a pop-up with ‘Alert Value’ column.

Alert Mail: Display of ‘Baseline Value’ Column and ‘Severity’ Column based on Certain Conditions: In tier-wise alert rule, for relational operators, such as >=, <=, >, <, = or != then ‘Baseline Value’ column is not displayed in Alert Mail and ‘Severity’ column is not displayed for Tier Wise Alert.

Alert based on the Deviation for Baseline: This is the subset of chart configuration that is displayed in advance section of alert mail. A user can specify a catalogue, which contains the graphs information to apply pattern match. The user needs one baseline to compare all the graphs available in catalogue. To get the baseline graph (this is the graphs for which alert is generated), the user needs some criteria, which should have the minimum or maximum value across all the indices of one condition for which alert is generated. Once the baseline is selected, the user can compare every samples of both the graphs (baseline as well as the catalogue graphs) and can filter all the graphs, which satisfies the threshold value provided in the action.  After that, all the resultant graphs are sent in the email body along with all the alert information.

Alert Action History Section to Show Details of Alert Action: An ‘Alert Action History’ tab is provided that contains details of action taken by alerts, such as SNMP Trap Sent / Email Sent / Cisco Spark Chat sent and so on.

Display of Dashboard Corresponding to Generated Alert: Now, the Product Dashboard URL is sent with preselected time frame in alert message. Therefore, when a user hits a URL that is sent via alert email, SNMP trap, and alert extension, only those graphs are displayed for which the alert is generated. Earlier, this used to open the default favorite and the user was required to plot the graphs (where the alert is generated) manually. This feature saves the user’s time and enables to view the relevant graphs automatically.

Multi DC: Display of Alerts for Data Centers with Different Test Runs: Alert feature is now implemented for different test runs for Multi DC. The user can now view active alert bell counter and the corresponding records in Active alerts.

Multi DC: Alert Settings Window: This enhancement is implemented to save same configurations across all the DCs in case a user tries to save Alert Settings for ‘All’ or individual DC. If any individual DC is selected, saving the Alert Settings impact only on the selected DC and also get the configuration from the selected DC that is reflected in UI. If DC is selected as All, all the changes done by user is saved on all the configured DCs. However, the configuration that is being displayed in the UI is of Master DC.

Slack integration with ND-Alerts: A new option for Slack is available in Alert Extensions under Alert Action. By using that, the user can send Alert Incident in Slack Application.

Reports

Common Query Manager: UI Filter in Transaction Summary Report: 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.

Display of ‘Data’ Value and ‘Percentage’ Value: Now, data value and percentage value is displayed with legend in case of ‘Pie’ and ‘Donut’ chart.

Excel Report Generation with ‘Last’ Value: The excel report can now be generated with Last value of the graph. The user can generate this by selecting ‘LastValue’ in ‘Type’ column of excel template.

Report Access Permission: If a user is assigned with ‘No Permission’ in capabilities section to access ‘Report’ feature, then on accessing the Reports feature from TestRun / Session UI / Dashboard, the session logs out with a message “You are accessing unauthenticated links hence closing this session”. In addition, the user cannot access the Reports menu in Widgets settings. On having Read-only permissions for Reports, the user can only view the generated reports or template, but cannot create a new one from Report Management UI.

‘Last’ Option in Report Management Window: Now ‘Last’ option is displayed in the drop down list of Formula Type for Pie and Donut chart type while creating Template from Template UI and from Report Management UI using Select Metrics.

More Filters in Reports: Few more presets, such as ‘Hours Back’, ‘Days Back’, ‘Weeks Back’, ‘Months Back’, ‘Last Week Same Day’ and ‘Last Month Same Date’ are provided in Reports. The above said presets are displayed when a user use ‘Compare’ feature.

Trend Report for Data of 95th Percentile: After implementation of this enhancement, now the trend compare report is generated with 95^th Percentile value in case of Avg, Min, and Max data values. Table in the generated report displays all the selected percentile values but chart is formed based on 95^th value. Earlier, chart of only normal graphs was coming, and now in case of percentile graphs, data values that displays in graph is of 95^th percentile.

Performance Dashboard

Inventory Configuration: A user can now add, remove, and update the inventory details.

MSSQL

Slow Queries Based on CPU and IO Feature: The user can now see slow queries based on CPU and I/O in DB Query Stats window by default. To see all results without any basis like previously, the user can select ‘ALL’ from the query basis dropdown. When CPU is selected as the basis, the data is sorted based on the “Worker Time” field. When I/O is selected, then data is sorted based on sum of Logical Reads and Logical Writes.

DrillDown to Session from Wait Stats Window: A user can now drill-down from Waitstats window to Session window. If the user clicks on any category, which are listed in Graph Panel of Wait Stats, it redirects to Wait Stats table in which only selected category and corresponding waittype are displayed in Wait Statics table panel. By clicking the waittype (present in wait stats table), the user can navigate to Session window and see SessionId for corresponding waittype.

Threshold Value for Different Indexes in the Action FlowMap in the Report Stats Monitor: A user can now set a threshold value for different indexes shown in the ‘Execution Plan’ in the Report Stats monitor. The user needs to open the ‘Configurations & Logs’ window and click the ‘Settings’ button on top-right corner. Then, in the window that opens up, the user can set the values.

NetCloud

Applying RTC on removing more than Existing Users

1. While trying to remove more virtual users than existing, the user can remove available users from that group only. For example: If there is a scenario with three groups – G1, G2, and G3 having 10, 100, and 500 users, on removing  50 virtual users 50 from G1, the user is allowed to remove only 10 virtual users from G1.
2. On adding 50 virtual users after applying RTC in G1 and trying to remove 100 virtual users from that group, the user can remove only 60 virtual users from G1.

Tool-Tip for Generator Name in Transaction Details: A user can now view the full name of the generator by hovering on the generator tab name in transaction details window.

Support for TCP Dump Feature: Support for TCP dump feature is provided in UI.

NetOcean

Display of Mode (Normal / RTC) in Header Label: Earlier, in both modes (Normal & RTC), same header label was displayed. Due to which, it was difficult to differentiate which one is for normal mode and which one is for RTC mode. Now, the corresponding mode is displayed in the header label, which helps a user to identify which header belongs to which mode.

Configuration Deletion Confirmation in JMS Window: A confirmation popup message is displayed while deleting any configuration of JMS. For example, “TIBCO configuration row(s) deleted successfully”.

Restriction to Save a WSDL Service with Same Name: A user cannot save a WSDL service with the same name, which already exists. While doing so, an error message is displayed.

Restriction to Save a Blank file in Dataset Parameter: A user cannot save a blank file in data-set parameter and indexed data-set parameter. While doing so, an error message is displayed.

Configuration Deletion from File while Deleting from UI: When a user deletes all the configuration settings from UI (for IBM MQ and TIBCO), the same gets deleted from the configuration file.

Scroll bar to See Whole Condition without Opening the Template: The user can now adjust width of table columns. If the table width is exceeded with the screen width, a horizontal scroll bar is displayed at the bottom. In addition, a master check box has been added according to the previous design.

Disabled Access Log (by Default) in New Machines: The Access Log settings for new machines is disabled by default. To capture access log, the user needs to enable it manually.

Adding IBM MQ and TIBCO Simultaneously: A user can now add IBM MQ and TIBCO configurations simultaneously, which earlier was limited to add configuration for either TIBCO or IBM MQ at a time.

Host Name and IP both in Source and Destination Server of JMS Configuration: Support for Host Name has been added in source and destination server of JMS configuration. Now, the user can enter server IP or server host name in “Server” field. In addition, placeholders have been added to changed fields to let the user know about the two possible values (IP/host name) which can be used.

HTTP2 Configuration: A user can now configure the following HTTP2 settings from UI:

• Server Push
• Max Concurrent Streams
• Initial Window Size
• Max Frame Size
• Header Table Size

File Extension .crt in ‘Browse’ Option: While browsing for a file, the user can now select a file with .crt extension.

Using Unused Ports: Earlier, if a connection time-out job is scheduled for the second time, an alert message is displayed stating not to use the port, which has already used. With this enhancement, that ‘used’ port is removed instead of displaying an alert message and only unused ports are displayed in the ports list.

Compression Type Setting of Service Level at Template Level: Service-level Compression type (selected) is now supported at Template-level. One more option ‘Select Type’ is added in the list of ‘Content-Encoding’ Compression-Type options at both service-level and template level. In addition, one more option on template-level is provided in case if user has already saved Compression-Type (ex: gzip) at service-level.

Support for AJB: Support for AJB calls is provided same as PinPad settings. The user can filter AJB services from service type drop down list. The user can create AJB request response pair and parameterize AJB response.

Configuration UI for Correlation Directory Settings: Configuration UI is provided in Global Settings, which displays the list of directories in correlation directory. In addition, the currently active correlation directory is displayed in “Manage Services” window.

File Extension Restriction in ‘Browse’ Option: A user can upload only those files whose extension has been configured in the property file of NetOcean configuration.

Addition of ‘Stopped’ Status in Connection Timeout Settings: Earlier in Connection Timeout Settings, if a user tried to stop any job, the status of that job used to get displayed as ‘Completed’. Now, if the user stops any job which is at ‘Scheduled’ or ‘Running’ status, the status of that job is displayed as ‘Stopped’.

Support for TLS1.3 Version: Support for TLS1.3 Version is provided, which earlier was limited to TLS1.2.

RTC Mode in Header Label in All Windows: Earlier, in both the modes (Normal & RTC), same header label is displayed, due to which it was tough to identify whether the header is for normal or RTC mode. Now, the corresponding mode (Normal or RTC) is displayed along with the header in all the windows.

NetDiagnostics

DDR

Pagination in Thread StackTrace in Hotspots Report: In Hotspots report, pagination is now supported in Thread StackTrace where a user can also select the number of records that can be viewed at once.

Flowpath Data from ND to NV: While opening flowpath report from NV, the user now gets flowpath data as per changing in rest call parameter, start time, and end time for ndsession Id.

Getting ‘Overall’ under Tier while Traversing through Flowpath Stats: Now, ‘Overall’ is coming under all Tiers in flowpath stats and Overall > Overall > Overall is removed from flowpath stats.

Drill-Down through Integration Point in Multi DC: This is a Multi-DC enhancement, which is handled in all the cases where Drill-Down through integration point is supported, such as Executive Dashboard, Web Dashboard. It is also handled while traversing from IP-Health Report.

Query Timeout for DDR Queries with JDBC: A user can set the query timeout (in seconds) from Dashboard via Configuration > Configuration Settings > Dashboard Settings > DB Settings.

Multiple Async DB Callout in Transaction FlowMap: ultiple DB Callouts are supported from Flowpath with the following cases:

1. Single Flowpath
2. Merged Flowpaths

Config UI

Entry Point for Advance Custom Profile: A new entry point ‘advancecustom’ is added for Advance custom profile from UI.

‘Help’ Icon in NDE Cluster Configuration Window: A ‘Help’ icon is provided in NDE Cluster Configuration window that displays the description of the labels used in the window.

Backend Naming Rules for Spanner DB from UI: A user can now configure Backend Naming Rules from Config UI for Spanner DB by selecting appropriate Integration Point Naming Rule(s) such as ProjectId, InstanceId, and DatabaseId.

Entry Points for Spanner DB from UI: New entry points are added for Spanner DB from UI. Below are some examples:

• google.cloud.spanner.SessionPool$AutoClosingReadContext.readRow(Ljava/lang/String;Lcom/google/cloud/spanner/Key;Ljava/lang/Iterable;)Lcom/google/cloud/spanner/Struct;
• google.cloud.spanner.SessionPool$AutoClosingReadContext.readRowUsingIndex(Ljava/lang/String;Ljava/lang/String;Lcom/google/cloud/spanner/Key;Ljava/lang/Iterable;)Lcom/google/cloud/spanner/Struct;
• google.cloud.spanner.SessionPool$AutoClosingReadContext.readUsingIndex(Ljava/lang/String;Ljava/lang/String;Lcom/google/cloud/spanner/KeySet;Ljava/lang/Iterable;[Lcom/google/cloud/spanner/Options$ReadOption;)Lcom/google/cloud/spanner/ResultSet;
• google.cloud.spanner.SessionPool$AutoClosingReadContext.executeQuery(Lcom/google/cloud/spanner/Statement;[Lcom/google/cloud/spanner/Options$QueryOption;)Lcom/google/cloud/spanner/ResultSet;
• google.cloud.spanner.SessionPool$AutoClosingReadContext.read(Ljava/lang/String;Lcom/google/cloud/spanner/KeySet;Ljava/lang/Iterable;[Lcom/google/cloud/spanner/Options$ReadOption;)Lcom/google/cloud/spanner/ResultSet;
• google.cloud.spanner.SpannerImpl$TransactionContextImpl.executeUpdate(Lcom/google/cloud/spanner/Statement;)J
• google.cloud.spanner.DatabaseClientImpl.writeAtLeastOnce(Ljava/lang/Iterable;)Lcom/google/cloud/Timestamp;
• google.cloud.spanner.DatabaseClientImpl.write(Ljava/lang/Iterable;)Lcom/google/cloud/Timestamp;
• google.cloud.spanner.SpannerImpl$SessionImpl.write(Ljava/lang/Iterable;)Lcom/google/cloud/Timestamp;
• google.cloud.spanner.SpannerImpl$SessionImpl.writeAtLeastOnce(Ljava/lang/Iterable;)Lcom/google/cloud/Timestamp;
• google.cloud.spanner.SessionPool$PooledSession.write(Ljava/lang/Iterable;)Lcom/google/cloud/Timestamp;
• google.cloud.spanner.SessionPool$PooledSession.writeAtLeastOnce(Ljava/lang/Iterable;)Lcom/google/cloud/Timestamp;

Change in Duration of Inactivity for an Instance: In ND Collector Settings, the duration of inactivity after which an instance is marked inactive is changed to 10 minutes.

Custom Configuration Name in DotNet Profile: In DotNet Profile, a new custom configuration name ‘enableProcessNotificationPhase’ is added.

Custom Configuration Name in ND Collector Settings: In ND Collector Settings, a new custom configuration name ‘NDC_T_DIGEST_DEBUG_INFO_DUMP’ is added.

New Columns in Download Agent Logs Window: In the ‘Download Agent Logs’ window, a user can view the file size and its modification time.

Saving Changes when Instances are Down (TierGroup Feature): By using the TierGroup feature, the user can add regex pattern, which enables those upcoming Tiers that comes under it and satisfies the regex pattern. In addition, the profile applied at TierGroup level automatically attached with upcoming tiers. A profile can also be attached with Tiers, which do not have any servers/instances under it. Moreover, whenever any server/instance comes up then, the profile attached at tier level is attached with them.

Capturing Weblogic Saaj Soap Service Callout: Support of following entry point is provided: weblogic.wsee.saaj.SOAPConnectionImpl.call(Ljavax/xml/soap/SOAPMessage;Ljava/lang/Object;)Ljavax/xml/soap/SOAPMessage;|HttpCallout|0

Custom Configuration Name in Java Profile: In Java Profile, a new custom configuration name ‘enableOptimizedInstrumentation’ is added.

Entry Points for HTTP: New entry points are added for HTTP from UI, which are as follows:

• connect(SocketAddress;)V
• connect(SocketAddress;I)V

Entry Point for Thread: The following entry point is added for Thread:
java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(Ljava/util/concurrent/RunnableScheduledFuture;)V

Entry Point for AsyncHttpService: The following entry points are added for AsyncHttpService:reactor.ipc.netty.http.server.HttpServerOperations.onHandlerStart()V|AsyncHttpService|0
reactor.netty.http.server.HttpServerOperations.onInboundNext(Lio/netty/channel/ChannelHandlerContext;Ljava/lang/Object;)V|AsyncHttpService|0

ND-NF Log Transfer: ND-NF Integration is enhanced by adding Topology and Flowpath information in access and application logs. Previously, only TOPO and FP are added at the end of the message. Now, in addition to that, the logs are getting cached and bulk log information is sent after each interval (configurable).

Apply Method based BT Rule based on URL: Business Transaction window has been re-designed and all the tabs for ‘Split by Method Execution’, ‘Split by Request Headers’, ‘Split by Response Headers’, and ‘Split By HTTP Body’ are moved inside Pattern Configuration. Two new fields – Rule ID and Parent Rule ID are also added in each type of BT.

ND Agent

Integration Points with Message Type: A new callout type (advCustomCallout) is introduced to handle configuration of advance custom callout.

Below are some examples of message types:

• TokenRequestMessage
• EligibilityRequestMessage (For Health Check)
• GetAuthPathRequestMessage
• GetAuthUrlRequestMessage
• SendSmsRequestMessage
• VerifyRequestMessage

This setting contains the following parameters:

• Fully Qualified Method Name (FQM)
• Type of the callout, (for example, advCustomCallout)
• User defined default backend name, for the callout
• Operation
  • RT: Return based advance callout
  • ARG: Argument based advance callout
  • ALL: Both Return and Argument type
  • DEFAULT: Same as customcallout

Addition of MongoDB IP in few Integration Point Stats: The user can now capture Mongo DB calls with higher version of Mongo i.e. MongoDB shell version v4.0.1.

Maximum Limit to set for Response Time: The maximum limit for response time is set to 86400000ms (1 day) for ‘Response Time’ search box in Search By Response Time window navigated through Integration Point > DDR > Flowpath By IP Response Time.

Automatic Detection of Callout using Socket API: This feature is helpful for detecting integration point callouts automatically, when environment is new. A client program creates a socket on its end of the communication and attempts to connect that socket to a server. When the connection is made, the server creates a socket object on its end of the communication. The client and the server can now communicate by writing to and reading from the socket.
java.net.Socket are using as client Socket.
Now, the Agent will have two new entry points (by default these will be disabled), for which backend name will be based on Host and Port only.
java.net.Socket.connect(Ljava/net/SocketAddress;)V|HttpCallout|0
java.net.Socket.connect(Ljava/net/SocketAddress;I)V|HttpCallout|0

ScheduledThreadPoolExecutor Thread Callout Detection: This feature is useful for detecting ThreadCallouts generated by ScheduledThreadpoolExecutor API in an environment. The agent will have one entry point (by default it is enabled).

java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(Ljava/util/concurrent/RunnableScheduledFuture;)V|Thread|1

New Integration Exit Point (SoapConnectionImpl.Call): Supported Exit point:
weblogic.wsee.saaj.SOAPConnectionImpl.call(Ljavax/xml/soap/SOAPMessage;Ljava/lang/Object;)Ljavax/xml/soap/SOAPMessage;|HttpCallout|1

React Netty 0.7 and 0.8 Applications: Support has been provided for React Netty 0.7 and 0.8 Applications. New entry point supported are:

For Reactor Netty (0.7 Series)
#reactor.ipc.netty.http.server.HttpServerOperations.onHandlerStart()V|AsyncHttpService|1
For Reactor Netty (0.8 Series)
#reactor.netty.http.server.HttpServerOperations.onInboundNext(Lio/netty/channel/ChannelHandlerContext;Ljava/lang/Object;)V|AsyncHttpService|

New End Point for DB2: DB2 support is provided in Java agent by new feature of capturing DB calls using JDBC interface API.

Executive Dashboard (ED)

Call Details of Any Third Party Integration Call: A user can download, sort, and filter the Calls Details by right clicking on Integration point  > DDR > Call Details.

Sequence Diagram Filter Criteria: After applying any filter option in Sequence Diagram filter settings window, the configured filter criteria is displayed in sequence diagram filter criteria, which earlier was displayed as default.

Display of Non-ND Tiers: Now, non-ND tiers, such as ‘Ingress’ and ‘Egproxy’ of Mobile Environment are displayed in ED.

End to End Monitoring: Currently in ED, ND tiers and only Access Log based Non ND tiers are displayed. In addition, the integration points of only ND tiers are displayed. There was no provision to display non Access Log based Non ND tiers and their integration points. However, with this new enhancement, multiple new Non ND tiers (non access log based) can also be displayed. All the Non ND nodes (new as well as existing) are displayed via JSON configuration. In current JSON, NON ND nodes of following groups are supported:

• HTTP Test Traffic Stats
• Akamai Connection Provider Stats
• NGINX Resource Stats V2
• Apigee Service Stats By API
• Access Log Stats Extended V6
• Access Log Stats Extended V5
• Access Log Stats Extended

NetVision

Display of Data in New Tab: Whenever a user clicks ‘Count’ link in ‘Event Aggregate Report’, the data is displayed in a new tab rather than in the existing one.

NVSPA: Filter out HTTP Data Based on Page Name: In smart search of HTTP filter, an option to filter the records based on page name is available to filter out HTTP requests for any page.

Event Configuration: A new event is configured for the error message ‘Request header field too large’ in ‘Reset Your Password’ section on ‘Login’ page.

Integration of Test Data Mapping Profile for NetTest: Profiles are created that contain selector mapping (mapping of new selector with old selector), data mapping (data associated with a session like store name, number of items in cart), form Mapping (mapping of form data). This profile data must be parsed and mapped to selector and form fields at runtime (when script is executing). So that script failure rate can be minimized.

Extension of Chrome Local Storage Limit: Chrome local storage limit is exceeded when running test case with profile. Test Data mapping Profile content length should be less than 5242880 bytes.

NVSPA: Filters: In NVSPA UI, once a user clears all the filters and does not apply any new filter for some time, then the complete data is fetched automatically and displayed on the UI.

Connection Type Filter Column in Session Table: A new column ‘Connection Type’ is provided in ‘Session’ window. The details of connection type is displayed in ‘Session Details’ window.

Angular 7 Migration: From this release, NVSPA is displayed in the ProductUI tab itself, instead of displaying in a new tab.

NVApp Compare Trend: NVAPP Compare trend provides an interface to compare page performance data, revenue, and traffic of two different time durations in NV UI.

Multi Level Aggregation: Through multi-level aggregation, same raw data is aggregated on multiple levels of aggregation for optimizing the queries to fetch data in less time.

Replaying User’s Action Performed on Multi Tab: In case, a user is visiting a website in multiple tabs (may be for comparing two products, or keeping a product in one bag and availing offer in other bag), all the actions performed by the user are useful to track the user behavior. NetVision can now exactly capture and replicate the behavior of the user and display all the user’s actions performed on multiple tabs.

Synthetic Monitoring (SM)

Capturing Performance Trace: Support to capture ‘Performance Trace’ is provided on UI within Global Configuration > Miscellaneous tab.

Tooltip for User Inputs: A tooltip is provided within Global Configuration > Miscellaneous > JS Processing Time and Data URI that helps a user to know about the corresponding inputs for disabling JS Processing Time and Data URI, capturing JS Processing time, capturing Data URI in block waterfall, and capturing both, which are 0, 1, 2, and 3 respectively.

URL Based Script: In NVSM UI and Scenario UI, while adding or editing a group, the URL type script will have ‘Script Name’ field also, where the user can provide script name along with page name and URL.

Lighthouse Report: Lighthouse Reports in SM are now created using Logging-reader and writer. So, dynamic data is updated.

NetForest

Grouping in Pie Chart:A user can now split Pie chart using a query. Earlier, the user can only split slices in Pie chart. The split chart query should be written before all buckets query:

Syntax: *|VIS count() by splitchart(<fieldname>[parameters like: size,orderby etc]),<fieldname>[parameters like: size,orderby etc]

Example: *|VIS count() by splitchart(log_message.reqLen[size=7]),log_message.reqPath[size=5]

Custom Label via VIS Query

It is used to provide custom label in VIS query. Therefore, that user can change/modify the label of columns and rows as per requirement. It is applicable for charts.

For count/countrate: *|VIS count(customLabel=query_count) by server[size=5 order=Descending orderBy=1 customLabel=server]

For others: *|VIS Average(resp_time customLabel=query_count) by server[size=5 order=Descending orderBy=1 customLabel=server]

NOTE: ‘customLabel’ does not support space in label name.

NF-ND Single Sign On (SSO)

Any user can access a product UI (NF/NV/ND) from other product UI once login into a product UI.

Example: If a user is logged-in to NetDiagnostics with some credentials and wants to go to NetVision or NetForest, user can directly move to that product without login to that product.

Individual Request for Each Panel of Dashboard

A user can now configure how many request(s) to send to capture data on dashboard panels via ‘Advance Settings’ section. The request could be either ‘single’ or ‘multiple’.

Single: To send one request for whole dashboard

Multiple: To send individual request for each panel of dashboard

Loading/Display of Charts

Now, only those charts are loaded, which are visible in Dashboard for the first time without scrolling down.

Example:

If any dashboard contains 20 charts and for the first time, when a user loads that dashboard, only four charts are visible without scrolling down. Then, request for only those four charts are sent to NFDB. Rest of the charts get loaded after those four charts are loaded successfully.

Importing Visualizations / Dashboard / Searches with Same Name

When a user imports more than one visualizations / dashboards / searches with the same name that already exists, it prompts to overwrite the data. It contains various options, such as ‘Overwrite all’ / ‘Overwrite selected’ / ‘Skip’.

‘By’ Clause with ‘Earliest’ and ‘Latest’ Functions: This provides the result with the ‘latest’ and ‘first’ occurrence of the field specified in ‘BY’ clause.

Example:
Earliest: *|stats earliest(@timestamp) BY server, type
Latest: *|stats latest(@timestamp) BY server, type

Filter Indices: On opening indices, all available indices are displayed on the page and the user can select indices for close / open operations. The user can filter out indices based on environment, tier, and date. In addition, the user can filter all the closed and open indices and can change indices’ status one by one.

Merge Rows based on Single Value for Creating Charts: This feature merges other fields based on one or more field name.

Syntax

*|merge <[VALUE|value]=[String|number]> <fieldNames>
<fieldNames>: multiple field name will be separated by comma(,)

Examples
*|merge value=”NA” field_name
*|merge  value=0 field_name
This construct should be use when there is high level of redundancy in data. That is, when majority fields’ values are something like “NA” or null.

‘int’ Datatype in Query for Eval Construct: ‘int’ datatype is now supported in query for ‘Eval’ and ‘Rex’ constructs.

Display of Build Version: A user can now view the Build version of NFUI along with the build version of NFDB and NFAlert.

‘Help’ Option to Show Sample Queries and Product Help: A ‘Help’ option is provided at the top-right corner of the window where the user can view product help and some sample queries with examples for better understanding.

Creation of New Fields:The newly created fields (by rex/eval) are displayed on top in document, initially it was displaying at last line or middle of document. Therefore, it was difficult for the user to find it.

Working of Now() Function Individually Without any Other Function: This function takes no arguments and returns the time that the search was started. The now() function is often used with other data and time functions. The time returned by the now() function is represented in UNIX time, or in seconds since Epoch time. When used in a search, this function returns the UNIX time when the search is run. If the user wants to return the UNIX time when each result is returned, use the time() function instead. The user can use this function with the eval, fieldformat, and where commands, and as part of eval expressions.

Min/Max in Stats/Docstats Queries

• Stats():Calculates aggregate statistics, such as average, count, and sum, over the results set. The user can use statistical and charting functions with the stats command
• Docstats(): Generates summary statistics of all existing fields in the search results and saves those statistics in to new fields. The user can use statistical and charting functions with the docstats command. Each time, on invoking the docstats command, the user can use one or more functions

Min/Max

The min/max in stats/docstats returns the minimum and maximum value of the field X respectively. If the values of X are non-numeric (such as Version, String), the maximum value is found using lexicographical ordering.

NOTE: Currently, the min/max aggregation is only supported for numeric field.

Bug Fixes

The following issues are fixed in 4.1.15.