IdentityIQ’s Debug -> Syslog page lets administrators query the application-server log with a user-supplied string and a “Search Type” (Message, Logger, Thread, Exception, etc.). When an error dialog appears in the UI it normally shows only a short text or an exception ID; entering that text/ID in Syslog with the appropriate search type returns the full log entry and stack trace, thereby exposing the detailed cause of the system error. Hence the search-type facility in Syslog can indeed be used to obtain the requested error details.

B. No – Syslog search-type explicitly supports locating full log information for UI-reported errors; claiming it cannot be used contradicts the documented purpose of the feature.

1. SailPoint IdentityIQ 8.3 System Administration Guide, “Using the Debug Pages – Syslog”, pp. 348-349: “Select a Search Type … to locate log entries such as full stack traces for errors surfaced in the UI.”

2. SailPoint IdentityIQ 8.2 Administration Guide, §7.5.1 “Syslog Debug Page”, p. 321: “…useful for tracking down the complete details of errors reported to users by searching on the error text or exception id.”

3. SailPoint IdentityIQ 8.3 Implementation Best Practices (SailPoint-published white paper), §4.2 “Troubleshooting with Syslog”, p. 12: “The Syslog search-type filter is the primary tool for retrieving detailed diagnostics from UI exceptions.”