Title: Titanium Error Intelligence – PHP Error Monitor & Diagnostics Author: Admin Plugins Published: সেপ্টেম্বর 1, 2026 Last modified: সেপ্টেম্বর 1, 2026 --- Search plugins ![](https://ps.w.org/titanium-error-intelligence/assets/banner-772x250.png?rev=3676227) ![](https://ps.w.org/titanium-error-intelligence/assets/icon-256x256.png?rev=3676220) # Titanium Error Intelligence – PHP Error Monitor & Diagnostics By [Admin Plugins](https://profiles.wordpress.org/aplugins/) [Download](https://downloads.wordpress.org/plugin/titanium-error-intelligence.1.0.0.zip) * [Details](https://bn-in.wordpress.org/plugins/titanium-error-intelligence/#description) * [Reviews](https://bn-in.wordpress.org/plugins/titanium-error-intelligence/#reviews) * [Installation](https://bn-in.wordpress.org/plugins/titanium-error-intelligence/#installation) * [Development](https://bn-in.wordpress.org/plugins/titanium-error-intelligence/#developers) [Support](https://wordpress.org/support/plugin/titanium-error-intelligence/) ## Description Titanium Error Intelligence is a local WordPress PHP error diagnostics plugin focused on how errors behave, not only on displaying raw log lines. It fingerprints supported critical errors, groups repeated occurrences and analyses changes in their timing and frequency. The diagnostics layer can identify sudden spikes, recurring patterns, short bursts, persistent errors and errors that have gone quiet. It also tracks the plugin, must-use plugin, theme or WordPress version associated with a grouped error when that information is available locally. For fatal-style failures that occur after WordPress has initialized, Titanium Error Intelligence can record a small privacy-reduced request-context snapshot and correlate it with the later log scan. This can show whether a grouped error affected frontend, REST API, AJAX, cron, login, wp-admin or WP-CLI execution without storing query strings, POST bodies, IP addresses, usernames or user IDs. The plugin also includes authenticated debug-log tools and a monitoring self-test, but the primary purpose is grouped error behaviour and impact diagnostics. #### What Makes It Different * Treats the debug log as an input to grouped diagnostics rather than as the end product. * Compares retained occurrence timing to identify spikes, bursts, persistence and recurring intervals. * Tracks source-version observations so a grouped error can be compared across plugin, theme or Core version changes. * Correlates privacy-reduced request context with supported fatal-style errors to show which execution areas are affected. * Runs locally without sending the retained error history or request-impact data to a bundled external diagnostics service. #### Error Behavior Intelligence * Groups supported fatal, parse, recoverable fatal, uncaught and WordPress database errors by a normalized fingerprint. * Detects sudden error spikes relative to the retained recent rate. * Detects recurring timing patterns when recent occurrences have a sufficiently stable interval. * Detects short bursts and errors that remain active across multiple days. * Marks recently introduced grouped errors and errors that have gone quiet. * Keeps recent occurrence timestamps bounded for lightweight behaviour analysis. * Retains grouped error intelligence for up to seven days. * Limits stored history on unusually noisy sites. #### Version-aware Error Lifecycle * Records the locally installed source version when an error is observed. * Supports plugins, must-use plugins, themes and WordPress Core. * Shows the first observed source version and the most recent error version. * Shows when an error continues after a source version changes. * Shows when the installed source version has changed and no recurrence has yet been recorded on that version. * Performs no remote version lookup. #### Request Impact Map * Correlates available fatal-style request context with a grouped error. * Separates frontend, REST API, AJAX, cron, login, wp-admin and WP-CLI contexts. * Stores a normalized route shape rather than a raw query-bearing URL. * Removes query strings before storage. * Replaces numeric IDs, email addresses, UUIDs, long hashes, token-like values and sensitive route parameters with placeholders where detected. * Does not store IP addresses, request bodies, usernames or user IDs. * Fatal-request correlation keeps only a WordPress/content-relative source file location where possible, otherwise only the filename; full server paths are not retained in request context. * Can show the most frequently affected normalized local route shapes for a grouped error. * Request-impact metadata follows the same seven-day retention window as grouped error history. #### Monitoring Self-Test The built-in self-test checks the local monitoring pipeline without deliberately generating a PHP error. It checks: * WP_DEBUG status. * WP_DEBUG_LOG status. * Configured log-directory writability. * Whether a harmless marker reaches the configured PHP error log. * Whether Titanium Error Intelligence can read that marker back. * Whether the five-minute background monitor is scheduled. * Whether local intelligence storage is writable. * Whether the local Site Watch health API is available. #### Log and Debug Tools * Detects a custom WP_DEBUG_LOG path. * Uses wp-content/debug.log when no custom path is configured. * Supports absolute custom log paths outside the public web root. * Can create a plugin-specific private log directory outside the public web root and move the active log there. * Enables or disables WordPress debug logging and on-screen error display. * Lists supported log and text files only in the configured directory; subdirectories are not scanned. * Reads a bounded tail of large logs for the browser viewer. * Searches and filters the currently loaded lines in the browser. * Auto-refresh can wait for a configured log file that does not exist yet and load it when WordPress creates it. * Renames, empties, deletes and downloads allowed log files through authenticated administrator actions. * Includes a bounded browser editor for smaller files. * Keeps the background monitor cursor aligned after primary-log edits, clears, renames and deletes. * Optionally removes plugin data on uninstall. * Never recursively deletes unrelated files from a private log directory. #### Titanium Site Watch Integration Titanium Error Intelligence exposes a compact local health summary for optional Titanium integrations. The summary contains grouped error metadata and behaviour counts such as spikes, periodic errors, bursts, persistence and frontend/API impact. The integration summary does not expose raw stack traces, SQL queries or absolute server paths. The public integration function is: ``` titanium_error_intelligence_get_health_summary() ``` #### Local by Default Titanium Error Intelligence does not send error history or request-impact data to a bundled external service and does not make remote version lookups. Its diagnostics data is stored in the WordPress installation. ### External Services Titanium Error Intelligence does not connect to or send data to any external service. Its More Plugins page contains normal links to related plugins on WordPress.org; those links are opened only when an administrator chooses to visit them. ### Privacy Titanium Error Intelligence is local by default and does not use a bundled external diagnostics service. The plugin stores small preferences, a monitoring cursor, grouped critical-error history for up to seven days, bounded recent occurrence timestamps, component-version observations and temporary request context used for local correlation. Request context deliberately excludes IP addresses, URL query strings, POST bodies, usernames and user IDs. Stored route shapes are normalized to reduce the chance of retaining identifiers in URL path segments. Fatal-request correlation stores only a WordPress/content-relative source file location where possible, otherwise a filename, rather than a full server path. The Titanium Suite dark-mode preference is stored only in the current browser’s local storage. ## Screenshots [⌊Error Behavior Intelligence groups recent critical errors by fingerprint and highlights occurrences, request impact, source lifecycle, recurring patterns, spikes, periodic activity and bursts.⌉⌊Error Behavior Intelligence groups recent critical errors by fingerprint and highlights occurrences, request impact, source lifecycle, recurring patterns, spikes, periodic activity and bursts.⌉[ Error Behavior Intelligence groups recent critical errors by fingerprint and highlights occurrences, request impact, source lifecycle, recurring patterns, spikes, periodic activity and bursts. [⌊Debug Settings in light mode, including WordPress debug logging, protected log storage, on-screen error display and configurable live admin error alerts.⌉⌊Debug Settings in light mode, including WordPress debug logging, protected log storage, on-screen error display and configurable live admin error alerts.⌉[ Debug Settings in light mode, including WordPress debug logging, protected log storage, on-screen error display and configurable live admin error alerts. [⌊Debug Settings in dark mode with the same logging, storage and live admin alert controls.⌉⌊Debug Settings in dark mode with the same logging, storage and live admin alert controls.⌉[ Debug Settings in dark mode with the same logging, storage and live admin alert controls. [⌊Pipeline Integrity self-test, detected debug log location and log directory overview, showing whether the local monitoring pipeline and required components are operating correctly.⌉⌊Pipeline Integrity self-test, detected debug log location and log directory overview, showing whether the local monitoring pipeline and required components are operating correctly.⌉[ Pipeline Integrity self-test, detected debug log location and log directory overview, showing whether the local monitoring pipeline and required components are operating correctly. [⌊Built-in Log Viewer with line filtering, search, error-type filters, auto-refresh, highlighted log entries and file management controls.⌉⌊Built-in Log Viewer with line filtering, search, error-type filters, auto-refresh, highlighted log entries and file management controls.⌉[ Built-in Log Viewer with line filtering, search, error-type filters, auto-refresh, highlighted log entries and file management controls. ## Installation 1. Upload the `titanium-error-intelligence` folder to `/wp-content/plugins/`, or install the ZIP through Plugins > Add Plugin. 2. Activate Titanium Error Intelligence. 3. Open Titanium Error Intelligence in wp-admin. 4. Enable WordPress debug logging if it is not already enabled. 5. Run the Monitoring Self-Test to verify the local pipeline. On WordPress Multisite, network activation is required because WP_DEBUG_LOG is installation- wide. One scanner runs from the main site to avoid duplicate processing. ## FAQ ### Is this only a debug.log viewer? No. The viewer is one tool in the plugin. The main diagnostics layer fingerprints and groups supported critical errors, analyses their frequency and timing, tracks source-version changes and correlates available request-impact context. ### How does spike detection work? The plugin keeps a bounded recent occurrence history. It compares the recent 15- minute activity with the retained preceding rate and requires multiple recent occurrences before an error can be labelled as a spike. A single isolated error is not considered a spike. ### What is a periodic error? When enough retained occurrences have a sufficiently stable interval, the plugin labels the grouped error as periodic and reports the approximate repeat interval. It reports the timing pattern only; it does not claim that a particular cron job caused the error unless that information is independently known. ### What does the Request Impact Map store? When context is available, it can store the execution context, HTTP method, privacy- reduced route shape, logged-in/guest classification, timestamp and bounded diagnostic metadata used for local correlation. It does not store IP addresses, URL query strings, POST bodies, usernames or user IDs. ### Why do some errors have no request context? Request context can be attached only when the plugin is already running in the request and PHP reaches the registered shutdown handler. Very early failures, failures that prevent local storage, and errors found only in an existing log may not have matching context. ### Does the plugin send error data to an external service? No. Error intelligence, history, request context and self-test data stay in the WordPress installation. The Site Watch integration is a local PHP function that another installed Titanium component can call. ### Does it work with a private WP_DEBUG_LOG path? Yes, provided PHP has permission to read the configured directory and file. File- changing actions also require write permission. ### Does the plugin modify wp-config.php? Only when an administrator uses the debug configuration switches. The plugin changes only WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY. Existing custom private WP_DEBUG_LOG paths are preserved. ### Does the self-test generate a PHP error? No. It writes a uniquely identified harmless marker through PHP’s normal error-log channel and verifies that the marker can be read from the configured log. The marker is not treated as a critical error by the intelligence scanner. ### How does WordPress Multisite work? Titanium Error Intelligence must be network activated. Intelligence data and settings are network-scoped, request context can be captured across sites, and one five-minute scanner runs from the main site. The plugin admin UI is available from the main site’s wp-admin. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Titanium Error Intelligence – PHP Error Monitor & Diagnostics” is open source software. The following people have contributed to this plugin. Contributors * [ Admin Plugins ](https://profiles.wordpress.org/aplugins/) [Translate “Titanium Error Intelligence – PHP Error Monitor & Diagnostics” into your language.](https://translate.wordpress.org/projects/wp-plugins/titanium-error-intelligence) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/titanium-error-intelligence/), check out the [SVN repository](https://plugins.svn.wordpress.org/titanium-error-intelligence/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/titanium-error-intelligence/) by [RSS](https://plugins.trac.wordpress.org/log/titanium-error-intelligence/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * Initial release ## Meta * Version **1.0.0** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/titanium-error-intelligence/) * Tags * [debugging](https://bn-in.wordpress.org/plugins/tags/debugging/)[diagnostics](https://bn-in.wordpress.org/plugins/tags/diagnostics/) [error monitoring](https://bn-in.wordpress.org/plugins/tags/error-monitoring/) [php errors](https://bn-in.wordpress.org/plugins/tags/php-errors/)[troubleshooting](https://bn-in.wordpress.org/plugins/tags/troubleshooting/) * [Advanced View](https://bn-in.wordpress.org/plugins/titanium-error-intelligence/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/titanium-error-intelligence/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/titanium-error-intelligence/reviews/) ## Contributors * [ Admin Plugins ](https://profiles.wordpress.org/aplugins/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/titanium-error-intelligence/)