...
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 currently has a limit of 256 Syslog log targets per instance.
Since DPOD currently adds 2 log targets for each monitored domain, including default domain, DPOD can monitor up to 128 domains, if no other Syslog log targets are defined on that device.
Known workarounds: None.
Callacble rule invocation appears as a seperated transaction
At present, callable rule within a transaction appears as diffrent transaction on the Ivestigate.
Known workarounds: None. Resolve this issue is part of product Roadmap
B2B support is limited
At present, B2B has the most important features supported such transaction (IDG term) aggregation . Still Configuration sampling and specific filtering anddashbaoard in dashbaoards are part of the current version.
Known workarounds: None. Resolve this issue is part of product Roadmap
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 Roadmap
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 :
