search cancel

Custom Traces are Invalid when Agent in New Mode

book

Article ID: 202139

calendar_today

Updated On:

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?

Cause

Tracer mapping is not set correctly on the new mode. 

Environment

Release : 20.6 

Component : APM Agents

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