Monitoring with z/OS Connect

The following topics describe the capabilities available in IBM® z/OS Connect to provide monitoring data that enables operational analysis, auditing and tracking of requests.

You can use one or more of the following capabilities in z/OS Connect to monitor API requests.
  1. Started task When z/OS Connect is running as a started task or within a z/OS container, you can monitor activity using interceptors through the following options:
    • Record SMF 123 data by using the audit interceptor. z/OS Connect provides a sample program to format the records, or there are monitoring products that can be used to process the records. For information on IBM monitoring products that use SMF 123 data, see What monitoring is available with z/OS Connect?
    • Monitor the health of APIs through real-time monitoring products such as OMEGAMON® for JVM. For more information, see Monitoring APIs with OMEGAMON for JVM and Using OMEGAMON for JVM to diagnose API failures.
      Note: IBM OMEGAMON for JVM requires APAR OA65632 for 5.5.0 and APAR OA65643 for 6.1.0 to monitor z/OS Connect Servers with the zosConnect-3.0 feature.
    • Deploy end to end tracking of business transactions that flow through z/OS Connect to Z assets by using tools like IBM Z® APM Connect. For more information, see Opens in new window. Using AppDynamics with z/OS Connect EE.
    • When running z/OS Connect as a started task or in a z/OS container, you can write your own z/OS Connect interceptor to monitor requests. For more information, see Extending z/OS Connect.
  2. Configure access log settings for HTTP endpoints in the logFormat attribute string of the httpAccessLogging element of the Liberty configuration for monitoring with Logging Request Headers. For more information, see Logging request headers
  3. zosConnect-3.0 Use the Liberty Microprofile metrics feature. For more information, see Using the Microprofile Metrics feature.
  4. zosConnect-3.0 Use OpenTelemetry to collect, process, and export telemetry data from applications and infrastructure for use in monitoring, troubleshooting, and understanding the behavior of applications and systems. For more information, see Monitoring with OpenTelemetry.

API provider interceptor monitoring

The following image shows the API provider interceptor monitoring options available.

Figure 1. API provider interceptor monitoring options with zosConnect-3.0 and zosConnect-2.0
Diagram showing the different methods available to monitor requests.

API requester interceptor monitoring

The following image shows the API requester interceptor monitoring options available.

Figure 2. API requester interceptor monitoring options with zosConnect-3.0 and zosConnect-2.0
Diagram showing the different methods available to monitor requests.