Hi,

I am pretty sure that CICS/CTG calls are/were traced at least in Java. I can't find any reference whatsoever though in the documentation. 

Was this discontinued or am I just looking in the wrong space?

Any hint greatly appreciated :-)

Regards,

Rainer

Hi Raine,

Maybe this is what're looking for:

• https://www.ibm.com/docs/en/iofz/1.1.x?topic=components-tracking-cics-transaction-gateway
• https://www.ibm.com/docs/en/iofz/1.2.0?topic=overview-supported-transaction-tracking-flows

Hope it helps,

Hi Israel,

Thanks for the links. As helpful as they are they leave me with the question: Will I see exit calls marked "CTG" in an Instana trace created by auto-trace which will created a service "CTG something" in the services list? The goal for now is only to identify CTG / CCIS calls from the Java side ideally with a transaction ID in the call details.

Downstream tracing is not necessary at this point. 

From the documentation it is not clear if we need to enable something or if it will work just OOTB.

Thanks and regards,

Rainer

In-lieu of the Z Observability component you can use the configuration based SDK to mark CTG exit points.

# Java Tracing
com.instana.plugin.javatrace:
  instrumentation:
#    # Lightweight Bytecode Instrumentation, enabled by default
#    # Disabling currently requires an agent restart
#    enabled: true
#    # OpenTracing instrumentation, disabled by default
#    # Enabling requires an agent restart
#    opentracing: false
#    # To enable using the SDK, provide a list of packages that should be
#    # scanned for SDK annotations. All subpackages are scanned, as it is a
#    # starts-with prefix matching.
#    # Scanning a large amount of classes slows down agent attach and requires
#    # more CPU for parsing, therefore it is recommended to limit to packages
#    # actually using SDK annotations.
#    # By default no packages are scanned for SDK annotations.
      sdk:
        targets:
          ## Trace CICS calls
          - match:
              type: class
              name: com.ibm.connector2.cics.ECIInteraction
              method: execute
            span:
              name: ECIInteraction.execute
              type: EXIT
              stackDepth: 3
              tags:
                - kind: argument
                  name: ECIInteractionSpec
                  index: 0

Thanks Walter,

That'll help. It also means there is no Autotrace for CTG calls in the Java sensor, but config is fine :-)

Regs,

Rainer

# Java Tracingcom.instana.plugin.javatrace:  instrumentation:#    # Lightweight Bytecode Instrumentation, enabled by default#    # Disabling currently requires an agent restart#    enabled: true#    # OpenTracing instrumentation, disabled by default#    # Enabling requires an agent restart#    opentracing: false#    # To enable using the SDK, provide a list of packages that should be#    # scanned for SDK annotations. All subpackages are scanned, as it is a#    # starts-with prefix matching.#    # Scanning a large amount of classes slows down agent attach and requires#    # more CPU for parsing, therefore it is recommended to limit to packages#    # actually using SDK annotations.#    # By default no packages are scanned for SDK annotations.      sdk:        targets:          ## Trace CICS calls          - match:              type: class              name: com.ibm.connector2.cics.ECIInteraction              method: execute            span:              name: ECIInteraction.execute              type: EXIT              stackDepth: 3              tags:                - kind: argument                  name: ECIInteractionSpec                  index: 0