IBM DataPower Operations Dashboard v1.0.13.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

The Log Target Analysis Level determines how many syslogs will be sent from the monitored device to DPOD.

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

Analysis Level NameMessage GroupsLog Level
Max DataCore, MemoryReqRes, B2B, MemActionLevel, ReqPayloadSize, ExtLatency, Sidecallsinfo
More DataCore, MemoryReqRes, B2B, MemActionLevel, ReqPayloadSize, ExtLatencyinfo
BalancedCore, MemoryReqRes, B2B, MemActionLevelnotice
More TPSCore, MemoryReqRes, B2Bnotice
Max TPSCore, MemoryReqRes, B2Berror


Message Group NameDescription
CoreRequired, DPOD may not show any data without this message group
MemoryReqResRequired, DPOD may not show any data without this message group
B2BThis 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
MemActionLevelThis message group will populate the memory graph in the transaction page,
DPOD can show some basic data even without this message group
ReqPayloadSizeThis message group  will populate service request size information in some dashboards, such as the Recent Activity dashboard
ExtLatencyThis message group will populate the transaction's extended latency details in the transaction page.

SideCallsWill show sidecalls details in the transaction page

Customize Message Groups

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


  • No labels