IBM Z OMEGAMON Data Provider

IBM Z OMEGAMON Data Provider makes data from z/OS available to various destinations.

Typically, the data consists of metrics or events from z/OS subsystems or applications, and the destinations are analytics platforms that analyze that data.
Data sources for OMEGAMON Data Provider include the following OMEGAMON products or components:
  • OMEGAMON monitoring agents on z/OS
  • Tivoli Enterprise Monitoring Server

Stream situation status updates to OMEGAMON Data Provider

Using the Tivoli Enterprise Monitoring Server and OMEGAMON Data Provider, you can stream situation status updates from your OMEGAMON® monitoring agents to third-party analytics platforms, such as Instana, Splunk, Elastic Stack, Apache Kafka, OpenTelemetry, Prometheus and Grafana. This feature is also referred to as (situation status streaming).

When a situation status changes (the situation starts, stops, becomes true, or becomes no longer true), the Tivoli Enterprise Monitoring Server forwards the activity to OMEGAMON Data Provider. Then, OMEGAMON Data Provider forwards the data to the integrated third-party analytics platform. The transferred data is in JSON format.

To enable situation status streaming, see (Optional) Configure situation status streaming.
Note: When situation status streaming is enabled (KDS_STREAM_SITUATION_STATUS set to Y), it is enabled for all situations; you cannot enable situation status streaming for only specific situations. To disable situation status streaming for all situations, set the value of parameter KDS_STREAM_SITUATION_STATUS to N. If you change the KDS_STREAM_SITUATION_STATUS parameter value, you must restart the monitoring server.
The following table describes the situation properties that are forwarded (in JSON format) from the monitoring server to OMEGAMON Data Provider, and subsequently to the integrated analytics platforms.
Table 1. Situation properties forwarded to the integrated analytics platform
Property Description
product_code The three-character kpp product code of the monitoring agent that owns the table. The value for situation status streaming is ksm.
table_name Name of the table that is mapped for situation statuses.
table_version An integer representing the table schema version.
situation_name Name of the situation with a status change.
predicate Situation formula.
type The type of situation event.

The possible types are as follows:

  • Pure. The situation has no sampling interval; it is not re-evaluated with a specified frequency.
  • Sampled. The situation formula has a specified sampling interval and gets reevaluated based on that interval.
  • Error. The situation formula is incorrect; for example, it fails to properly start.
write_time Date and time when the status change was sent.
system_name Name of the system from which the status change was sent.
sysplex_name Name of the z/OS sysplex from which the status update was sent.
smf_id The SMF ID of the z/OS LPAR from which the status change was sent.
local_timestamp Timestamp value from the Tivoli Enterprise Monitoring Server.

The format for the time values consists of 16 digits as follows: YYYMMDDHHMMSS000

Where:

  • YYY is the number of years since the year 1900.
  • MMDDHHMMSS is months, days, hours, minutes, and seconds, respectively.
  • The last three digits are zeros.
deltastat

Situation status. The possible values are as follows:

  • Started. The situation started.
  • Stopped. The situation stopped.
  • True. The situation rule is triggered.
  • No longer true. The situation was true but the next time the condition is reevaluated, the situation is not true anymore.
  • Situation in error. This value is returned when something is wrong with the situation formula.
situation_results Object with the data on the situation with a status change.

This data is included only when the deltastat value is True.

originnode Origin node. The name of the managed system where the situation was triggered.

This data is included when the deltastat value is True or No longer true.