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
Click to expand instructions ...
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
Click to expand instructions ...
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
Click to expand instructions ...
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
BASH
expected result:
Running.
BASH
If the agent is not running, use the following command:
sudo service instana-agent start
BASH
Step 4: For Distributed Db2 observability, check that JDBC application has the required environment variables set
How do I deactivate the Instana JVM Instrumentation using JDBC 4.0 for Db2 on z/OS?
Click to expand instructions ...
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?
Click to expand instructions ...
Answer: Currently this function is not available for call.tag tags in Instana APM. All values within a mainframe trace are String-based.
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.