November was a big month for OMEGAMON. There were functional updates to OMEGAMON Data Provider and OMEGAMON AI Insights. New administration functions were added to OMEGAMON Web UI. Each of those enhancements were utilized by the new IBM Z OMEGAMON AI for Db2 6.1 release. A new Situation streaming function has been added to the base OMEGAMON infrastructure. And finally, all suites containing OMEGAMON agents were updated with the latest agent releases and OMEGAMON Web UI functionality.
OMEGAMON Data Provider updates
Several maintenance items have been included in APAR OA68403 that shipped in November 2025. In addition, a new protocol, Splunk HEC, has been introduced to improve the performance and security of connections to Splunk.
OMEGAMON® Data Broker
Minimum supported Zowe™ version raised from 3.0.0 to 3.2.0
OMEGAMON Data Broker is a plug-in for the Zowe cross-memory server. The latest plug-in requires a server from Zowe 3.2.0 or any later 3.x.x.
If you already run OMEGAMON Data Broker using the server that is supplied with OMEGAMON Data Provider, then this change involves no additional upgrade action for you. As before, use the latest supplied load modules. The existing caveat, to ensure compatibility: always use the latest supplied load modules for OMEGAMON Data Broker and Zowe cross-memory server. Don't mix old and new. For a list of the related load modules, see Configuring OMEGAMON Data Broker using the server supplied with OMEGAMON Data Provider.
However, if you run OMEGAMON Data Broker using a server in a separate Zowe installation, then you need to perform one of the following actions. Either:
· Switch to using the server that is supplied with OMEGAMON Data Provider
· Upgrade that separate Zowe installation to Zowe version 3.2.0 or any later 3.x.x
For information to help you make this choice, see Configuring OMEGAMON Data Broker.
Upgraded Zowe cross-memory server
OMEGAMON Data Provider supplies the Zowe cross-memory server load module in TKANMODP(KAYSIS01) and the dynamic linkage base plug-in for the server in TKANMODP(KAYSISDL). These load modules have been updated to match the load modules supplied with Zowe 3.2.0.
Plug-in load module eligible for module sharing
The OMEGAMON Data Broker plug-in load module, KAYB0001, loads into the z/OS® link pack area (LPA). This module is now eligible for the module sharing feature of Zowe, potentially conserving LPA space when a z/OS instance runs multiple instances of OMEGAMON Data Broker.
OMEGAMON Data Connect
HTTP output: Splunk HEC support
The HTTP output now supports sending data to the Splunk HTTP Event Collector (HEC) event endpoint, services/collector/event.
To send data to the Splunk HEC event endpoint, you configure an OMEGAMON Data Connect HTTP output endpoint with the following parameters:
· The Splunk HEC event endpoint URL
· The new parameter format: splunk-hec-event, to instruct OMEGAMON Data Connect to send data in the request format required by the Splunk HEC event endpoint
· Splunk-HEC-specific parameters under the new parameter splunk-hec
For example:
http:
enabled: true
endpoints:
ep1:
url: http://mysplunkserver.example.com:8088/services/collector/event
format: splunk-hec-event
splunk-hec: # Splunk-HEC-specific parameters
token: 01234567-890a-bcde-f012-34567890abcd # Required
# Optional HEC-specific parameters
sourcetype: "odp_{product_code}_{table_name}"
source: odp
host: odp-host
index: odp
# Optional HTTP output parameters, not HEC-specific
compression: true
batching:
enabled: true
batch-size: 100
linger: 30
Existing HTTP output configurations are unaffected. The default value of the new format parameter (format: default) matches the previous behavior of the HTTP output.
Prometheus output: use table primary key fields as default labels
You no longer have to specify metric labels. The labels parameter is now optional.
If you omit labels, then, by default, the Prometheus output uses the primary key fields of the table as labels. For the list of primary key fields of a table, see the primary_key entry in the dictionary provided by the data source. For OMEGAMON monitoring agents as a data source, see OMEGAMON attribute dictionary. For other data sources, see the separate documentation for that software.
OMEGAMON Web UI Introduced
In a previous release, OMEGAMON Data Requestor was introduced. This is a Grafana plug in that enables fast dashboard building and execution by leveraging the ITM REST API and your own copy of the Grafana server. You may have thought that ODR was the name of the new OMEGAMON user interface. This release introduces the new OMEGAMON Web UI or “Web UI” for short. It includes ODR for data access, introduces a new Admin web application and a fully supported Grafana server is now available via IBM Tivoli Management Services. Hundreds of pre-built dashboards have been included to provide an easy to deploy new user experience.
It doesn’t yet replace any existing user interface. The goal is to reduce and eliminate the Tivoli Enterprise Portal functionality. At this time, the monitoring functions of the TEP can be achieved in the Web UI. There are two admin functions included with this release: Situation Editing and Take Action. There are additional admin functions available in both the TEP and E3270UIs. For those looking at a faster migration off the TEP, they might choose to use the monitoring capabilities of the Web UI, the new admin functions of the Web UI and the remaining admin functions within E3270UI. More admin functions are planned that will further reduce the dependencies on TEP/TEPS infrastructure. If there are TEP/TEPS admin functions that you can’t leave today, please let us know at zconcierge@rocketsoftware.com or by submitting an AHA Idea.
For more on the new Web UI functionality, see the new documentation.
OMEGAMON AI Insights V2
Predictive Analytics have been updated to support OMEGAMON for Db2. In addition, the UI has been modified from it's original Kibana to the new OMEGAMON Web UI so it is a seamless experience to go from seeing an anomaly to getting more diagnostic information about its root cause. Several blogs have already been shared to provide additional information.
How OMEGAMON AI gives the possibility to solve problems before these impact the end user experience
Runbook - Db2 Use Case #1 - DSG Group and Connection type CPU Divergence
IBM Z OMEGAMON AI Insights 2.2.0 - Release Note
Streaming Situations to analytic platforms
This functionality is a long time customer request. This will enable the start and the end of a situation that is initiated within a z/OS TEMS to be sent where you need it. One key use is to open a service ticket and then to reduce the severity of that ticket when the situation ends. It's one more means to trigger an action elsewhere to speed the mean time to resolution of the problem.
More details can be found in this blog and in the product documentation.
Introduction of IBM Z OMEGAMON AI for Db2 V6.1
For the first time, in a long time, a new Db2 agent has been introduced that was not in support of a new Db2 product release. As a result, many functional enhancements were introduced, including new uses of ODP and OMEGAMON AI Insights. Rather than repeat all the good works, please see this recent blog.
Summary
Plenty of amazing new functions have been introduced this month and many more to come. If you'd like to learn more, reach out to zconcierge@rocketsoftware.com. If you'd like to see more about OMEGAMON Data Provider or OMEGAMON AI Insights, check the Master Blog out.
#CICS
#db2z/os
#IBMMQ
#IBMZ
#IBMZOS
#IBMAI
#IMS
#IBMInstana
#jvm
#OMEGAMON
#ODP
#OMEGAMONAIInsights
#OpenTelemetry