Metrics Statistics

In Web Dashboard, user can view various statistics on the metrics, which are as follows:

  • Thread Hotspot Stats
  • Flowpath Stats
  • DB Queries Stats
  • Method Stats
  • Exception Stats
  • HTTP Headers Condition Stats
  • Integration Point Stats
  • Business Transactions

Thread Hotspots Stats

Thread Hotspots:

  • Threads which are stuck in one method for a time more than the threshold value are called as Hot Spot threads.

48

Understanding Metrics:

  • Number of Threads: Total number of threads in JVM.
  • Number of all Hot Spot Threads: It shows total count for all the hot spot thread detected.
  • All Hot Spot Thread Duration: Duration for all hot spot threads in seconds.
  • Number of all New hotspot threads: This is the count for new hot spot detected.
  • New Hotspot Thread Duration: Duration for new hot spot threads in second.
  • Number of Blocked Threads: It shows count for blocked threads which are waiting for a resource held by another thread.
  • Number of runnable Threads: Threads in these states are considered to be in executing tasks.
  • Number of Time Waiting Threads: It shows count of ‘time waiting threads’ which enters time waiting state for a specific interval of time.
  • Number of Waiting Threads: It shows count for waiting threads which are waiting for another thread to complete its task.
  • Number of Terminated Threads: It shows counts for terminated threads.

All Graphs regarding threads

Hotspot Threads Details:

  1. Go to Panel settings and click the Thread HotSpots option.

  1. The Thread HotSpot Details window is displayed.

There are following Thread Hotspot details in this window:

  • Thread ID: Unique Id of the thread
  • Hotspot Entry Time (Absolute): Start time of the hotspot
  • Hotspot Entry Time (Elapsed): Start time of the hotspot related to test run start time
  • Hotspot Duration: Duration of the hotspot in seconds
  • Thread State: Current state of thread, such as runnable, timed_waiting, blocked, running etc.
  • Thread Priority: It is the priority of thread, such as 1, 2, 3 and so on. Threads with priority 1 are executed first and so on by JVM.
  • Stack Depth: Number of methods within the stack defined the depth of the stack trace captured for hotspot.
  1. User can apply filters on the thread details window to find out details on specific threads. There are following filter options:

  • Showing hotspots: Specify the duration when hotspots occurred, such as last 10 minutes, last 20 minutes, and so on.
  • Stacktrace contains: Specify the thread name. The stacktrace with the specified method is displayed.
  • Min depth: Specify the minimum stack depth. The result is displayed based on the value selected.
  • Min duration: Specify the minimum duration of the hotspot (in seconds). The hotspots whose minimum duration is the one that is specified are displayed in the result.
  1. Once the filters are applied, click the Apply button . To reset the filters, click the Reset button .
  1. At the top pane, there are following tabs – No Grouping, All Frames, and Custom Depth. No Grouping tab displays the thread details without grouping. In All Frames tab, user can specify group by the thread Hotspots based on all frames. In custom depth, user needs to specify the number of top frames for grouping. Here, we are displaying the window that is displayed on the selection of – No Grouping, All Frames, and Custom depth. 

No Grouping

 

All Frames

This window displays stack trace signature details, such as total unique signatures, start time, end time, tier, server and instance.

There are following other details displayed in this window:

  • Stack Trace Signature: A signature to identify common stack traces in hotspot
  • Stack Frame: The containers of stack depth are stack frames
  • Stack Trace (Top Methods): Top methods for all threads matching group by signature
  • Min Depth: Minimum hotspot thread stack depth
  • Max Depth: Maximum hotspot thread stack depth
  • Thread Count: Number of hotspot threads grouped by specified signature
  • Min Duration: Minimum duration of current group of matched hotspots
  • Max Duration: Maximum duration of current group of matched hotspots
  • Avg Duration: Average duration of current group of matched hotspots
  • VMR: It stands for Variance to Mean Ratio. It is the standard deviation of duration

Custom Depth

On selecting this option, user needs to specify the number of top frames for grouping.

Enter the number of top frames for grouping and click OK. The resultant window is displayed with grouping by the specified custom depth.

There are following other details displayed in this window:

  • Stack Trace Signature: A signature to identify common stack traces in hotspot
  • Stack Frame: The containers of stack depth are stack frames
  • Stack Trace (Top Methods): Top methods for all threads matching group by signature
  • Compare Depth: Number of frames targeted for comparing stack for each thread
  • Min Depth: Minimum hotspot thread stack depth
  • Max Depth: Maximum hotspot thread stack depth
  • Thread Count: Number of hotspot threads grouped by specified signature
  • Min Duration: Minimum duration of current group of matched hotspots
  • Max Duration: Maximum duration of current group of matched hotspots
  • Avg Duration: Average duration of current group of matched hotspots
  • VMR: It stands for Variance to Mean Ratio. It is the standard deviation of duration

Flowpath Stats

Flowpath

Flowpath consists of controlled flow of fully qualified methods invocation that is called for serving user request.

Understanding the Metrics

  • Total Flowpaths: It shows total count for Flowpath Instance generated in a test run.
  • Flowpaths per sec: It shows Flowpath generated per second.
  • Flowpath Duration (ms): It shows Flowpaths durations in milliseconds

Graphs regarding Flowpath

DB Queries Statistics

DB Queries

DB queries are used for extracting useful information from database in the form of result sets.

DB Query metrics

 

Understanding the Metrics:

  • All DB Queries per sec– Total DB Queries count.
  • All DB Queries Duration (ms) – Duration of total DB Queries in milliseconds.
  • Select DB Queries per sec – Select type DB Queries Count.
  • Select DB Queries Duration (ms) – Duration of Select type DB Queries in milliseconds.
  • Insert DB Queries per sec-Insert type DB Queries Count per second.
  • Insert DB Queries Duration (ms) -Duration of Insert type DB Queries in milliseconds.
  • Update DB Queries per sec-Update type DB Queries Count per second.
  • Update DB Queries Duration (ms) -Duration of Update type DB Queries in milliseconds.
  • Delete DB Queries per sec-Delete type DB Queries Count.
  • Delete DB Queries Duration (ms) -Duration of Delete type DB Queries in milliseconds.
  • Create DB Queries per sec-Create type DB Queries Count per second.
  • Create DB Queries Duration (ms) -Duration of Create type DB Queries in milliseconds.
  • Drop DB Queries per sec-Drop type DB Queries Count per second.
  • Drop DB Queries Duration (ms) – Duration of Drop type DB Queries in milliseconds.
  • Other DB Queries per sec– Other database queries per second, ex: stored procedure calls etc.
  • Other DB Queries Duration (ms) – Duration of miscellaneous queries in milliseconds.

Graphs regarding DB Queries

Method Stats

Fully qualified methods are used for monitoring purpose called as Method monitor. It monitors the total invocation of a fully qualified method in a test.

Understanding the metrics

  • Total Method Invocations: It shows the total method invocation for a particular method.
  • Method Invocations/sec: It shows total method invocations per second.
  • Method Execution Time (ms): It shows method execution time in milliseconds.

Graphs regarding Method Monitor

 

Exception Stats

Exceptions are used for monitoring purpose called as Exception Monitor. It monitors the total invocation of a particular exception in a test run.

Understanding the Metrics

  • Total Exception Invocations: It shows the total exception invocation for a particular exception.
  • Exception Invocations/sec: It shows total exception invocation per second.

Graphs regarding Exception Monitor

 

HTTP Headers Condition Stats

HTTP Headers are used for monitoring purpose called as HTTP Headers Condition Monitor. It monitors total request invocation of a particular HTTP condition Header in a test run.

Understanding the Metrics

  • Total Requests: It shows total requests for HTTP condition monitors which are applied in test run.
  • Requests/sec: It shows total requests per second.

Graphs regarding HTTP Condition Monitor

72

Integration Point Stats

Integration point is an end-point of the tier hierarchy that stores/provides information on the requests sent to server, such as DB calls, coherence calls, and so on. These serve data to front-end servers. A backend server which can service many front-end servers at same time and act like an integrated data point so it is known as Integrated point. Following are the stats provided on integration point level.

Understanding the Metrics

  • Total Calls: It provides total calls made to the integration point.
  • Calls/Sec: It provides number of calls made per second.
  • Average Response Time (ms): It provides average response time taken by each call.
  • Errors: It provides number of errors in the calls made to the integration point.

Graphs regarding Integration Point

Business Transactions

A Business Transaction (BT) is the aggregate of all the required software functions and components called upon to deliver an application response to a device or user initiated request. BT examples include purchasing an item, transferring funds, or tracking an order. Following are the stats provided at business transaction level.

Understanding the Metrics

  • Request per second: It provides total number of requests per second
  • Average response time: It provides average response time of business transaction
  • Average request size: It provides the average size of the request
  • Errors/second: It provides number of transactions per second containing error
  • Normal average response time: It provides average response time of the normal category transactions
  • Slow Average Response time: It provides average response time of the slow category business transactions
  • Very slow average response time: It provides average response time of the very slow category business transactions
  • Error average response time: It provides average response time of the error category business transactions
  • Percent slow and very slow transactions: It provides percentage of slow and very slow business transactions
  • Average CPU time: It provides average CPU time taken for the execution of requests.

Business Transactions Graphs

Drill Down Reports in Business Transaction

User can view the following drill down reports for business transactions:

  • Flowpath Group by Business Transaction
  • DB Request Group by Business Transaction
  • Normal Transaction
  • Slow Transaction
  • Very Slow Transaction
  • Error Transaction

Drill Down Reports

User can view drill down reports (based on the metrics in the widget) from Web Dashboard by right-clicking on a widget. For example, here is a snapshot of drill down reports around transactions.

In the subsequent sections, we are describing about integrated Flowpath report where all other reports are included in the same window (by clicking a record). User just needs to scroll for a particular report. To view the integrated flowpath report, right-click a widget, go to Drill Down Reports and click the Flowpath Report link. System displays integrated Flowpath Report.

This window contains information, such as Business Transaction, URL, Category, Start Time, Response Time (ms), Methods, URL, Status code, number of CallOuts, CallOut Errors, Category, CPU Time (ms), Parent FlowpathInstance, Total CPU Time (ms), and others.

  • To view HTTP Report, click the URL link
  • To view Hotspot report, click the Category link
  • To view Method Timing report, click the Response Time link
  • To view Method Call details, click the Methods link
  • To view End-to-end transaction FlowMap, click the Callout link
  • To view DB report, click the DB Callouts link.

Apart from this, flowpath window displays various icons through which a user can perform various functions:

SR. No.IconDescription
1Copy flowpath link
2 Show all flowpaths of selected flowpath’s session
3 Show all flowpaths of selected flowpath’s NV session
4 Open NV Session
5 Open Executive Dashboard
6 Open aggregate flowpaths of selected flowpaths
7 Download as PDF report
8 Download as Word report
9 Download as Excel report
10 Start auto instrumentation
11 View Metadata
12Compare flowpaths
13Delete Cached Data

View Metadata

When a user clicks the View Metadata  icon, metadata report is displayed. This report contains the details of all metadata and mapping of Tier, Server, and Instance as per the topology in tabular form. The mapping section is displayed by default.

Mapping

This section contains three tables that have the mapping of Tier, Server, and Instance as per the topology.

Metadata

This section contains 10 tables, which have the following details:

  • Tier
  • Server
  • Instance
  • Package
  • Class
  • Method
  • Backend
  • Tables Records
  • BT
  • Query

A user can update the tables from DB by clicking the Refresh  icon.

IP Summary

This is an advanced BT Analyzer to capture all respective and individual Integration Point Calls. This section displays BT callout summary and BT callout details. In BT callout summary, the details include – BT name, minimum / maximum / total HTTP callouts, minimum / maximum / total DB callouts, minimum / maximum / total callouts, and flowpaths. It also displays BT callout details.

To view IP Summary, click the Business Transaction link within the FlowPath window.

The user can also check asynchronous call details in IP Summary by clicking ‘Type’ in BT Callout Details section.

The initiation and end of the asynchronous call are displayed in a pop-up window as displayed below.

HTTP Report

HTTP report displays details on various sections, such as http information, request headers, response headers, custom data, session data, and condition data. To view the HTTP report, click the URL link on the Flowpath report window. The HTTP Report is displayed.

Hotspot Report

This report is used to find out a thread that is taking more time in execution or was stuck in the processing. This may cause a spike in the graphical representation of the processing. To view the Hotspot thread details, click the Category link on the flowpath report window. The Hotspot thread details window is displayed.

Thread Hotspot Stats

This displays two sections:

  • Hotspot thread by State: This displays hotspot thread based on various states, such as runnable, waiting, blocked, and timed_waiting.
  • Hotspot thread by Stack depth: This displays hotspot thread based on stack depth.

Hotspot Summary

This section displays a summarized view of hotspot that includes – thread id, thread name, tier, instance, hotspot entry time, hotspot duration, total hotspot duration, thread state, thread priority, and stack depth. The total hotspot count is displayed in the header of this table.

Integration Point Calls

This section displays details of integration point calls that includes – IP name, type, start time, duration, status, and query.

Clicking the query link displays query details in a dialog box.

Clicking on the IP name navigates the user to Integration point health section.

This window displays various information on integration points, such as average response time (ms), maximum response time(ms), response time trend, Calls per second (CPS), CPS trend, total number of calls, total errors, and error trend.

It also displays expanded view of response time trend, CPS trend, and error/sec trend.

Thread StackTrace

This section displays details of thread stack trace based on the selected thread ID. The information displayed are frame, class, method, line, source file, and count. A user can also configure which column to display or hide by clicking the Show/Hide columns  icon. The Count column is displayed only after the user merges stacktrace in thread stacktrace by clicking the Merge StackTrace  icon.

Exception Report

Exception instance report displays detailed information on the exception occurred, such as exception trend, aggregate exceptions (exception class, throwing class, throwing method, and exception count), exception details (tier, server, instance, integration point, time, exception class, message, throwing class, throwing method, line method, and cause), stack trace, and source code.

Note: The exceptions are captured for .NET, Java, and NodeJS agents.

Exception Stats

This section displays two sub-sections. One for group by exceptions where percentage of exception groups (such as PSQLException and NumberFormatException) is displayed and another is exceptions where exception stats (exception by time at X-axis and exception by count at Y-axis) is displayed.

Aggregate Exception(s)

This section provides aggregated details of the exception(s), such as exception class, throwing class, throwing method, and exception count.

Exceptions

This section displays details of an exception. To view details of a particular exception class, click the exception counts within the Aggregate Exception(s) section. The details include tier, server, instance, integration point, time, exception class, message, throwing class, and throwing method.

Stack Trace

This section displays stack trace that contains stack data. On clicking a record from the left, source data is displayed at the right.

User can perform further actions from this section:

  • To view recorded variables, click the  icon.
  • To copy source code, click the   icon.
  • To download method body, click the  icon.
  • To download class file, click the  icon.

Transaction FlowMap

Once business transactions are refined, user can monitor the business transaction performance. Business transaction list contains a high-level information of the application health and performance of a business transaction. It displays information such as, FP details, DB request report, method timing report, hotspot thread details, view related graphs, current instance log, and all instance log.

A user can view the transaction flow map that provides a detailed flow of the transactions. Network delay is also captured for each node of transactions and with respect to each method

.

From this window, user can view other details, such as DB request report, method timing report, hotspot thread details, method call details, exception reports, current instance log, all instance log, and related graphs.

A user can view the ‘DB Requests’ by double-clicking a node. The window displays various details of a query, such as minimum, maximum, and average time (in milliseconds), count, execution time (in milliseconds), error count, and total time (in milliseconds). The user can download the report in PDF, Word, and Excel formats. The user can click the Copy Query  icon to copy the query.

The user can also check asynchronous call details in Transaction Flowmap. To do that, the user must view the Transaction Flowmap in expanded mode by clicking   icon in the upper-right corner. Pause on the callout to view the asynchronous call details.

DB Request Report

DB queries are used for extracting useful information from database in the form of result sets.

It displays two sections – DB Stats and Query. In DB stats section, top 5 DB queries by response time is displayed. It also displays the query details, such as query, first query time, last query time, query count, error count, minimum count, maximum count, and so on. Within the Query section, the complete query is displayed. When a user clicks an area over the Chart, the Query is changed in the lower panel according to the selected area.

Method Timing Report

This section displays the time taken by the methods for their execution. It contains the package name, class name, method name and various categories of time taken for execution. It displays two sections – Method Stats and Method Summary.

Method Stats

Method Summary

Upon clicking the method name, Service Method Timing window is displayed.

HotSpot Thread Details

This feature is used to view the Hotspot thread details. This section displays information on Thread HotSpot Stats, hotspot summary, integration point calls, and thread stacktrace.

Thread Hotspot Stats

This displays two sections:

  • Hotspot thread by State: This displays hotspot thread based on various states, such as runnable, waiting, blocked, and timed_waiting.
  • Hotspot thread by Stack depth: This displays hotspot thread based on stack depth.

Hotspot Summary

This section displays a summarized view of hotspot that includes – thread id, thread name, tier, instance, hotspot entry time, hotspot duration, total hotspot duration, thread state, thread priority, and stack depth.

Integration Point Calls

This section displays details of integration point calls that includes – IP name, type, start time, duration, status, and query.

Clicking the query link displays query details in a dialog box.

Clicking on the IP name navigates the user to Integration point health section.

This window displays various information on integration points, such as average response time (ms), maximum response time(ms), response time trend, Calls per second (CPS), CPS trend, total number of calls, total errors, and error trend.

It also displays expanded view of response time trend, CPS trend, and error/sec trend.

Thread StackTrace

This section displays details of thread stack trace based on the selected thread id. The information displays, such as frame, class, method, line, and source file.

Method Call Details

This section displays a table of all the methods that are called in the business transactions.

It displays method summary, such as method name, percentage, cumulative self-time, average self-time, cumulative wall time, average wall time, cumulative CPU self-time, average CPU self-time, count, wait time, and sync time.

It also displays method calling tree below this section that displays details of all the executed methods. The details include – elapsed time, wall time, percentage, CPU time, Thread ID, Thread, arguments, instance, and class.

User can also configure which column to display or hide.

User can configure column width settings, by clicking the Column Width button.

User can reorder columns by clicking the Reorder Columns button.

User can view the service method timing by clicking the method name within the method summary section.

Exception Report

Exception instance report displays detailed information on the exception occurred, such as exception trend, aggregate exceptions (exception class, throwing class, throwing method, and exception count), exception details (tier, server, instance, integration point, time, exception class, message, throwing class, throwing method, line method, and cause), stack trace, and source code.

Exception Stats

This section displays two sub-sections. One for group by exceptions where percentage of exception groups (such as PSQLException and NumberFormatException) is displayed and another is exceptions where exception stats (exception by time at X-axis and exception by count at Y-axis) is displayed.

Aggregate Exception(s)

This section provides aggregated details of the exception(s), such as exception class, throwing class, throwing method, and exception count.

Exceptions

This section displays details of an exception. To view details of a particular exception class, click the exception counts within the Aggregate Exception(s) section. The details include tier, server, instance, integration point, time, exception class, message, throwing class, and throwing method.

Stack Trace

This section displays stack trace that contains stack data. On clicking a record from the left, source data is displayed at the right.

User can perform further actions from this section:

  • To view recorded variables, click the  icon.
  • To copy source code, click the  icon.
  • To download method body, click the  icon.
  • To download class file, click the  icon.

Show Related Graphs

Show Related Graph is the graphical representation of data captured by different monitors, such as CPU Utilization, Thread HotSpots, Process CPU stats, etc. as per the user requirements.

  1. To view the related graphs, right-click over a tier and click the Show Related Graph option.

2. This displays the related graphs in another window.

3. Upon closing this, related graphs information is displayed in tabular format.

4. Clicking on any graph displays the stats of that particular graph.

5. To set samples, click the Set Sample link, this prompts user to provide the number of start samples and end samples.

6. To view all graphs in one frame, click the  icon.

7. To view all the graphs in multiple frames, click the  icon.

Handling Incomplete and Erroneous Flowpaths messages

If the ND agent finds that a flowpath is incomplete due to some reasons (such as JIT compilation error, test stopped), the flowpath is displayed with grey color and on clicking of Status field it shows relevant messages.

Upon clicking the Status link, error details are displayed.

In IP Summary section, such flowpaths are displayed with  icon.

Upon clicking this icon, error details are displayed.

Dynamic switch to show exact FlowMap

FlowMap UI contains a switch on top-right corner to view actual FlowMap and current FlowMap.

Case -1: View Actual FlowMap is ‘No’

Case – 2: View Actual FlowMap is ‘Yes’ 

Method Timing Report

This section displays the time taken by the methods for their execution. It contains the package name, class name, method name and various categories of time taken for execution.

The Method Timing Report is displayed. This report contains three tabs – Method, Class, and Package. Click on a particular tab to view its details.

Method Call Details

This section displays a table of all the methods that are called in the business transactions. It displays method details, such as elapsed time, wait time, percentage, CPU time, and so on. User can also configure which column to display or hide by clicking the Show/Hide columns  icon.

Sometimes, the methods are highlighted in a color, such as red, yellow, green, blue, and others. Each color has its own meaning. For example, when elapsed time of two adjacent rows is greater than or equal to threshold value in Method Calling Tree, the row is highlighted in yellow color. The user can view the meanings by clicking the Show Method Color Meaning  icon.

User can configure column width settings, by clicking the Column Width button.

User can reorder columns by clicking the Reorder Columns button.

For filter settings, click the Filters button at the upper-right corner. This displays the Method Call Tree Filter Settings window.

Here, the user can configure filter for Method Calling Tree. Upon clicking the Apply button, filters are applied and Method Calling Tree is displayed accordingly.

The user can click  icon to show the callouts in expanded / collapsed form.

The user can also check the asynchronous call details in Method Calling Tree. These are denoted by ‘ASYNC Init’ and ‘ASYNC Exit’ as displayed below.

The user can check the details of initiation of the asynchronous call by double-clicking ‘ASYNC Init’.

The user can check the details of end of the asynchronous call by double-clicking ‘ASYNC Exit’.

The details of a child thread are displayed in the same window but as a new tree. The first method of the corresponding child tree of the new thread is highlighted so that the user can easily view the new thread tree and analyze it.

Sequence Diagram

A Sequence diagram is an interaction diagram that shows how objects operate with one another and in what order. It is a construct of a Message Sequence Chart. A sequence diagram shows object interactions arranged in time sequence. Sequence Diagram can be opened directly from flowpath using flowpath Instance or indirectly from Split View by first clicking on any link then on Sequence Diagram tab..

Using Flowpath Instance

Click the Flowpath instance as below:

This opens up the Sequence Diagram tab.

Here, user can view the complete details, such as package, class, methods details by mouse hover:

User can view Tier Callout details by mouse hover on a tier callout:

User also has an option to view child sequence diagram and exception:

The user can also check asynchronous call details in Sequence Diagram. The initiation details of the asynchronous call can be viewed when the user pauses on the   icon.

The user must scroll down and pause on  icon to view the ending details of the asynchronous call.

For filter settings, click the Filters button at the upper-right corner. This displays the Sequence Diagram Filter Settings window.

Here, user can configure filter for sequence diagram. Upon clicking the Apply button, filters are applied and sequence diagram is displayed accordingly.

DB Report

DB queries are used for extracting useful information from database in the form of result sets.

It displays two sections – DB Stats and Query. In DB stats section, top 5 DB queries by response time is displayed. It also displays the query details, such as query, first query time, last query time, query count, error count, minimum count, maximum count, and so on. With in the Query section, the complete query is displayed.

Common Filters

User can apply common filters to view the desired results across all reports. To do this, click the filter UI icon  on the top-left corner of the window. This displays the common filters based on the report selected.

Categories of Filters:

There are following categories of filters:

  • Report Filter
  • Time Filter
  • Group By and Order By
  • Common Filters
  • Request Status
  • Script Filters
  • User Filters

Report Filter

User can change the report type and can apply other filters to open another report.

This displays the report based on the report filter.

Time Filter

User can select the time filter from a specified range or can select a custom time.

Custom Time

In case of Custom time, user needs to provide the date and time within the “From” and “To” fields.

Group By and Order By

The GROUP and ORDER BY clauses are both used to organize data.

 Group By: User can select the fields on which the records are to be group by. User can select multiple columns. The GROUP BY clause’s purpose is summarize unique combinations of columns values.

 Order By: Based on the ‘group by’ columns, user can select the fields for ‘order by’. The ORDER BY clause’s purpose is to sort the query result by specific columns.

Common Filters

There are following common filters: Tier, server, instance, business transaction, business transaction category, and integration point. BT categories includes – Normal, Slow, Very Slow, and Errors.

Below is an illustration of using common filters for BT IP Summary report.

  1. Select the report type as IP Summary and specify the time filter.

2. Within the Common Filters section, select the tier, server, and instance names. These names are displayed in alphabetical order in their respective fields. 

  1. Then, select the BT from the drop-down list.

  1. Then, select integration point accordingly.

  1. Post specifying the filters, the BT IP Summary report is displayed accordingly.

Request Status: User can filter records based on the request status, such as all success, all failures. User can also select the failure type from the available options, such as ConFail, MailBoxError, WriteFail, Reload, Stopped and so on.

Script Filters: User can also filter scripts based on various fields, such as URL, Page, Script, and transaction.

Flowpath Filters

User can also filter records based on flowpath data. These filters includes:

  • Total Response: Specify the operator and filter value for response time. For example – Response time > 20 ms.
  • Methods: Specify the operator and filter value for method time. For example – Method time > 20 ms.
  • Corr ID: Specify the correlation ID to be filtered, and then select the function, such as Exact, StartsWith, EndsWith, and Contains.
  • Order By: Specify the order in which the Flowpath details should be sorted by selecting an option such as Total Response Time, Callout Errors, and Cpu Time from the drop-down list.

Example: Flowpath with Common Filters

Example: Hotspot with Common Filters

Example: Method timings with Common Filters

Example: DB Queries with Common Filters