IB Operation Errors

Tailored Operational Context
  • Target Database:
  • Context Type:
  • Alert Severity:
  • Triggered Time:
  • Firing Context:

IB Operation Errors Alert

Alert ID: ib_operation_errors Category: Integration Broker Default lookback: 24 hours

What This Alert Detects

This alert finds asynchronous Integration Broker operation instances that are in Error or Timeout status within a configurable lookback window. These are messages that attempted to process but did not complete successfully.

An IB operation instance represents a single execution of a Service Operation through the Integration Broker. When an instance errors, the message did not reach its destination. The original publish/subscribe data is preserved in the IB tables and can usually be resubmitted from the Service Operations Monitor.

Severity Logic

StatusSeverity
ErrorCritical
TimeoutWarning

Error status means the processing actively failed. Timeout means it ran out of time, which may be a transient issue but still warrants investigation.

Alert Details

Each alert item includes:

  • Operation instance ID
  • Service operation name
  • Status (Error or Timeout)
  • The originating node
  • When the instance was created
  • A link to the IB Monitor detail page

Configuration

alerts:
  checks:
    ib_operation_errors:
      enabled: true
      lookbackHours: 24          # How far back to look for errors
      excludeOperations:         # Operation names to skip
        - SOME_NOISY_OPERATION
SettingDefaultDescription
lookbackHours24Number of hours back to search for error/timeout instances
excludeOperations[]List of IB operation names to exclude from this check

How to Respond

  1. Click the alert link to go to the IB Monitor entry for the failed operation
  2. Review the error details. The IB Monitor shows the error message or exception
  3. Check whether this is a configuration issue (wrong endpoint, auth failure) or a data issue
  4. If the message needs to be reprocessed, you can do so from PeopleSoft’s Service Operations Monitor
  5. If this is a recurring operation, investigate the root cause before errors pile up

Relationship to Other IB Alerts

This alert finds operations that have already ended in error. For operations that are stuck in progress, see IB Operations Stalled.

For similar alerts on publication and subscription contracts, see: