Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Lack of dedicated PEGA Alert for slow FTS search queries

SA-85416

Summary



Unable to identify poor performing FTS Search queries due to the lack of Pega alerts.


Error Messages



RequestorLockExceptions
PEGA0086 alerts



Steps to Reproduce

  1. Index the work items.
  2. Launch a slow query (for example, 1 && 2 && 3 && 4 && 4 && 5 && 6 && 7 && 8 && 8 && 9 && 0 && a && aa && ab && ac && ad && ae && af).
  3. Launch a fast query (for example, pyDefault). The Request #3 is served after Request #2. The slow requests or timeouts are not reported by an Alert.

Root Cause



A defect or configuration issue in the operating environment
PEGA0054 already exists for this issue; however the alert is not enabled by default.



Resolution



Perform the following local-change:

Define a threshold which matches the SLA for FTS searches.

Follow the instructions in the article to define the threshold: https://community.pega.com/knowledgebase/articles/pega0054-alert-query-exceeded-operation-time-threshold
Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us