This category | controls the following |
apama.socket | Socket-level communications. |
apama.messaging | Internal messaging-related messages. |
apama.debughandler | Correlator EPL debugger. |
apama.streams | Stream queries within EPL. |
apama.jms | Correlator-integrated messaging for JMS. |
apama.status | Correlator status lines. |
apama.connectivity | Connectivity plug-ins - framework. |
com.softwareag.connectivity | Connectivity plug-ins - Java framework. |
com.apama.jmon | JMon framework. |
com.apama.correlator.jms | Correlator-integrated messaging for JMS. |
connectivity.chain.ChainName | Connectivity plug-ins - chain-related messages. |
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.PluginName. ChainName | Connectivity plug-ins - messages from a specific plug-in. Applies to connectivity plug-ins written in both C++ and Java. |
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. |