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 a time sequence. Sequence diagram can be opened directly from flowpath using flowpath Instance or from split view by first clicking on any link and then on sequence diagram tab.

Filters

In filter, you can apply a filter in the sequence diagram. To apply a filter, click on the Filter Filter button the Sequence Diagram Filter Settings window will open where you have to provide the value for the following options:

• Class Name Width (in px): In this option, you have to provide the width for the class name. The value which you will provide will be in Pixels (px).
• Top Methods: In this option, you can see the top methods for the sequence diagram. By default, it will show the Top 5
• Show Methods (walltime in ms)>=: In this option, you can see the methods walltime which will be greater than or equal to the provided value. By default, the walltime is set to 1.
• Highlight Methods (walltime in ms)>: In this option, you can highlight the methods walltime which will be greater than or equal to the value provided. By default, you can see 1500 highlighted methods.

In the Sequence Diagram Settings window, there are the following fields:

• Class Name Width (in px): In this option, you have to provide the width for the class name. The value which the user will provide will be in Pixels (px). By default, the class name is set to 300.
• Top Methods: In this option, you have to provide the value for methods wanted to By default, the top methods are set to 5.
• Show Methods (walltime in ms): This option will show the methods walltime which will be greater than or equal to the provided value. By default, the value for the time to show method is set to 1.
• Highlight Methods (walltime in ms): This option will highlight the methods walltime which will be greater than or equal to the value provided.
• Wall Time: This is the total time a method takes to execute from start to
• Threshold Wall Time: Wall time is the total time taken by a method to complete all its tasks. A threshold wall time refers to the maximum amount of time allocated for a particular process or task to run before it is terminated. By default, the threshold wall time is set to 1500.

Note:

1. You can view the sequence diagram image in a new tab by clicking on the View Image in New Tab
2. To start the dynamic diagnostics, you have to click on the Click to Start Dynamic Diagnostics icon, For details refer to Dynamic Diagnostics Configuration.

Positive Filters

Positive Filters allow you to see all the methods that are related to the selected filter. In the positive filter, choose the value for the following fields:

• Packages: In packages, you have to select the Java package from the drop-down list that they want to import for the method call.
• Classes: In classes, you have to select the required class as per the package that they want to import.
• Methods: In classes, you have to select the required class as per the package that they want to import.

Negative Filters

Negative Filters hide all those methods that are related to the selected filter. In the negative filter, choose the value for the following fields:

• Do not show methods: In this option, the user has to provide the method name that they do not want to show.

Advanced Settings

In Advanced Settings, there are the following options from which you can select as per your requirement:

• Do not filter callouts: In the Do not filter callouts options, there are the following options:
• HTTP CallOuts
• DB CallOuts
• JMS CallOuts
• Error CallOuts
• Thread CallOuts
• DBError CallOuts
• Async Callouts
• Exceptions

Notes:

• If you want to show the thread queue time and self-time, then select the Show All Show All Button.
• Once you have filled up all the fields, click on the Apply Apply button to apply the Method Call Tree Filter Settings.
• You can also reset the Method Call Tree Filter Settings by clicking on the Reset Reset button. If you don’t want to apply the settings, then you have to click on the Cancel Cancel button.

Dynamic Diagnostics Configuration

The auto instrumentation process is time-consuming, as it has to take an in-memory thread dump at regular intervals and find out all methods in active threads. To tackle this shortcoming, Dynamic Diagnostics Auto Instrumentation is implemented. It is a lightweight solution for finding problems in business transactions. Dynamic diagnostics instrumentation is triggered only on the specific business transaction and stack dump is considered only for those threads, which are executing that transaction. We can configure Dynamic Diagnostics by:

• General Settings
• Advance Settings

General Settings

In general settings, you have the following fields:

• Business Transaction: In this field, you have to enter the business transaction executed on the instance, such a Catalog, Product, or Tracking an order. By clicking this you can view the IP summary report.
• Session Name: In this field, you have to enter the name of the session, which is automatically named, based on the business transaction selected. You can also edit the business transaction.
• Session Duration: In this field, you have to specify the duration of the session for which it will be running.
• Completion Mode: This is the action, that has to be taken regarding downloading the instrumentation files, once the instrumentation is completed. There are the following options:
• No Download: If you select this option, then no files will be
• Download files after session: If you select this option, then the files are downloaded after the session is completed.
• Download and apply: If you select this option, then files are downloaded and applied for instance.
• Apply Mode: In this field, you have to select the mode in which you want to apply the dynamic diagnostic configuration. There are following options within this section:
• Apply on Instance: In this option, you can apply the instrumentation on instances without saving the file.
• Apply on Instance and Save: In this option, you can apply the instrumentation on instances and can also save the file. 

Advance Settings

In advanced settings, you have the following fields:

• Maximum stack depth to identify idle threads: In Auto Instrumentation, application agents will ignore idle threads, which have stack depth less than the provided value.
• Sample Interval: In sample interval, you have to enter the sample interval of dynamic diagnostics.
• Trace Level: This is the trace level of dynamic diagnostics auto instrumentation with its level value as Level 1, level 2, Level 3 and so on.
• Number of thread samples to instrument methods: This shows the total number of thread samples used to instrument a method.
• Percentage of executing methods in thread samples to be instrumented: This is the percentage of thread samples used to instrument a method.
• Percentage of executing methods in flowpaths to be un-instrumented: This is the percentage of methods that will be un-instrumented if their response time is very small.
• Maximum method(s) to be considered for Auto Instrumentation: This is the maximum unique method(s) without overloading which will be considered in auto instrumentation process.
• Minimum average execution time of method for Instrumentation (in ms): This method will be un-instrumented if the average execution time of the method less than the provided value.
• Weightage of methods in stack traces having Exception/Integration point calls: All methods in stack traces having exception and integration point calls will have more weightage for auto instrumentation.
• Concurrent Auto Instrumentation Threshold: This is the maximum number of active business transaction serving threads for dynamic diagnostics AI
• Dump data: This shows the quantity of data dump in dynamic diagnostics.
• Thread blacklist filter: This is used for providing the thread names excluded from the dynamic diagnostics AI
• Thread whitelist filter: This is used for providing the thread names included in the dynamic diagnostics AI
• Blacklist filter: This is used for providing BT names excluded from dynamic diagnostics AI
• Whitelist filter: This is used for providing the BT names included in the dynamic diagnostics AI

Notes:

• If you want to remove auto instrumentation session changes just after their completion, then you have to click on the Remove Auto Instrumentation session changes after its completion checkbox.
• If you want to delete the configuration from the server, then you have to click on the Delete from server checkbox.
• If you want to enable auto instrumentation for method capturing, then you have to click on the Enable Auto Instrumentation for Method Capturing checkbox.
• You can also apply method % for each and every level of each applied method by setting the method % for the following three levels:

1. Method % of Level 1: In this option, you can set the method percentage value for Level 1. By default, the level percentage is set to 35%.
2. Method % of Level 2: In this option, you can set the method percentage value for Level 2. By default, the level percentage is set between 35 to 60%.
3. Method % of Level 3: In this option, you can set the method percentage value for Level 3. By default, the level percentage is set between 60 to 85%.

• Once you have provided all the values, you have to click on the Start Start button to start the dynamic logging. If you want to reset the dynamic diagnostics configuration window, you have to click on the Reset to Default Reset to Default Button. If you don’t want to apply dynamic diagnostics, then you have to click on the Cancel Cancel button.
• You can also see the Tier, Server, Instance, Start Time, End Time, Response Time, BT information, URL and keyword information at the top of the sequence diagram window.