Queue Latency

Queue Latency Alert

Alert ID: queue_latency Category: Process Scheduler Default threshold: 15 minutes

What This Alert Detects

This page documents the queue latency alert, which monitors the delay between a process’s scheduled run time and its actual start time. It queries the PSPRCSRQST table for processes that have started running or completed within the lookback window and calculates the delay as BEGINDTTM - RUNDTTM.

Severity Logic

For example, with the default threshold of 15 minutes:

• A process scheduled for 10:00 that started running at 10:20 → Warning

What Gets Checked

The alert queries the Process Scheduler request table (PSPRCSRQST) for processes whose BEGINDTTM (begin datetime) is in the past lookback window (default 24 hours). For each process, it calculates the difference between BEGINDTTM and RUNDTTM (scheduled run datetime).

Processes that have not started running yet (empty BEGINDTTM value) are skipped. Active queuing checks are handled by the backlogged_processes alert.

Alert Details

Each alert item includes:

• Process name (PRCSNAME)
• Process instance number
• Start delay duration (in minutes)
• Current run status (Initiated, Processing, Success, Error, etc.)
• The operator who submitted the request
• A link to the Process Monitor detail page for that instance

Configuration

alerts:
  checks:
    queue_latency:
      enabled: true
      thresholdMinutes: 15         # Minutes delay before flagging as Warning
      lookbackHours: 24            # Hours to look back for completed/running processes
      excludeProcesses:            # Process names to skip
        - LOW_PRIORITY_AE

How to Respond

1. Click the alert link to go to the Process Monitor entry for the flagged process.
2. Review the process server definition to identify if it is running and accepting work.
3. Check the max concurrent limits configured on the Process Scheduler server or category definitions.
4. Verify if other higher-priority processes occupied all available channels.
5. If the delay is caused by category stalls, adjust the process class concurrency settings.

Tuning the Threshold

Environments with heavy batch schedules may experience normal queue delays during peak hours. Set thresholdMinutes high enough to prevent alerts on minor delays but low enough to flag scheduler capacity bottlenecks or server category stalls.