Alerts

Alerts

Alert checks run on a 5-minute timer against every connected database. Findings appear on the dashboard with severity, and clear automatically when the underlying condition resolves. There is no acknowledge or dismiss.

How the Alert System Works

1. psLens runs a set of alert checks on a timer (default: every 5 minutes)
2. Each check queries one or more connected databases
3. If a check finds something worth noting, it creates alert items with a severity level
4. Alert results appear on the dashboard immediately
5. When the underlying issue resolves, the alert clears automatically on the next check cycle

Alerts always reflect the current state of the system.

Alert Severity Levels

Alert Data Retention

Alert results are stored for 15 minutes. This means the dashboard shows findings from the most recent check cycle. Once an issue is resolved and the next check runs cleanly, the alert data expires.

Configuring Alerts

Alerts are configured in config.yaml. You can:

• Enable or disable the entire alert system (alerts.enabled)
• Set how often checks run (alerts.intervalMinutes)
• Enable or disable individual checks
• Set thresholds for stalled/long-running checks
• Set lookback windows for error checks
• Exclude specific process names or IB operation names from checks

See Configuration for the full configuration reference.

Alert Categories

Browse alerts by category:

• Process Scheduler: Long-running processes, errors, backlogged jobs, locked operators, critical process monitoring
• Integration Broker: Operation errors, contract errors, stalled messages, volume anomalies, sync exceptions
• Web Server / WebLib: Alerts when the PeopleSoft Web Server or WebLib endpoints fail to respond
• Security: Failed login detection and authentication monitoring
• Generic SWS Alerts: Define custom, queryable alert rules using PsoftQL against any whitelisted tables

See Alerts in Action

The catalog tells you what psLens checks. A live walkthrough shows what matters operationally: how alerts appear, how they clear, and how quickly your team can move from a card on the dashboard to the underlying problem.