What it can do for your business

DynamicPULSE is an application monitoring tool that specializes in an application's internal monitoring. DynamicPULSE has the following characteristics:

  • Can be attached with a simple setting
  • Implements monitoring without the user's awareness
  • Automatically measures the processing time of the application
  • Records the application's parameter/return value/SQL

for Support Desk

Using DynamicPULSE, the details of the operations can be traced. The support desk members can easily understand the user’s operation and respond quickly to the user’s inquiry.

for Application Maintenance

Using DynamicPULSE, problems in the application can be promptly understood. Application developers can solve the application’s issues quickly and improve the satisfaction of end users.

for Service Manager

Using DynamicPULSE, the Service Manager can confirm the trend of usage and grasp which function should be improved as priority.

Key features

Operation History

Task log and point log contents can be viewed in Operation History view. Log information corresponding to a single user operation of an application is called the task log. A task log may consist of multiple point logs representing the contents of internal processes. A point log has a structure representing the method calling hierarchy in a task, which corresponds to the method calling of a class.

Operation History

Task log and point log contents can be viewed in Operation History view. Log information corresponding to a single user operation of an application is called the task log. A task log may consist of multiple point logs representing the contents of internal processes. A point log has a structure representing the method calling hierarchy in a task, which corresponds to the method calling of a class.

Web Transaction Trace

For the point log's detailed information, method names are arranged in a tree structure as shown below. The structure shows the call relationship. The time spent to execute the method and the percentage of the processing time to the total processing time are shown on the right of the method name.

Web Transaction Trace

For the point log's detailed information, method names are arranged in a tree structure as shown below. The structure shows the call relationship. The time spent to execute the method and the percentage of the processing time to the total processing time are shown on the right of the method name.

Request Analysis

The object of the parameter and return value can be confirmed here. The object is being parsed in the Application Agent-side, and the parsed data is being recorded as a JSON string.

Request Analysis

The object of the parameter and return value can be confirmed here. The object is being parsed in the Application Agent-side, and the parsed data is being recorded as a JSON string.

SQL Performance Analysis

SQL statements (SELECT, INSERT, UPDATE, DELETE, etc.) that are actually called will be displayed in SQL.

SQL Performance Analysis

SQL statements (SELECT, INSERT, UPDATE, DELETE, etc.) that are actually called will be displayed in SQL.

    Operation History

    Task log and point log contents can be viewed in Operation History view. Log information corresponding to a single user operation of an application is called the task log. A task log may consist of multiple point logs representing the contents of internal processes. A point log has a structure representing the method calling hierarchy in a task, which corresponds to the method calling of a class.

    Web Transaction Trace

    For the point log's detailed information, method names are arranged in a tree structure as shown below. The structure shows the call relationship. The time spent to execute the method and the percentage of the processing time to the total processing time are shown on the right of the method name.

    Request Analysis

    The object of the parameter and return value can be confirmed here. The object is being parsed in the Application Agent-side, and the parsed data is being recorded as a JSON string.

    SQL Performance Analysis

    SQL statements (SELECT, INSERT, UPDATE, DELETE, etc.) that are actually called will be displayed in SQL.

Essential information

  • Operation History: Task log and point log contents can be viewed in Operation History view. Log information corresponding to a single user operation of an application is called the task log. A task log may consist of multiple point logs representing the contents of internal processes. A point log has a structure representing the method calling hierarchy in a task, which corresponds to the method calling of a class.
  • Web Transaction Trace: For the point log's detailed information, method names are arranged in a tree structure as shown below. The structure shows the call relationship. The time spent to execute the method and the percentage of the processing time to the total processing time are shown on the right of the method name.
  • Request Analysis: The object of the parameter and return value can be confirmed here. The object is being parsed in the Application Agent-side, and the parsed data is being recorded as a JSON string.
  • SQL Performance Analysis: SQL statements (SELECT, INSERT, UPDATE, DELETE, etc.) that are actually called will be displayed in SQL.
  • Access Statistics: Access Statistics view regards task logs as access count and can analyze data based on the aggregated access statistics information.
  • Ranking: Ranking view, processes problems can be extracted/analyzed based on the rankings, which were aggregated based on the performance information recorded in the task log.
DynamicPULSE is an application monitoring tool that specializes in tracking the internal operations of the application using simple settings.

Company information

DynamicPULSE

Provided by FUJITSU SYSTEMS WEB TECHNOLOGY LIMITED

DynamicPULSE