Changing the logging level of Z APM Connect's request monitoring exits

Edit online

By default, Z APM Connect's request monitoring exits log messages at the INFO level. To change the logging level, complete this task.

About this task

Z APM Connect request monitoring exits log messages to the output location specified by the user-defined log4j2 configuration. To customize the monitoring exits' log output location, add a log4j2.xml file to the JVM's classpath (and the resource adapter's classpath, if applicable). A sample log4j2.xml is provided with AGM-RequestExit.jar.

To view details about Transaction Tracking events produced by the Z APM Connect request monitoring exits, set the logging level to DEBUG.

Note:
  • For viewing AGMServerExit events, this update is dynamic, and your CICS TG will not need to be restarted.
  • For viewing AGMClientExit events, this update is static, and only newly invoked client applications will print event data.

Procedure

  1. To customize the AGMClientExit's logging level, locate your agmconfig.properties file and set the property agm.ctg.client.logging.level to your wanted logging level. Possible options are TRACE, DEBUG, INFO, WARN, and ERROR.
  2. To customize the AGMServerExit's logging level, locate your agmconfig.properties file and set the property agm.ctg.server.logging.level to your wanted logging level. Possible options are TRACE, DEBUG, INFO, WARN, and ERROR.