log analyzer php

Debugging raw PHP environments shouldn't feel like deciphering ancient scrolls. This skill parses runtime logs from php-fpm, mod_php, and CLI to isolate root causes without the overhead of modern framework abstractions.

What it does

• Runtime diagnostic parses PHP Fatal errors, Warnings, Deprecated notices, and Parse errors from raw logs.
• Stack trace mapping reconstructs the execution flow from #0 {main} up to the failure point.
• SAPI identification distinguishes between pool-specific php-fpm events, mod_php crashes, and CLI execution failures.
• Security scrubbing flags exposed database connection strings, session IDs, and hardcoded API keys in error messages.
• Resource monitoring identifies memory limit exhaustion and execution timeouts within the runtime configuration.

How it works

1. Log ingestion where the developer provides raw text from php-fpm logs, system logs, or standard error output.
2. Environment context involving a quick check for PHP version (7.4 to 8.3) and SAPI type to adjust for language-level changes.
3. Pattern matching against known runtime failures like class autoloading issues, PDO exceptions, or SIGSEGV signals.
4. Structured reporting outputting a standardized executive summary with severity levels and sensitive data alerts.

Frameworks & tools

This tool focuses on core PHP runtimes (7.4, 8.x), php-fpm, and Composer-based autoloading. It is specifically designed for vanilla PHP or custom engines, excluding Laravel-specific log formats.

Why this beats prompting it yourself

Generic prompts often miss the subtle differences between PHP 7.4 and 8.x type conversions or fail to alert you when display_errors is dangerously active in production. This skill specifically looks for memory leaks and fpm pool saturation patterns that standard models overlook.

Use cases

• Debugging "White Screen of Death" events on legacy PHP servers.
• Investigating max_children saturation in php-fpm pools under high load.
• Auditing logs for sensitive data leaks during runtime exceptions.
• Troubleshooting PDO connection failures and SQL state errors.

Known limitations

Does not support Laravel/Illuminate log formats. Requires clear stack traces for deep analysis. Focuses on runtime and server-side errors rather than client-side logic.