Skip to main content

Tracking Performance Statistics of Pass-through Services and Operations

Tracking Performance Statistics of Pass-through Services and Operations

To ensure that your ESB system continues to meet the needs of your users, it is important to monitor and track its performance. By performing this monitoring regularly, you can manage any increase in workload by adding resources to handle the increased load. If your pass-through services and operations are using persistent messages, you can use InterSystems IRIS’s monitoring facilities to track and report on performance, but the Activity Volume monitoring provides a mechanism to produce summary performance statistics that are useful for the following:

  • Tracking overall system performance.

  • Ensuring that the system is meeting Service-Level Agreements (SLAs).

  • Identifying potential problems.

If you have suppressed storing persistent messages (see Suppressing Persistent Messages in Pass-through Services and Operations), these summary statistics are your main tool for tracking performance.

The summary statistics consists of the following information for each pass-through service and operation:

  • Total number of messages that completed during a fixed time interval (10 seconds)

  • Total elapsed time to complete processing these messages

As generally true for monitoring performance, it is important to monitor and record performance statistics on a regular basis. This allows you to detect trends and compare current performance to a baseline. This can be useful in determining whether the cause of performance problems is increased load, network issues, problems with the servers providing the services, or ESB performance issues.

The summary statistics mechanism for pass-through services and operations consists of the following components:

  • Configurations and Global settings to enable pass-through services and operations to generate the statistics.

  • Daemons to get the statistics from the pass-through services and operations and send them to a daemon to store the statistics.

  • User interface to monitor and explore the statistics.

For details, see Monitoring Activity Volume in Monitoring Productions.

FeedbackOpens in a new tab