Search Indexing Errors

This alert triggers when a search definition’s latest index build reported errors in PTSF_INDEX_STAT or PTSF_ES_DT_ERR, or rows failed Real-Time Indexing.
Categories:
New to psLens? This page documents one specific alert. To see how it appears on the dashboard, what operators investigate, and how teams tune it, start with a live walkthrough.
Book a Demo Browse Alerts
Tailored Operational Context
  • Target Database: —
  • Context Type: —
  • Alert Severity: —
  • Triggered Time: —
  • Firing Context: —
  • Contextual SQL: 
    —

Search Indexing Errors Alert

Alert ID: ptsf_indexing_errors Category: Search Framework Default lookback: 24 hours Runs: every 15 minutes

What This Alert Detects

This alert triggers when PeopleSoft has recorded indexing errors for a search definition. It reads three sources:

SourceWhat it holdsScope
PTSF_INDEX_STATThe error count an index build reportedLatest build only
PTSF_ES_DT_ERRRequests the search engine rejected during a buildLatest build only
PTSF_INDDATA_ERRows that failed Real-Time IndexingWithin the lookback

“Latest build” is the build recorded for the definition in PTSF_SCHED_STAT. A clean rebuild clears the first two sources, so the alert resolves on its own.

Severity Logic

ConditionSeverity
Any source has errors for a search definitionWarning

There is one alert item per search definition, listing each source that has errors.

Alert Details

Each alert item includes:

  • The search definition
  • The error count the latest build reported
  • The number of requests the search engine rejected
  • The number of rows that failed Real-Time Indexing in the lookback window
  • A link to the Search Framework Monitor

Configuration

alerts:
  checks:
    ptsf_indexing_errors:
      enabled: true
      lookbackHours: 24    # Window for failed Real-Time Indexing rows
SettingDefaultDescription
lookbackHours24How far back to count rows that failed Real-Time Indexing

How to Respond

  1. Open the Search Framework Monitor and switch on the Indexing Errors panel. It shows the first part of the search engine’s response for each rejected request, and the record and keys of each failed row.
  2. Follow the process instance link to Process Monitor for the build’s message log.
  3. Fix the cause the search engine reports, then rebuild the index for the definition.

What This Alert Cannot See

A build that ends in Success with no recorded errors is not flagged, even if it indexed nothing. PeopleSoft can leave its document counts at zero after a successful build, so a zero count is not treated as an error. Check the document count in the search engine.

Required Tables

Each source is read only when its table is whitelisted. PTSF_INDEX_STAT and PTSF_ES_DT_ERR also need PTSF_SCHED_STAT. With no source available the alert is inactive.