During load tests, we suppressed reporting of -438 db2 errors because that is what jumped out on the WARN messages in the IntroscopeAgent.log. Even though those errors were suppressed by the agent, we continue to see abnormally high response times during the first 10 minutes of the test. The agent is configured with the NoRedefNoRetrans.jar and NoRedef.profile agent profile.
Release : 10.7.0
Component : APM Agents
To ignore additional errors, add additional ignore properties sequentially. For example, to ignore two types of errors, the properties would look like this:
Those will ignore errors only.
However turning off SessionBeanTracing and SessionBean3Tracing will not trace any SessionBeans at all while the above will only take care of errors, non errors will be reported.
You can also disable the two below properties by setting them to false
For NoRedef (and regular Agent.jar), enabling or disabling either or both the deep instrumentation properties below do matter. See below on what happens if one is enabled but the other is not.
# Note: The following describes the functional behaviour on combination of the two properties
# introscope.agent.deep.instrumentation.enabled and introscope.agent.deep.trace.enabled
# 1. The introscope.agent.deep.instrumentation.enabled property must be enabled
# for the introscope.agent.deep.trace.enabled property to function.
# 2. When introscope.agent.deep.instrumentation.enabled=true and introscope.agent.deep.trace.enabled=true,
# the agent automatically instruments deep transaction trace components and collects deep transaction traces.
# 3. When introscope.agent.deep.instrumentation.enabled=true and introscope.agent.deep.trace.enabled=false,
# the agent automatically instruments deep transaction trace components.
# However no deep transaction trace component data is sent to the Enterprise Manager or displayed.