Db2 Query Monitor as a data source for OMEGAMON Data Provider

IBM Z OMEGAMON Data Provider takes z/OS® data, such as metrics and events, and makes it available to analytic platforms, such as IBM® Instana, Splunk, Elastic, and Prometheus. You can set up Db2® Query Monitor to be used by OMEGAMON Data Provider as a z/OS data source.

OMEGAMON Data Provider streaming architecture

Db2 Query Monitor can stream data through the OMEGAMON Data Provider components OMEGAMON Data Broker and OMEGAMON Data Connect, as shown in the following figure:
This flow diagram shows that Db2 Query Monitor uses the Db2 Data Access Common Collector to pass information to the OMEGAMON Data Broker in the ZOWE cross-memory server and then to OMEGAMON Data Connect in the Java runtime environment.

This flow diagram shows that Db2 Query Monitor uses the Db2 Data Access Common Collector to pass information to the OMEGAMON Data Broker in the ZOWE cross-memory server and then to OMEGAMON Data Connect in the Java runtime environment.

The major components in this architectural diagram are:

1. Collector: Db2 Data Access Common Collector (CQC).
CQC makes Db2 Query Monitor data streamable to analytics engines.
2. OMEGAMON Data Broker: A plug-in for the Zowe cross-memory server.
Db2 Query Monitor sends data to OMEGAMON Data Broker for processing. OMEGAMON Data Broker configuration parameters include the host name and port on which OMEGAMON Data Connect is listening.
3. OMEGAMON Data Connect: A Java application that can run on or off z/OS.
Data processed in OMEGAMON Data Broker is forwarded to OMEGAMON Data Connect. OMEGAMON Data Connect configuration parameters identify input and output platforms.