Cloud Agent limitations

The Cloud Agent feature is currently supported under the following limitations:

• You may connect up to 4 Cloud Agents to a DPOD installation.

• Each Cloud Agent may discover up to 10 DataPower Gateway pods.

• The cumulative transaction rate of all the DataPower Gateways that are connected via Cloud Agents to a DPOD installation should not exceed 40 TPS.

• The Cloud Agent operator was tested only on OpenShift.

Changes to gateway objects

• DPOD requires some configuration changes in the gateways at both device and domain levels. These changes are details in Gateway Changes Performed by DPOD.

...

• In DataPower firmware 7.6, the tenant module was introduced only to physical appliance type 8436.

• Only On tenant devices, only capturing transactions on tenant devices is supported.

• The following features are currently not supported for Tenant tenant devices:

  • Device resource monitoring Appliance Maintenance (CPU, memory, etc.)

  • Maintenance plans (Backup, Sync, Firmware Upgrade)

  • Extended Transaction

...

• This limitation is derived from a limitation of the monitored device.

• Log targets defined at the default domain collect all logs from all domains, and currently there is way to apply a filter to the log targets in order to filter out logs from other application domains.

• Known workarounds: See Monitoring Transactions in the Default Domain for more details.

DPOD integration with API-C can be applied to only a single API Connect domain per DataPower Gateway for firmware lower than 7.6

• This limitation is derived from a limitation of the monitored device.

• Known workarounds: Upgrade to firmware 7.6 / 7.5.2.8 or later.

WS-M does not capture multi-protocol Gateway services payloads for firmware lower than 7.5.2

• This limitation is derived from a limitation of the monitored device.

• Known workarounds:  Upgrade to firmware 7.5.2.1 or later.

Limitation on the number of domains that DPOD can monitor on a single gateway

• Since the DataPower gateway currently supports up to 1,000 log targets, DPOD can monitor a maximum of 333 domains per each gateway, if no other custom log targets are defined. See details and calculation below for more information.
  This limitation is per each DataPower gateway and has no effect on the number of gateways that can be connected to DPOD.

• The total amount of log targets per each DataPower gateway cannot exceed 1,000 and consists of:

  • One required default log target per domain (created when the domain is created with the name default-log), which cannot be removed.

  • Additional custom log targets, created by the customer for non-DPOD use.

  • Log targets created by DPOD - DPOD will create one log target for the default domain, and 2 log targets for each monitored application domain.

• Before you enable DPOD monitoring:

  • Count how many domains should be monitored by DPOD (except the default domain) - DOMAINS_COUNT

  • Count how many log targets already exist in the DataPower gateway - EXISTING_LOG_TARGETS_COUNT
    You can view the existing log targets in the DataPower gateway WebGUI under default domain → Log Target Status → Show All Domains

  • Make sure the following calculation is true:

    Code Block
    EXISTING_LOG_TARGETS_COUNT + (DOMAINS_COUNT x 2) + 1 < 1,000

• Known workarounds: If the number of expected log targets exceeds the limit, do not enable DPOD monitoring. You may use the following methods to allow for DPOD monitoring:

  • Reduce the amount of monitored domains by setting up monitoring only for selected domains (see Configuring Monitored Gateways).

  • Delete unused domains or move domains to another gateway.

  • Delete unused custom log targets that were created for non-DPOD use.

B2B support is limited

• At present, Only the most important B2B features (e.g.: transaction aggregationdetails) are supported. Configuration sampling and specific filtering in dashboards are part of the current version.