AI is where everything is going today. The goal of OMEGAMON Data Provider has been to feed z/OS metrics derived by OMEGAMON Agents to as many analytic platforms as possible. Up to this point, ODP has supported TCP, Kafka and Prometheus connections to a wide variety of analytic platforms. Prometheus is an HTTP(S) pull request.
With the introduction of APAR OA65247/PTF UJ93616, ODP now adds the HTTP/HTTPS Post protocol as an additional means for communicating. Like TCP and Kafka, the new HTTP(S) is a push of data to analytic platforms. In particular, this was done to enable IBM® Instana Observability on z/OS®customers that choose a SaaS deployment model that is based on OpenShift. OpenShift does not support the TCP TLS security protocol, only the HTTPS protocol.
HTTP is about new ODP functionality. With the announcement of OMEGAMON AI Insights, ODP is feeding data to a new AI service to identify anomalies within z/OS, Networks and Java Virtual Machines. Check out this blog for an overview of that offering.
How to configure HTTPS
It's not much different than a TCP connection. The JSON output is the same. It has its own section within connect.yaml used for getting access.
Make the connection secure
And the reason it was implemented was to include the security features of HTTPS. Here are the various ways that ODP can be secured.
OMEGAMON Data Provider continues to evolve. More data targets accessible now with the addition of HTTP. And ODP is evolving as an engine to introduce new AI capabilities. We are far from done. Stay tuned for future innovations.
As always, our master blog has accumulated all these blogs as a central repository to get more information specific to ODP and will now include content around OMEGAMON AI Insights.