March 2022: APAR OA62775
Support for IMS and JVM monitoring agents, and other new function.
- Support for more monitoring agents
-
- IMS:
- IBM OMEGAMON for IMS on z/OS, V5.5
- Java Virtual Machine (JVM):
- IBM Z OMEGAMON for JVM on z/OS, V5.5
- IMS:
- OMEGAMON Data Broker
- New warning messages report records lost due to the OMEGAMON Data Broker record queue limit being reached: KAYB0046W, KAYB0047W.
- OMEGAMON Data Connect
-
- Multiple TCP outputs
- Previously, OMEGAMON Data Connect could send JSON Lines over
TCP to only a single destination. To send to multiple TCP outputs, you had to run multiple
instances of OMEGAMON Data Connect.
Now, a single instance of OMEGAMON Data Connect can send JSON Lines over TCP to multiple destinations.
- Different filter for each output
- Previously, you could specify only a global-level filter that applies to all JSON-format
outputs: TCP, Kafka, and STDOUT.
Now, you can also specify a filter for each output. These are known as output-level filters. If you specify a filter at both levels, the output-level filter replaces the global-level filter.
The combination of multiple TCP outputs and output-level filters means, for example, that a single instance of OMEGAMON Data Connect can send one set of attributes over TCP to Splunk and a different set to the Elastic Stack.
- Starter dashboards
- The starter Elastic Kibana dashboards have moved to a new GitHub repository.
Documentation-only changes:
- Character encoding issues for the YAML documents RKANPARU(KAYOPEN) and connect.yaml.
- Updated example Elastic Stack
configuration:
- Uses data streams instead of time-based indices
- Index names now also include the product code as a qualifier, in addition to the existing table name qualifier