Configuring Logging and Debugging for Oracle CEP 15-9
15.2.3 log-stdout
This section provides information on the log-stdout element:
15.2.4 Configuring Severity for an Individual Module
Individual modules of Oracle CEP can specify their logging severity. This severity overrides the default logging severity of Oracle CEP server.
You do this by specifying an entry child element in the logger-severity-properties element in the Oracle CEP server config.xml
file. You may specify multiple entry child elements for any number of modules.
To configure severity for an individual module: 1.
Edit the Oracle CEP server config.xml file.
rotation-time String
The time in k:mm format, where k is the hour specified in 24 hour notation and mm is the minutes.
Default is 00:00 rotation-time-span-factor
Long Factor applied to the timespan to determine the number of
milliseconds that becomes the frequency of time based log rotations. Default is 3600000.
rotated-file-count Integer
Specifies the number of old rotated files to keep if number-of-files-limited is true. Default value is 7.
rotation-size Integer The size threshold, in KB, at which the log file is rotated.
Default is 500. rotation-time-span Integer
Specifies the interval for every time-based log rotation. Default value is 24.
rotate-log-on-startup-enabled Boolean
If true, the log file is rotated on startup. Default value is true.
number-of-files-limited Boolean
If true, old rotated files are deleted. Default is false.
Table 15–4 Configuration Parameters for log-stdout
Parameter Type
Description
name String
The name of this configuration object. stdout-severity
String The threshold severity for messages sent to stdout. Default value is
Notice. Valid values are:
■
Emergency
■
Alert
■
Critical
■
Error
■
Warning
■
Notice
■
Info
■
Debug
■
Trace stack-trace-depth Integer
The number of stack trace frames to display on stdout. A default value of -1 means all frames are displayed.
stack-trace-enabled Boolean If true, stack traces are dumped to the console when included in
logged messages. Default value is true.
Table 15–3 Cont. Configuration Parameters for log-file
Parameter Type
Description
15-10 Oracle Complex Event Processing Administrators Guide
2.
Add an entry child element to the logger-severity-properties element as Example 15–2
shows.
Example 15–2 entry Child Element of the logger-severity-properties Element
logging-service namemyLogServicename
logger-severityWarninglogger-severity logger-severity-properties
...
entry keyCQLProcessorkey
valueDebugvalue entry
... logger-severity-properties
... logging-service
3.
Set the key element to any of the following:
■
Component name : a component name constant exactly as
Table 15–5 lists.
Table 15–5 Logging Component Name Constants
Component Name Constant Description
Adapters Applies to log messages from adapter instances running on the
Oracle CEP server. Cache
Applies to log messages from caching systems and cache instances running on the Oracle CEP server.
Channel Applies to log messages from channels running on the Oracle
CEP server. CQLProcessor
Applies to log messages from Oracle CQL processors running on the Oracle CEP server.
EplProcessor Applies to log messages from EPL processors running on the
Oracle CEP server. Ede
Applies to log messages from the Event-Driven Environment, the Oracle CEP server event-dispatching infrastructure.
EventTrace When set to Info or Debug, allows you to trace events as they
flow through the EPN for all applications. You can dynamically change the severity of this log key using Oracle CEP Visualizer.
At the Info severity, you see log messages like: May 26, 2009 5:53:49 PM PDT Info EventTrace
BEA-000000 Application [helloworld], Stage [helloworldOutputChannel] received insert
event
At the Debug severity, the log messages include details of the event:
May 26, 2009 6:02:34 PM PDT Debug EventTrace BEA-000000 Application [helloworld],
Stage [helloworldOutputChannel] received insert event [HelloWorldEvent: HelloWorld - the current
time is: 6:02:34 PM]
Lifecycle Applies to log messages from Oracle CEP server and
application lifecycle operations.