IBM DataPower Operations Dashboard v1.0.6.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

Version 1 Next »

Default transaction domain are not monitored

This limitation is derived from the monitored device limitation. todo:hk I don't completely understand what this is

Default transaction collects all logs from all domains and currently no filter exists on a log target level to filter all logs from applicative domains.

There is a workaround but it can only work if customer accepts to duplicate all network traffic or only using default domain. contact support for that.

WS-M does not capture Multi Protocol Gateway services

This limitation derives from limitations in the monitored device. However, a user can use an intrusive opath to add a formatter, or use DPOD's custom logging mechanism to add payload
todo:add payload to what? 

Payload size does not display response size

At present, monitored devices do not report the front end response payload size. Nor do they report on the backend request and response.

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 :

 

 

  • No labels