APM Mainframe Agent - Insight Metrics

Products

• DX SaaS

Issue/Introduction

Evaluating some of the metrics ingested by the APM DB/2 - Mainframe Agent.  It has been determined a few of the metrics for DB2 can be turned off. 

Ideally, this would be a dynamic change to a config file and refresh the agent, but unfortunately that doesn't seem to be the case and the ingestion of

If APM doesn’t have that capability, what would it take to set something like that up?  As metrics become more important or less important over time or for a specific issue, it would be beneficial to be able to dynamically flip which metrics are being ingested into APM from Mainframe Db2.

Bare minimum, do the following:

Turn off these metrics:

• Blocks
• Bytes
• Rows
• Claim Requests
• Global Lock Suspensions
• Group Buffer Pool
• Locking Highlights
• Locking Statistics
• Logging Statistics
• P-Lock Negotiations

Resolution

To turn off insight mainframe metrics,  modify the metric mappings in the config/InsightMetrics.xml file.  For instance, to turn off "Claim Requests" metrics, the customer could try looking up the "Claim Requests" section in the config/InsightMetrics.xml file and then comment out the entire "sub-categories" xml section for "P-Lock Negotiations" by enclosing the section with "<!-" and "-->" markers, e.g. 

 

        <!-- Claim Requests -->

        <!-- 
        <sub-categories xsi:type="java:com.ca.apm.agent.extension.mainframe.metrics.insight.data.InsightMetricCategory">
           <category-name>(IDB2:DSAISTD) Claim Requests</category-name>
           <metric-path>Claim Requests</metric-path>
           <metric-properties  xsi:type="java:com.ca.apm.agent.extension.mainframe.metrics.insight.data.InsightMetricProperty">
               <result-column-name>CLAIM_REQUESTS</result-column-name>
               <metric-name>CLAIM Requests Count</metric-name>
               <metric-type>NUM_B10_DELTA</metric-type>
           </metric-properties>
        </sub-categories>        

        -->