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

book

Article ID: 5299

calendar_today

Updated On:

Products

APP PERF MANAGEMENT CA Application Performance Management Agent (APM / Wily / Introscope) CUSTOMER EXPERIENCE MANAGER INTROSCOPE

Issue/Introduction

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

 

Cause

Engineering has discovered an issue where upstream .NET agents triggers transaction traces in the downstream .NET agents, the agent propagate traces regardless of there is a tail filter or not when introscope.agent.transactiontracer.tailfilterPropagate.enable=true.

Normally you enable this feature on all the desired agents to include the backend trace data (for example, from the SYSVIEW extension)

This defect#DE250285 has been already fixed in 10.5.2.

 

Environment

This issue can affect any APM NET Agent 10.x that has cross process transaction tracing enabled with upstream and downstream agents. This issue do not affect Java Agents

Resolution

From the upstream JVMs, you have 2 options:


Option 1) disable CPTT (cross-process transaction tracing)

Comment the below 2 lines in Webservices.pbd
 
TurnOn: WebServicesCorrelationTracing
TurnOn: WCFRuntimeTracing


Option 2) set introscope.agent.transactiontracer.tailfilterPropagate.enable=false

Restart the managed application for the changes to take effect

 

Additional Information

https://docops.ca.com/ca-apm/10-5/en/implementing-agents/net-agent/properties-reference-net-agent#PropertiesReference.NETAgent-Cross-processTransactionTrace