Symptoms

• DPOD issues internal alerts about misconfigured log targets.
• Transactions from a certain domain or several domains are not showing in DPOD.
• Transactions from one domain appear in a different domain than they should.

Cause

Each log target that DPOD creates in the Gateway has a unique ID to identify the gateway and the domain it belongs to. DPOD scans the gateways' log targets configuration and generates an internal alert when it detects a log target that is configured with a wrong ID.

This might be caused by:

1. Exporting and importing domains between gateways without a deployment policy that excludes the log targets.
   The import will replace the log targets of the target domain with the log targets of the source domain, so the log target of the target domain will use the ID of the source domain, instead of those that DPOD set for the target domain.

2. Replacing an existing DPOD installation with a new one for monitoring the same DataPower gateways, without setting the log targets on all gateways form the new installation.

Resolution

To setup the log targets again and assign them with correct IDs, go to Manage → Devices → Gateways, click the gateway and under the “Setup” tab click “Setup Syslog for Device” and “Setup Syslog for all domains”.