What are the values for introscope.enterprisemanager.transactiontrace.filter.types?

Document ID : KB000011919
Last Modified Date : 14/02/2018
 Show Technical Document Details
Introduction:

 In APM 10.1 and later, a new feature was added -- Transaction Trace EM AppMap plugin. This allows appmap data to be derived from transaction traces

This knowledge document talks about how to set the type of transaction trace to be generated.
Question:

   I want to know what are possible values for introscope.enterprisemanager.transactiontrace.filter.types? I found a comma-separated example

  # Comma separated list of TT types to be matched, TTs of all other types will not be considered for processing
  # to generate AppMap artefacts.

   introscope.enterprisemanager.transactiontrace.filter.types=Normal,Sampled
Environment:
APM 10.1 through APM 10.5 when introscope.apm.appmap.legacy.data.source = false is set (To use transaction tracing instead of legacy tracers.) This property is removed in APM 10.7
Answer:

  There are six possible values:

  -  Normal  -- A traced transaction that was caught by the transaction tracer.

  -  Sampled -- A traced transaction that was sampled by the agent automatically.

  -  ErrorSnapshot -- An error snapshot as discovered by ErrorDetector.

  -  LeakHunterSnapshot -- A potential leak event collected by LeakHunter.

   - LeakHunterStackSnapshot  -- A stack snapshot collected by LeakHunter.

   - Stall -- A transaction that has begun execution but has stalled.

   - WhatsInteresting -- An event describing in simple language an interesting behavior in the system as discovered by one of the analytical heuristics in Introscope.

   - BundledTrace  -- Transaction trace that records only boundary components in its stack. Used for feeding the dependency map   

   - Property Change -- Event for Agent Property Change

 
Additional Information:

  How to Enable/Disable the EM Transaction Trace (TT) Plugin  TEC1078896

  https://support.ca.com/us/knowledge-basearticles.tec1078896.html