The Log Target Analysis Level determines how many syslogs will be 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 that allow DPOD to show , 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 only show syslog messages that are equal or above a certain log levelcollect 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 Name | Message Groups | Log LevelMinimum 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 |
...
You can configure which message groups and log level minimum severity are assigned to each analysis level from theusing system parameters (.
For example, the parameters parameter "Transaction Analysis Level - Balanced" will assign message groups and log level minimum severity to the Balanced analysis level)
In most cases, you can leave the default analysis levels setup .
| Note |
|---|
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 . Specify the file's location 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:
| Code Block |
|---|
+.messageGropName.syslogMessageCode=logLevel.logCategory,logLevel.logCategory,logLevel.logCategory |
...
... |
To remove messages from a message group use:
| Code Block |
|---|
-.messageGropName.syslogMessageCode=logLevel.logCategory,logLevel.logCategory,logLevel.logCategory... |
Examples:
| Code Block |
|---|
+.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 |
...
Similarly, remove a message from a message group by adding the line:
-.messageGropName.syslogMessageCode=logLevel.logCategory,logLevel.logCategory,logLevel.logCategory
...
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 |
...
| Note |
|---|
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. MemActionLevel |