IB Nodes Down
Categories:
- Target Database: —
- Context Type: —
- Alert Severity: —
- Triggered Time: —
- Firing Context:
—
IB Nodes Down Alert
Alert ID: ib_nodes_down
Category: Integration Broker
Default threshold: Immediate
What This Alert Detects
This alert triggers when there are entries in the PeopleSoft table PSNODESDOWN. An entry in this table indicates that a message node is blocked or offline.
When the Integration Broker attempts to publish a message to an external or remote node and the connection fails, the system registers the node as “down” in PSNODESDOWN. While the node is down, all subsequent publication contracts to that node are automatically paused/blocked and remain queued in the database until the node status is resolved.
Severity Logic
| Condition | Severity |
|---|---|
Message node entry exists in PSNODESDOWN | Critical |
What Gets Checked
The alert queries PSNODESDOWN for any active rows. For each row found, it groups the results by message node and counts the number of blocked transactions.
Alert Details
Each alert item includes:
- The name of the offline message node
- The count of blocked transactions queueing for the node
- A link to the Node detail page in the browser showing connection diagnostics
Configuration
alerts:
checks:
ib_nodes_down:
enabled: true
| Setting | Default | Description |
|---|---|---|
enabled | true | Whether this check is active. |
How to Respond
- Click the node link in the alert to inspect the node configuration and test connectivity.
- Check if the external target service (e.g. an external API gateway, third-party system, or another PeopleSoft application node) is offline or undergoing maintenance.
- Verify network routing and gateway connector configurations.
- Once the external endpoint is confirmed to be healthy, delete the down-node status entry in PeopleSoft (typically via the Service Operations Monitor > Administration > Nodes Down page) and resubmit or force retry the stalled publication contracts.