...
- The nv.aep.sno logger that traces the sequence numbers of inbound and outbound messages
- Enabled via
- nv.aep.sno.trace=debug when using native trace logging
- Settng the level of the nv.aep.sno logger to Trace when using SLF4J
- Enabled via
- The nv.aep.event logger that traces events dispatched to an engine
- Enable via
- nv.aep.event.trace=debug when using native trace logging
- Setting the level of the nv.aep.event logger to Trace when using SLF4J
- Enable via
- The nv.aep.alert logger that traces alert events emitted by the engine.
- Enable via
- nv.aep.alert.trace=info when using native trace logging
- Setting the level of the nv.aep.alert logger to WARN when using SLF4J
- Enable via
- The nv.aep.txn logger that traces the execution of transactions within an engine
- Enable via
- nv.aep.txn.trace=debug when using native trace logging
- Setting the level of the nv.aep.txn logger to Trace when using SLF4J
- Enable via
- The nv.aep.msg logger that traces the flow of messages through an engine.
- Enable via
- nv.aep.msg.trace=debug when using native trace logging
- Settingthe level of the nv.aep.msg logger to Trace when using SLF4J
- Enable via
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
...
<apps>
<app name="processor-send-driver" mainClass="com.neeve.embedded_xvm_sample.driver.SendDriver">
<enableEventTrace>true</enableEventTrace>
<enableAlertTrace>true</enableAlertTrace> <--Since 3.11.61-->
<enableScheduleTrace>On</enableScheduleTrace>
<enableSequenceNumberTrace>On</enableSequenceNumberTrace>
<enableTransactionTrace>On</enableTransactionTrace>
<enableMessageTrace>true</enableMessageTrace>
<messageTraceFilterUnsetFields>true</messageTraceFilterUnsetFields>
<messageTraceInJson>true</messageTraceInJson>
<messageTraceJsonStyle>SingleLine</messageTraceJsonStyle>
<messageTraceMetadataDisplayPolicy>On</messageTraceMetadataDisplayPolicy>
...
</app>
</apps>
... |
...
| Configuration Setting | Description |
|---|---|
| Enables / disables diagnostic trace logging of events received and dispatched by the engine. | |
| Enables / disables diagnostic trace logging of alert events emitted by the engine. | |
| Enables / disables diagnostic trace logging of scheduled events. | |
| Enables / disables diagnostic trace logging related to message sequencing. | |
| Enables / disables diagnostic trace logging of transaction staging. | |
| <enableMessageTrace> | Enables / disables message trace |
| One of JsonPrettyPrintStyle (Default is SingleLine) | |
| One of MetadataDisplayPolicy (Default is Only) | |
| true or false, new feature to filter values for fields that aren't set (instead of display their default values) (Default is true) | |
| true or false, whether or not to output in json format, setting to false uses a more efficient text based display, but doesn't support single line or unset field filtering (Default is True) |
...
Transaction execution trace is not output by a backup agent.
| Anchor | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Alert trace traces any event implement IAlertEvent to the nv.aep.alert logger. For example, an UnhandleMessageEvent emitted because no MessageView factory could be found, would yield trace like:
| Panel |
|---|
<13,343452,TestMachine> 20190314-15:24:13:533 (wrn)...[AepEngine<sma-tck-forwarder>] [ALERT]: [event=UNHANDLED_MESSAGE, type=111, source=sma-tck-forwarder, owners=2, endOfBatch=true, delay=0, scheduledTime=0, dispatchTime=0, time=1552602253523, metadata=[2,3,2300,1,0,0,0,-1,F_BE_1], key=F_BE_1, messageId='18', reason=com.neeve.sma.SmaException: Fault in handling of inbound message by channel [id=18, topic=F_BE_1]: View factory '2300' could not be found] |
Unlike other AepEngine loggers, alert trace is enabled by default. This is because under normal usage patterns alerts are almost always indicative of a problem. Application's that want finer grain control over logging of alert logging can disable alert trace and provide their own EventHandler for IAlertEvent.
| Anchor | ||||
|---|---|---|---|---|
|
See Tracing Messages
...
The trace output by an engine during shutdown is relatively standard and does not warrant special explanation.
The nv.aep.event logger that traces events dispatched to an engine
- Enable via
- nv.aep.event.trace=debug when using native trace logging
- Setting the level of the nv.aep.event logger to Trace when using SLF4J