Created: | Updated:
Why is IronTap dropping SMF records?
Answer: The following steps provide you with an overview of the most common pitfalls and how to solve them:
Step 1: Verify that SMF records enabled
Verify that z/OS clients stream supported SMF records streamed to the Kafka cluster.
Step 2: Verify that the instrumented applications call mainframe LPARs that are monitored by z/IRIS
Note that several load-balancing mechanisms on the mainframe may distribute the work among different LPARs, CICS regions, etc.
Step 3: For Distributed Db2 observability, check that JDBC application has the required environment variables set
Step 4: Is IronTap integration configured correctly?
For information on how to configure z/IRIS integration with OpenTelemetry, refer to Configuring IronTap OpenTelemetry integration
Step 5: Is the correct EBCDIC code page set in the IronTap config file?
Refer to Configure IronTap to find out more about EBCDIC code page configuration in IronTap is correct
z/OS applications might use code pages that differ from the system default code page.
Step 6: Ensure that your application is correctly instrumented by the agent
Refer to Troubleshooting OpenTelemetry integration for instructions on debugging OTEL integration issues
How do I share my IronTap logs with support?
Ensure agent logs are active
Ensure IronTap logs are active
Run the relevant business applications for which tracing or metrics are needed
Attach the following files to your support ticket:
APM agent logs (regular log file as well as the metrics/traces log)
How do I extract or collect SMF records for my z/IRIS support issue?
Why is the zos.db2.cpu.time and zos.db2.elapsed.time zero?
Answer: The mainframe administrator has to activate class 2 & 3 like in the following Db2 transaction trace-set:
-START TRACE(ACCTG) CLASS(1,2,3) IFCID(3) DEST(SMF) TDATA(CORRELATION)