5.7.2 Checking an Engine Log

The debug information of a CEP engine and the error messages generated at its start or during its operation will be output to an engine log. Rule errors checked when the CEP engine starts will also be output to the engine log.

One CEP engine outputs two engine logs. One is used for output relating to input adapter and high-speed filter processing, and the other is used for output relating to complex event processing and output adapter processing. The engine logs have no predetermined format.

The output destination of each engine log is shown below.

Engine log of the high-speed filter

/var/opt/FJSVcep/cep/flt/logs/EngineLog/CEPengineName/engine.log

Engine log of complex event processing

/var/opt/FJSVcep/cep/cep/logs/EngineLog/CEPengineName/engine.log

If "DebugLogListener" is used in complex event processing rules, processing results will be output to the engine log of complex event processing.

Note

Engine log splitting

If a "DebugLogListener" log of more than 102,400 characters is to be output at once to the engine log, the log will be split and then output. Refer to "Checking when a DebugLogListener log has been split" below for details.

Checking when a DebugLogListener log has been split

If the output results of hits for complex event processing statement conditions exceed 102,400 characters, the output results will be split every 102,400 characters and then output.

At split output, beginning and end identifiers will be added to the split output log. When this happens, only the end identifier will be output in the first output result of the split log, and only the beginning identifier will be output in the last output result.

Beginning identifier

The following content will be output:

YYYY-MM-DD hh:mm:ss,sss [DEBUG]
*****CUT_threadID_nanosecond*****

End identifier

The following content will be output. threadID and nanosecond will have the same values as those of the beginning identifier.

*****CUT_threadID_nanosecond*****

Note

Possibility of log output getting out of sequence

There is a possibility that the processing results of other events being executed simultaneously will interrupt the units into which the log was split. Reference the log according to "Example of output when a log has been split" below.

Example

Example of output when a log has been split

2011-12-07 14:01:13,720 [DEBUG] 6e1619bd-a048-4c64-9efb-306e9f2b88d6:length=100000
6e1619bd-a048-4c64-9efb-306e9f2b88d6[0]
        residence       :12: String
        value   :ON: String
        gatewayId       :00000001: String
(...)
6e1619bd-a048-4c64-9efb-306e9f2b88d6[123]
        residence:30: String
        val
*****CUT_94_19131119552293*****            ... 1.
 
~~~ log of other events ~~~
 
2011-12-07 14:01:13,720 [DEBUG]            ... 2.
*****CUT_94_19131119552293*****
ue      :ON: String
        gatewayId       :00000001: String
6e1619bd-a048-4c64-9efb-306e9f2b88d6[124]
        residence       :38: String
        value   :ON: String
        gatewayId       :00000001: String
(...)
6e1619bd-a048-4c64-9efb-306e9f2b88d6[247]
        residence       :30: String
        val
*****CUT_94_19131119552293*****            ... 3.
 
~~~log of other events ~~~
 
2011-12-07 14:01:13,720 [DEBUG]            ... 4.
*****CUT_94_19131119552293*****
ue      :ON: String
        gatewayId       :00000001: String
6e1619bd-a048-4c64-9efb-306e9f2b88d6[248]
        residence       :38: String
        value   :ON: String
        gatewayId       :00000001: String  ... 5.
 
~~~log of other events ~~~

Explanation of output example:

End of the first part of the split output log. Check the identifier (*****CUT_94_19131119552293*****).
Next beginning of the continuing part of the split output log. This is started using the same identifier (*****CUT_94_19131119552293*****).
Next end of the continuing part of the split output log. This is split using the same identifier.
Similarly, this is split up to the last part using the same identifier.
The end of the last part of the split output log has no identifier.