IBM DataPower Operations Dashboard v1.0.10.0
A newer version of this product documentation is available.
You are viewing an older version. View latest at IBM DPOD Documentation.
Publish Sync Events via Syslog and Email
Setup
- The maintenance configurable parameters page provides information on how to setup the syslog destination.
- The Email destination is configured in the plan definition.
- Configure the SMTP parameters from the System Parameters Page, see the System Parameters List Page for a description of each parameter
- If you set a value for "The HTTP Address of the UI" parameter - a link to the DPOD UI will be added to the emails with a shortcut to the relevant plan or task execution results.
The following events will be published via Email and/or syslog (as defined in the sync plan):
Plan Events
Sync Plan Completed Successfully
All sync tasks finished successfully
Syslog Message Id -Â 0x00a0400a
Sync Plan Completed Successfully with Skipped Tasks
Some sync tasks finished successfully and some were skipped (but none failed)
Syslog Message Id -Â 0x00a0401a
Sync Plan Failed
At least one task failed
Syslog Message Id -Â 0x00a0402a
Task Events
Sync Task Completed Successfully
A sync task finished execution successfully
Syslog Message ID -Â 0x00a0200a
Sync Task Failed
A sync task failed for any reason
Syslog Message ID -Â 0x00a0201a
Sync Task - Found Unsaved Changes in Source DomainÂ
A warning message about unsaved changes found in the source domain
Syslog Message ID -Â 0x00a0202a
Sync Task Skipped
When a sync task did not execute - for example, when the device was not available
Syslog Message ID -Â 0x00a0203a
Sync Task Long Running
If a task's status did not change for more than 60 minutes (see maintenance configurable parameters for more information), DPOD will issue the "Long Running" event and will consider the task as finished
Syslog Message ID -Â 0x00a0204a
Sync Task was not Executed
For tasks that passed all validations but did not execute. e.g. when the maintenance window timeframe ended before the task was executed
Syslog Message ID -Â 0x00a0205a