AIOps: Monitoring and Observability - Group home

Batch reporting and compression added to HTTP output in OMEGAMON Data Provider

  

In July, IBM has released APAR OA66572/PTF UJ95536 as the latest ODP functional APAR. There are four new functions added in this release: 

  1. Batching in HTTP Output
  2. Compression in HTTP Output
  3. Custom request headers in HTTP Output
  4. Custom metric expiration for Prometheus Output

Batching in HTTP Output

Prior to this APAR, a single record request was sent per HTTP call. This remains the default. New parameters are available to send multiple records per HTTP request which will improve overall throughput. A specified number of records can be aggregated within a single record within a certain amount of specified time, as short as nano-seconds and as long as days.

Compression in HTTP Output

Compression via gzip can be added, to reduce network traffic and improve performance. This is especially useful when output batching has been enabled.

Custom request headers in HTTP Output

New configuration parameters can be added to HTTP output requests. These can be useful within certain analytics platforms.
Each of these HTTP output changes are intended to be leveraged when IBM Instana is the analytic platform of choice. Please see the latest Instana documentation for specific configuration recommendations.

Custom metric expiration for Prometheus Output

A new metric-expiration parameter can be added to each table definition within connect.yaml. The default remains that there is no expiration.

Future ODP Enhancements

Got an idea? What additional functionality? Let us know. Many customers are using ODP functionality now. We’ll consider any request that a business might make.

Summary

As always, additional ODP information can be found within our master blog here.

#CICS
#db2z/os
#IBMMQ
#IBMZ
#IBMZOS
#IBMAI
#IMS
#Instana
#jvm
#OMEGAMON
#ODP
#OMEGAMONAIInsights