IB Sync Operation Exceptions
Categories:
- Target Database: —
- Context Type: —
- Alert Severity: —
- Triggered Time: —
- Firing Context:
—
IB Sync Operation Exceptions Alert
Alert ID: ib_sync_exceptions
Category: Integration Broker
What This Alert Detects
This alert detects synchronous IB service operations that have logged errors in the sync transaction log (PSIBLOGHDR) within the configured lookback window. Results are aggregated by operation name to avoid noise from high-volume sync operations that may have individual errors but function normally overall.
Unlike async IB errors (which create persistent queue entries), sync operation errors are logged transiently in PSIBLOGHDR. Without active monitoring, these errors are often missed until a consuming system reports a problem.
Severity Logic
All findings are reported at Critical severity. Sync errors are always surfaced immediately because they affect real-time integrations.
What Gets Checked
The alert queries PSIBLOGHDR for records with error status within the lookback window, aggregated by IB operation name. Only operations with at least one error are reported. Operations in the exclude list are skipped.
Alert Details
Each alert item includes:
- Service operation name (with link to Service Operation detail page)
- Number of errors in the lookback window
- Lookback window in hours
Configuration
alerts:
checks:
ib_sync_exceptions:
enabled: true
lookbackHours: 24 # How far back to check for sync errors
excludeOperations: [] # Operation names to ignore
| Setting | Default | Description |
|---|---|---|
lookbackHours | 24 | Hours to look back for sync operation errors |
excludeOperations | [] | List of operation names to exclude from this check |
How to Respond
- Click the alert link to open the Service Operation detail page
- Review the operation’s handler configuration and routing
- Check PSIBLOGHDR directly for the specific error messages (psLens links to the operation, not individual log entries)
- Verify that the operation’s service handler is still functional and the underlying code has not changed
- Contact the calling system to understand whether they are seeing failures on their end
- Use the Sync Operations Without Logging report to identify any sync operations that are not logging and may have undetected errors
Prerequisites
The PSIBLOGHDR table must be whitelisted in the PeopleSoft SWS framework on each target environment. Sync logging must be enabled on the relevant routings. If logging is disabled, errors will not appear in PSIBLOGHDR. See the Sync Operations Without Logging report to find operations where logging may be disabled.
Tables Queried
| Table | Description |
|---|---|
| PSIBLOGHDR | IB sync transaction log headers |