How to use the Request Impact Map to see where a fatal-style error was felt
When context is available, Titanium correlates a small request snapshot captured during the failing request with the grouped error found later in the log. The snapshot is deliberately reduced before storage.
Use impact evidence step by step
- Open the Impact map column for the grouped error you are investigating.
- Check whether the strongest evidence is Frontend, REST API, Login, AJAX, Cron, Admin or CLI.
- Compare the counts across contexts instead of focusing only on the most recent request.
- If a normalized local route shape is shown, use it to identify the affected page or endpoint family without expecting the original query string.
- Compare the request context with the error source and behavior pattern.
- If no request context exists, use the behavior and raw log evidence instead of assuming the plugin failed to monitor the error.
