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: Verify that the APM agent is up and running
The agent has to be installed and started (Full APM mode) on the same machine the Java application is running on. On Linux, use the following command to view the current state of the agent:
sudo service instana-agent status
If the agent is not running, use the following command:
sudo service instana-agent start
Step 4: For Distributed Db2 observability, check that JDBC application has the required environment variables set
Step 5: Is IronTap integration configured correctly?
To configure z/IRIS integration with Instana, refer to Configuring Instana APM integration
For information on how to configure z/IRIS integration with OpenTelemetry, refer to Configuring IronTap OpenTelemetry integration
Step 6: 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 7: Ensure that your application is correctly instrumented by the agent
Set the agent log level to debug either via the UI or the agent config
Restart your application
Entries like 'Successfully instrumented class com.ibm.db2.jcc' should appear in the agent logs
Step 8: Activate ‘Logging Metrics’ or ‘Traces’ to monitor the agent
Enable "Logging Metrics or Traces to File" as described in the Instana Agent documentation
Ensure that the agent is creating traces for your application
Refer to https://mainstorconcept.atlassian.net/wiki/spaces/ZIR/pages/1098252289 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)
Instana APM related FAQ
How do I deactivate the Instana JVM Instrumentation using JDBC 4.0 for Db2 on z/OS?
Answer: Disable the feature by setting:
-Dmainstorconcept.ziris.enable=false and remove z/IRIS related system properties. Restarting the JVM is required for the changes takes effect. Refer to “Activating z/IRIS JDBC instrumentation Instana” for more information.
How do I filter mainframe traces in Instana APM by numeric values?
Answer: Currently this function is not available for call.tag tags in Instana APM. All values within a mainframe trace are String-based.