Custom Traces are Invalid when Agent in New Mode

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• CA Application Performance Management (APM / Wily / Introscope)
• INTROSCOPE
• DX Application Performance Management

Issue/Introduction

Installed SaaS 20.6 Agent and  find an issue with one of our custom probes.

Currently when a tracer is set to “Hc2BlamePointTracerDifferentInstances”, then the AutoProbe throws an error saying the specified tracer class is invalid.

If this is set back to the legacy class “BlamePointTracerDifferentInstances” , the AutoProbe does not complain but it logs that a legacy API is in use and then later throws some “High Concurrency Stall Feature” errors (as noted in https://knowledge.broadcom.com/external/article?articleId=35705).

Is this tracer not valid in the newer version?

Environment

Release : 20.6 

Component : APM Agents

Cause

Tracer mapping is not set correctly on the new mode. 

Resolution

Some tracer names are changed between old and new mode.

Legacy Tracer:

Type: BlamePointTracerDifferentInstances

ClassName: com.wily.introscope.agent.trace.BlamePointTracer

New Tracer:

Type: Hc2BlamePointTracerDifferentInstances

ClassName: com.wily.introscope.agent.trace.hc2.BlamePointTracer

Other Eg:
SetFlag:  TECTMF
TurnOn:  TECTMF

IdentifyMatchingClassesAs: "net.abc.def.*" TECTMF
TraceComplexMethodsIfFlagged:  TECTMF  MethodTimerHC  "Custom|{packagename}|{classname}|{method}:Average Response Time (ms)"
TraceComplexMethodsIfFlagged:  TECTMF  PerIntervalCounterHC  "Custom|{packagename}|{classname}|{method}:Invocations Per Interval"
TraceComplexMethodsIfFlagged:  TECTMF  ConcurrentInvocationCounter  "Custom|{packagename}|{classname}|{method}:Concurrent Invocations"
TraceComplexMethodsWithParametersIfFlagged:  TECTMF  ExceptionErrorReporter  "Custom|{packagename}|{classname}|{method}:Errors Per Interval"
TraceComplexMethodsWithThresholdIfFlagged:  TECTMF  StalledMethodTracer  "Custom|{packagename}|{classname}|{method}:Stall Count" 30000

 

Additional Information

Some customers have reported removing the reference to acc-master.pbl in the agent directives file property 

      introscope.autoprobe.directivesFile=hotdeploy

causes the "MethodTimerHC" tracer to be not recognized by the agent, logging this error in logs several times per second

      [IntroscopeAgent.Agent] CloudEventListener Fetching Instance ID null

The workaround is to add the reference to acc-master.pbl even though it is not used.

      introscope.autoprobe.directivesFile=acc-master.pbl,hotdeploy