IBM RMF Operational Analytics is a software product that helps you monitor and analyze your IT infrastructure. It can help you identify potential problems and take steps to prevent them from happening.
This IBM publication covers IBM RMF Operational Analytics (RMF OA), an offering that is part of IBM Z OMEGAMON Integration Monitor and that lets you monitor the activity of a z/OS environment from a workstation. RMF OA takes its input data from the Distributed Data Server (DDS), stores each collected RMF report in a corresponding Elasticsearch index, and provides sample dashboards and visualizations for key performance indicators, which you can use to build your own customized KPIs.
The guide first describes the basic architecture and the prerequisites, then walks through the installation procedure on z/Linux Red Hat: installing Java, Elasticsearch, Kafka, Zookeeper and the Kafka broker and distributed worker, preparing and running the Ansible-based RMF OA installation file, setting up password encryption, and performing installation checks. A final chapter explains how to use RMF OA, covering spaces, reports, indexes, index patterns, dashboards and visualizations, and ends with notices.
| Operating system | Red Hat Enterprise Linux 8.2.x (x386 or z) |
|---|---|
| Supported z/OS versions | 2.2, 2.3, 2.4, 2.5 |
| Other prerequisites | Java 11, Elasticsearch 7.12.1, Kibana 7.12.1, Kafka 2.4.1 (Scala 2.11), Confluent Kafka Connect Elasticsearch 5.4.1 |
| Required privileges | User account with root privileges (directly or via sudo) |
| Elasticsearch port | 9200 |
| Kafka server port | 8083 |
| Kibana access port | 5601 |
| DDS access port | 8803 |
| Data collection interval | 60 or 100 seconds |
| Resources for 10 LPARs on a single RMF OA node | Memory 64 GB (0–3 months) / 128 GB (4–12 months); disk 0.5 TB / 1 TB; vCPU 16 / 32 |
RMF OA is an offering that helps you monitor and troubleshoot z/OS performance issues while using historical data for trend analysis and analytics, and it is available as part of IBM Z OMEGAMON Integration Monitor.
It takes its input data from the Distributed Data Server (DDS); one DDS per sysplex is needed for a complete overview of the z/OS environment.
Among other prerequisites the guide lists Red Hat Enterprise Linux 8.2.x, Java 11, Elasticsearch 7.12.1, Kibana 7.12.1, Kafka 2.4.1 and Confluent Kafka Connect Elasticsearch 5.4.1.
The guide lists 9200 for the Elasticsearch server, 8083 for the Kafka server and 5601 for Kibana access, and the Kafka server must be able to reach the DDS on port 8803.