...
Each analysis level is composed of message groups that allow DPOD to show information about the transactions (see the message groups descriptions below)
In addition, each analysis level will show syslog messages only equal or above a certain log level.
The message groups and log level for each analysis level are configurable from the system parameters.
The Default for IDG domains is Max Data
The Default for API Connect domains is Balanced
...
| Message Group Name | Description |
|---|---|
| Core | Required, DPOD may not show any data without this message group |
| MmeoryReqResMemoryReqRes | Required, DPOD may not show any data without this message group |
| B2B | This message group will enable special B2B filters in the Raw Messages page (like "B2B Message ID" and "B2B From Partner ID"), DPOD will show B2B transactions even without this message group |
| MemActionLevel | This message group will populate the memory graph in the transaction page, DPOD can show some basic data even without this message group |
| ReqPayloadSize | This message group will populate service request size information in some dashboards, such as the Recent Activity dashboard |
| ExtLatency | This message group will populate the transaction's extended latency details in the transaction page. |
| SideCalls | Will show sidecalls details in the transaction page |
...
If you wish to add or remove specific syslog messages from a message group, you can specify an override file, change the system parameter "Transaction Analysis Level - User Override Path" to specify the file's location
The file should contain one or more lines to add or remove messages to message groups,
To add messages to a message group use:
+.messageGropName.syslogMessageCode=logLevel.logCategory,logLevel.logCategory,logLevel.logCategory
For Example
+.MemActionLevel.0x80e0013f=debug.memory-report
Will add the message 0x80e0013f (debug log level and above, on log category memory-report) to the message group MemActionLevel
+.B2B.0x80123456=debug.b2bgw, error.mpgw
Will add the message 0x80123456 (debug log level and above, on log category b2bgw, and error log level and above for log category mpgw) to the message group B2B
Similarly, remove a message from a message group by adding the line:
-.messageGropName.syslogMessageCode=logLevel.logCategory,logLevel.logCategory,logLevel.logCategory
For example:
-.MemActionLevel.0x80e0013f=debug.memory-report
Will remove the message 0x80e0013f (debug log level and above, on log category memory-report) from the message group MemActionLevel