This category | controls the following |
apama.applicationEvents | Correlator application event logging. Provides detailed output of the inner workings of the correlator, such as context-state changes, event triggering, spawning, routing, etc. To enable application event logging, you have to set the log level of this category to DEBUG. See also
Viewing garbage collection and application events information. |
apama.connectivity | Connectivity plug-ins - framework. |
apama.debughandler | Correlator EPL debugger. |
apama.jms | Correlator-integrated messaging for JMS. |
apama.messaging | Internal messaging-related messages. |
apama.socket | Socket-level communications. |
apama.status | Correlator status lines. |
apama.streams | Stream queries within EPL. |
apama.verboseGC | Correlator garbage collection messages for all monitors. To enable garbage collection logging, you have to set the log level of this category to DEBUG. See also
Viewing garbage collection and application events information. |
apama.verboseGC.MonitorName | Correlator garbage collection messages for the specified monitor. To enable garbage collection logging, you have to set the log level of this category to DEBUG. See also
Viewing garbage collection and application events information. |
com.apama.correlator.jms | Correlator-integrated messaging for JMS. |
com.apama.jmon | JMon framework. |
com.softwareag.connectivity | Connectivity plug-ins - Java framework. |
connectivity.PluginName. ChainName | Connectivity plug-ins - messages from a specific plug-in. Applies to connectivity plug-ins written in both C++ and Java. |
connectivity.TransportName. ManagerName | Connectivity plug-ins - messages from managers. |
connectivity.apama. hostPluginName.ChainName | Connectivity plug-ins - messages from the specified host plug-in. The valid host plug-in names (such as eventMap) are listed in
Host plug-ins and configuration. |
connectivity.chain.ChainName | Connectivity plug-ins - chain-related messages. |
plugins.PluginName | EPL plug-ins - in C++, Java or Python. Note that handling of Java logging is slightly different to EPL and Python. By convention, we recommend Java EPL plug-ins should specify plugins.PluginName when creating the Logger object, for example, com.apama.util.Logger.getLogger("plugins.MyPlugin"). However, this is only a convention, and if some other string or a Java class is specified instead, then that will be used as the correlator's log category. Keep in mind that the logging for the EPL plug-ins is about logging from Java, Python and C++ plug-ins that can be called from EPL. For information on logging from EPL itself, see
Setting EPL log files and log levels in a YAML configuration
file. |