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 only show syslog messages that are equal or above a certain log level.
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 Level |
|---|---|---|
| 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 are assigned to each analysis level from the system parameters (For example, the parameters "Transaction Analysis Level - Balanced" will assign message groups and log level to the Balanced analysis level)
In most cases, you can leave the default analysis levels setup
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 location in the system parameter "Transaction Analysis Level - User Override Path"
...
For example:
-.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
| Note |
|---|
Changing message groups setting may have tremendous impact on DPOD performance, DPOD functionality and also on network utilization. Supporting customers for performance issueissues will be performingperformed on default message group setting only. |