IB Dispatcher Down

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

IB Dispatcher Down Alert

Alert ID: ib_dispatcher_down Category: Integration Broker Default threshold: 10 minutes

What This Alert Detects

This alert monitors Integration Broker dispatcher processes (such as the publication dispatcher, subscription dispatcher, or handler dispatchers) on active domains and triggers when any dispatcher is inactive or has stopped reporting health updates.

When a dispatcher process is down, messages assigned to that dispatcher fail to process and queue up indefinitely, leading to a backlog.

Severity Logic

ConditionSeverity
Dispatcher status is not active, or no health update within thresholdMinutesWarning
Dispatcher has not updated health status for more than thresholdMinutes × 2Critical

For example, with the default threshold of 10 minutes:

  • No health update for 11 minutes → Warning
  • No health update for 20+ minutes → Critical

What Gets Checked

The alert queries PSAPMSGDSPSTAT for dispatcher process statuses. For each dispatcher associated with an Active domain (from PSAPMSGDOMSTAT), it verifies:

  1. The status string is "ACT" (Active).
  2. The health timestamp (DspHealthDttm) has been updated within the threshold window.

Note: Dispatchers on inactive domains are ignored by this check (they are covered by the IB No Active Domain check).

Alert Details

Each alert item includes:

  • Dispatcher process name
  • Physical machine/host name
  • App server path
  • The last updated health timestamp
  • Reason for the down status (e.g. status not active, or elapsed minutes since last update)
  • A link to the Integration Broker Monitor page

Configuration

alerts:
  checks:
    ib_dispatcher_down:
      enabled: true
      thresholdMinutes: 10
SettingDefaultDescription
thresholdMinutes10Minutes a dispatcher can go without updating health before raising a Warning. Critical fires at 2× this threshold.

How to Respond

  1. Go to the Integration Broker Monitor on the psLens dashboard to identify which specific dispatcher on which host is failing.
  2. Log into the affected PeopleSoft application server and check the status of the dispatcher processes via PSAdmin.
  3. Review the application server and Pub/Sub subdirectories log files (such as APPSRV.log, TUXLOG, or stderr / stdout logs) for crashes, Tuxedo errors, or database lockups.
  4. Restart the Pub/Sub processes on the application server if the dispatcher has locked up or crashed.