.Net Agent sending a large amount of (typically backend) traces.

Document ID:  TEC1219994
Last Modified Date:  08/07/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Application Performance Management

Releases

  • CA Application Performance Management:Release:10.2
  • CA Application Performance Management:Release:10.3
  • CA Application Performance Management:Release:10.5
  • CA Application Performance Management:Release:10.1
  • CA Application Performance Management:Release:10.0

Components

  • WILY INTROSCOPE:APMINT
Issue:

A .Net Agent (usually backend agents) sends excessive traces that are not for transaction tracing, sampling, auto tracing, etc.

 

Environment:
This was found in APM 10.2 but could impact all 10.x environments. This can affect any APM 10.x .NET Agent that has cross process transaction tracing enabled with upstream and downstream agents. The problem is happening with downstream agents.
Cause:

  Engineering has discovered there is an issue where the upstream agent triggers transaction traces in the downstream agent. The agent was propagating traces regardless of there is a tail filter or not when introscope.agent.transactiontracer.tailfilterPropagate.enable is set to true.

 Normally you enable this (Set to true) setting on all desired agents to include backend trace data (for example, from the SYSVIEW extension) with Transaction Traces.

Workaround:

  From the upstream JVMs, disable CPTT (cross-process transaction tracing) or set introscope.agent.transactiontracer.tailfilterPropagate.enable=false and restart IIS. This will be fixed soon in a future release.

 

Additional Information:

Note that this issue does not happen with Java Agents.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >