...
At present, monitored devices do not report the front end response payload size. Nor do they report on the backend request and response.
Known workarounds: None. Resolve this issue is part of product Roadmap.
Limitation on the number of domains to be monitored on a single gateway
IDG From 7.5.X it might support up to 500 - http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.ibm.dp.doc/logtarget_logs.html (Perior IDG currently has a limit of 256 Syslog log targets per instance.)
By default each domain will have 2 syslog target defined by IDG.
Since DPOD currently adds another 2 log targets for each monitored domain, including and 1 for default domain,
Customer will also have its own log target to other system (like Security tools)
So Number of domain is Equals to : {500 -[Number of Existing Domains * 2] - [Customer predefined syslog targets] }/ 2
DPOD can monitor up to 128 125 domains, if no other Syslog log targets are defined on that device.
Known workarounds: NoneCustomer encouraged to move some of its domains to another device.
B2B support is limited
At present, B2B has the most important features supported such transaction (IDG term) aggregation . Still Configuration sampling and specific filtering in dashbaoards are part of the current version.
Known workarounds: None. Resolve this issue is part of the product Roadmaproadmap
Callacble rule invocation appears as a seperated transaction
At present, monitored devices do not report the front end response payload size. Nor do they report on the backend request and response.
Known workarounds: None. Resolve this issue is part of product Roadmaproadmap
Error is not displayed in "Extended transactions"
The extended transaction is the only feature of DPOD that involves instrumentation of XSLT transformation to the Web Service Proxy policy (request / response and error rules).
The instrumentation is integrated by the system only when initiated by the system administrator and not by default.
when an error is being raised but the service (WS-Proxy) the following situation are possible :
- No error rule in the service that the error is being raised on and previous services are configured with "Process HTTP errors = on"
Since there is no error rule, an extended transaction log record is not being generated and there for the error is not displayed in "extend transactions" screen.
The extended transaction will look similar to the following (you can see that one record is missing) :
- No error rule in the service that the error is being raised on but previous services do have error rule configured
Since there is no error rule, an extended transaction log record is not being generated and there for the error is not displayed in "extend transactions" screen.
Previous services do have error rule so the "extend transactions" screen will look similar to the following :
- The Extended transaction is not supporting APIC / APIM. You must not NOT run it in those DoomainsThe API-C / API-M Domains
- In some cases the Extended transaction is not always work deployed on MPG services because of the diversity of configuration in this Servicesservices. Customer encorage to to open a PMR and provide the service configuration - so this cases can be aligned.