Developing Apama Applications > Developing Apama Applications in EPL > Using Correlator Plug-ins in EPL > Using the Log File Manager plug-in
Using the Log File Manager plug-in
Apama includes the Log File Manager plug-in to assist in logging status and diagnostic information from EPL and Java applications. However, rather than using the Log File Manager plug-in directly, you typically route events to the LoggingManager monitor and the LoggingManager monitor calls the functions in the Log File Manager plug-in based on the routed events.
It can be convenient to use the Log File Manager because of its comma-separated value (CSV) output and the ability to query the logging level.
Note: An alternative to the Log File Manager plug-in is to use the engine_management utility to set logging levels and log files, and then insert log statements in your EPL code. You can expect better performance from this alternative. See Setting logging attributes for packages, monitors and events in Deploying and Managing Apama Applications, and Specifying log statements.
The LoggingManager.mon file is in the monitors directory of your Apama installation dirctory. This file defines events and actions that help you log information. The EPL in LoggingManager.mon uses both the Log File Manager plug-in and the Time Format plug-in. As this is quite comprehensive you are unlikely to need to use the Log File Manager plug-in directly, and the latter is only documented here for completeness.
If you find that you do need to directly use the Log File Manager plug-in, specify something like the following right after the monitor statement for the monitor that needs to use the plug-in. This loads the Log File Manager plug-in and assigns it the alias logMgr:
import "Loggingplugin" as logMgr;
The Log File Manager plug-in is available as libLoggingPlugin.so in the lib directory on Unix. On Microsoft Windows it is available as LoggingPlugin.dll in the bin directory.
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.