This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

System Overview

The health overview of all connected databases and active alerts.

System Overview

The home screen of psLens (System Overview) gives you a quick health overview of all your connected PeopleSoft databases, with a focus on anything that currently needs attention.

psLens Dashboard showing active alerts and database status

The psLens dashboard showing database connection status and active alerts

What You See on the Dashboard

Alert Summary

The top section of the dashboard shows active alerts grouped by database. Each alert card tells you:

  • What type of issue was found (for example, long-running processes or IB errors)
  • How many items were found in this check
  • When the check last ran
  • A link to the relevant monitor page for more detail

Alerts are color-coded by severity:

ColorSeverityMeaning
RedCriticalImmediate attention recommended
YellowWarningShould be investigated
BlueInfoLow priority, worth noting

If there are no active alerts, the dashboard shows an “all clear” state.

Database Cards and Health Scores

For each active database connection, the dashboard renders a database card with four operational monitoring categories. Each category displays a visual 0–100 circular health ring, a health tier label, and key operational metrics:

Status TierScore RangeColorIconMeaning
Healthy90 – 100GreenOperations normal; no critical issues or high error rates.
Degraded60 – 89YellowModerate errors, stalled queues, or active warnings detected.
Critical0 – 59RedSevere issues, active critical alerts, or blocked queues.

Each score begins at 100 points and applies bounded deductions based on real-time database queries and active alert states:

1. Process Scheduler Health Score

Evaluates Process Scheduler queue health, blocked jobs, and recent execution failures:

  • Active Critical Process Alerts: -25 points per active alert (capped at 50 points total).
  • Active Warning Process Alerts: -10 points per active alert (capped at 20 points total).
  • Currently Blocked Processes: -15 points per process currently in Blocked status (RunStatus 18, capped at 40 points total).
  • Process Errors Today: -2 points per process ending in Error (3), Not Successful (10), or Unable to Post (12) since midnight (capped at 20 points total).
2. Integration Broker Health Score

Evaluates messaging throughput, stalled contracts, and synchronous/asynchronous transaction failures:

  • Active Critical IB Alerts: -25 points per active alert (capped at 50 points total).
  • Active Warning IB Alerts: -10 points per active alert (capped at 20 points total).
  • IB Errors & Timeouts Today: -2 points per failed or timed-out message since midnight (capped at 30 points total).
  • IB Working / Stalled Items Today: -2 points per message in New or Working status since midnight (capped at 15 points total).
3. User Logins (24h) Health Score

Evaluates authentication activity and failed sign-on attempts over the rolling 24-hour window:

  • Active Failed Logins Alert: -30 points if the failed_logins critical alert is currently firing.
  • Unique Users with Failed Logins (last 24h): -1 point per unique operator ID with failed login attempts recorded in PSPTLOGINAUDIT (capped at 30 points total).
4. Active Alerts Health Score

Evaluates the overall system alert posture across all enabled alert checkers:

  • Active Critical Alerts: -25 points per active critical alert across any checker (capped at 60 points total).
  • Active Warning Alerts: -10 points per active warning alert across any checker (capped at 30 points total).
  • Active Info Alerts: -2 points per active informational alert (capped at 10 points total).

Note on Muted Alerts: Alerts that are currently muted (suppressed) in psLens are excluded from health score deductions so maintenance windows or known issues do not artificially lower the score.

Database Connection Status

The dashboard also shows whether psLens can connect to each configured database. A database that is unreachable will still show in the list but will be marked as disconnected. Alerts for a disconnected database won’t run until the connection is restored.

How Alerts and Health Scores Are Refreshed

The dashboard uses a live connection to the psLens server. Alert results are updated automatically on the page as new check results arrive — you do not need to manually refresh.

Alert checks run on a background schedule (default: every 5 minutes). The timestamp on each alert card shows when that specific check last completed.

Click a database’s name or its DB Home button to open DB Home, the page for that one database.

Each alert item on the dashboard has a direct link to the relevant page in psLens. For example:

  • A long-running process alert links to the Process Monitor entry for that process instance
  • An IB operation error alert links to the IB Monitor entry for that operation
  • A process error alert links to the Process Monitor entry for that process

Dismissing Alerts

Alert results are automatically cleared when the underlying issue resolves. For example, if a long-running process finishes, its alert disappears from the dashboard on the next check cycle. There is no manual dismiss — the alerts always reflect the current state of the system.

Alert Configuration

Alerts are configured in config.yaml. You can enable or disable individual alert types, adjust thresholds, and exclude specific processes or operations. See Configuration and Alerts for details.

1 - DB Home

One database’s alerts, Process Scheduler, Integration Broker, sign-ins, projects, and reports on one page.

DB Home shows the current state of one PeopleSoft database: its connection, alerts, Process Scheduler and Integration Broker status, sign-ins, recently changed projects, and report activity.

Opening DB Home

  • On the System Overview, click a database’s name or its DB Home button.
  • In the sidebar, click DB Home. It opens the database you used last.
  • Press Ctrl+K and type “DB Home”.

The database switcher next to the name moves between databases. The page address (for example /dbhome?db=HR92DEV) can be bookmarked or shared.

The header shows the connection status, PeopleTools release, database type, when psLens last checked the connection, and uptime over the last 30 days. PIA Login opens the database’s sign-in page. A warning appears when tables psLens reads are not whitelisted, with a link to the list and the SQL to add them.

Health

The same four scores as the database’s System Overview card: Process Scheduler, Integration Broker, Logins (24h), and Active Alerts. The System Overview page explains how each score is calculated.

Active Alerts

Alerts currently firing for this database, critical first, each with its first three items. Muted alerts are listed last. Muting and rechecking happen on the Active Alerts page.

Process Scheduler

  • Servers: every server in PSSERVERSTAT with its status and last heartbeat. A running server whose heartbeat is more than 10 minutes old is marked Stale, the same rule the Process Scheduler Down alert uses.
  • Errors in the last 24 hours: the latest 10 requests that ended in Error, Not Successful, or Unable to Post, with a link to all of them in the Process Monitor.
  • Recent requests: the 15 newest process requests of any status.

Integration Broker

  • Domains: messaging domains in PSAPMSGDOMSTAT and how many are active.
  • Dispatchers: how many report ACT status.
  • Nodes down: nodes listed in PSNODESDOWN, with the number of operations held for each.
  • Sync errors, last 24 hours: synchronous service operations with errors in PSIBLOGHDR, most errors first.

Sign-in Activity

When PSACCESSLOG is whitelisted, the card lists the 15 latest PIA sign-ins with the user, client address, sign-in time, and sign-out time. The sign-out reason comes from PeopleSoft: Signed out, Browser expired, Abandoned, Re-login, or Other. A sign-in from the last 12 hours with no sign-out is marked Open; older ones show “No sign-out recorded”. Batch, API, and application server sign-ons are left out.

Above the list, a count shows sign-ins from the last hour with no sign-out recorded. It includes sessions that ended without signing out, such as a closed browser.

PSACCESSLOG has no index on sign-in time, so psLens reads the whole table for this card. On a test database with 1.2 million rows each query took about half a second. To turn the card on, whitelist the table:

INSERT INTO PS_CHG_PSLENS_WL (RECNAME) VALUES ('PSACCESSLOG');

Without it, the card shows each user’s last sign-on attempt from PSPTLOGINAUDIT. Either way, it lists users with failed logins in the last 24 hours.

Recent Project Activity

PeopleSoft does not keep a log of project copies. This card lists projects whose definition changed in the last 7 days (PSPROJECTDEFN.LASTUPDDTTM), who changed them, and the compare or copy target database saved on the project, when there is one.

Security Checks

The latest saved run of the Nodes with No Password and PeopleTools Access Audit reports for this database: the number of findings, how many were added or removed since the run before, and when it ran. If a report has never run against this database, the card links to run it. DB Home never runs these reports itself.

Scheduled and Recent Reports

  • Scheduled Reports: enabled report schedules that include this database, with when each runs next. Times use the psLens server’s clock.
  • Recent Reports: the 8 newest report runs for this database, with status and findings count.

Recently Viewed

Objects you opened in this database, newest first.

Loading, Refresh, and Offline Databases

The header, alerts, reports, and recently viewed items come from psLens’s own records and appear immediately. The PeopleSoft sections load after the page appears, each card on its own, so a slow or failing query affects only its card. Results are reused for 2 minutes; Refresh fetches everything again.

When the database is offline or in scheduled downtime, the PeopleSoft cards say so and psLens sends no queries. Alerts, reports, and recently viewed items still show.