z Open Dataz Open Data
Overview
  • odp-elastic-samples
  • odp-prometheus-samples
  • cics-performance-analyzer-elastic
  • ims-performance-analyzer-elastic
  • transaction-analysis-workbench-elastic
  • ims-connect-extensions-analysis-splunk
  • Db2 Query Monitor Starter Dashboards
  • Instana Configuration Topics
GitHub
Overview
  • odp-elastic-samples
  • odp-prometheus-samples
  • cics-performance-analyzer-elastic
  • ims-performance-analyzer-elastic
  • transaction-analysis-workbench-elastic
  • ims-connect-extensions-analysis-splunk
  • Db2 Query Monitor Starter Dashboards
  • Instana Configuration Topics
GitHub
  • ODP Prometheus samples

    • Overview

      • Introduction
      • Requirements
    • Installing the dashboards

      • Overview
      • Configure OMEGAMON Data Connect
      • Update the ODP collection configuration
      • Create historical data collections
      • Configure Prometheus and Grafana

Update the ODP collection configuration

  1. On z/OS, edit the ODP collection configuration member RKANPARU(KAYOPEN) to specify the attribute groups required by the dashboard:
collections:
  - product: km5            
    table: ascpuutil        
    interval: 0             
    destination:
      - pds
      - open
  - product: km5            
    table: km5wlmclpx       
    interval: 0             
    destination:
      - pds
      - open
  - product: km5            
    table: m5stgcdth        
    interval: 0             
    destination:
      - pds
      - open
  1. Reload the configuration of collection tasks to reflect the updated KAYOPEN member.

    For the job that runs the OMEGAMON z/OS monitoring agent, enter the following MVS MODIFY system command:

    F <job_name>,KPQ,RELOAD_CONFIG,KAY
    

    Replace <job_name> with the corresponding job name: for example, OMEGDS.

Last Updated: 3/23/22, 5:26 AM
Contributors: David Dai
Prev
Configure OMEGAMON Data Connect
Next
Create historical data collections