IB Operations Stalled

IB Operations Stalled Alert

Alert ID: ib_operation_stalled Category: Integration Broker Default threshold: 30 minutes

What This Alert Detects

This alert finds asynchronous Integration Broker operation instances that are stuck in New or Working status and have been in that state longer than the configured threshold. These are messages that started processing (or are waiting to be processed) but have not completed in a reasonable amount of time.

Cross-reference with IB Dispatcher Down first. A stalled queue plus a down dispatcher is almost always the dispatcher.

Severity Logic

For example, with the default threshold of 30 minutes:

• An operation stuck for 35 minutes → Warning
• An operation stuck for 65 minutes or more → Critical

Alert Details

Each alert item includes:

• Operation instance ID
• Service operation name
• Current status (New or Working)
• How long it has been stuck (in minutes)
• The originating node
• A link to the IB Monitor detail page

Configuration

alerts:
  checks:
    ib_operation_stalled:
      enabled: true
      thresholdMinutes: 30       # Minutes before flagging as Warning
      excludeOperations:         # Operation names to skip
        - BULK_SYNC_OPERATION

How to Respond

1. Click the alert link to go to the IB Monitor entry for the stalled operation
2. Check whether the IB dispatcher/handlers are running on the PeopleSoft application server
3. Look for signs of a larger IB backlog (many operations in New status)
4. Check the gateway and connector configuration if the operation can’t reach a node
5. If the operation is safe to reprocess, you can cancel and resubmit from PeopleSoft’s Service Operations Monitor

Relationship to Other IB Alerts

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

For similar alerts on publication and subscription contracts, see:

• IB Publication Contracts Stalled
• IB Subscription Contracts Stalled