IBM DataPower Operations Dashboard v1.0.14.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Log Target Analysis Levels
- Assaf Cohen (Deactivated)
- Amit Munwes
- Hanan Kenan
The Log Target Analysis Level determines the amount of transactional data that is sent from the monitored device to DPOD.
Usually the default level should be used. However, if messages are dropped (at the monitored device or at DPOD) or network bandwidth becomes an issue, this setting might be used to reduce the amount of transactional data that is sent to DPOD, at the cost of displaying less information about each transaction.
Each analysis level is composed of message groups, which contain the set of messages required to display a certain type of information about the transactions (see the message groups descriptions below). In addition, each analysis level will collect all messages with a minimum severity or higher.
The Default analysis level for IDG and API Connect domains (on DataPower API Gateway) is Max Data
The Default analysis level for API Connect domains (on DataPower Gateway) is Balanced + SideCalls
Analysis Level | Message Groups | Minimum Severity |
|---|---|---|
Max Data | Core, MemoryReqRes, B2B, MemActionLevel, ReqPayloadSize, ExtLatency, Sidecalls | info |
More Data | Core, MemoryReqRes, B2B, MemActionLevel, ReqPayloadSize, ExtLatency | info |
Balanced | Core, MemoryReqRes, B2B, MemActionLevel | notice |
More TPS | Core, MemoryReqRes, B2B | notice |
Max TPS | Core, MemoryReqRes, B2B | error |
Â
Message Group Name | Description |
|---|---|
Core | Required, DPOD may not show any data without this message group |
MemoryReqRes | 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"), |
MemActionLevel | This message group will populate the memory graph in the transaction page, |
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 tab in the transaction page. |
SideCalls | This message group will populate the sidecalls tab in the transaction page |
Customize Analysis Levels
You can configure which message groups and minimum severity are assigned to each analysis level using system parameters.
For example, the parameter "Transaction Analysis Level - Balanced" will assign message groups and minimum severity to the Balanced analysis level.
Changing message groups setting may have tremendous impact on DPOD performance, DPOD functionality and also on network utilization. Supporting customers for performance issues will be performed on default message group setting only.
Customize Message Groups
If you wish to add or remove specific syslog messages from a message group, you can specify an override file. Specify the file's path in the system parameter "Transaction Analysis Level - User Override Path".
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...To remove messages from a message group use:
-.messageGropName.syslogMessageCode=logLevel.logCategory,logLevel.logCategory,logLevel.logCategory...Â
Examples:
+.MemActionLevel.0x80e0013f=debug.memory-report
Will add the message 0x80e0013f (debug log level and above, with 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, with log category b2bgw, and error log level and above withr log category mpgw) to the message group B2B
-.MemActionLevel.0x80e0013f=debug.memory-report
Will remove the message 0x80e0013f (debug log level and above, with log category memory-report) from the message group MemActionLevel