log analyzer laravel

    1

    Structured Laravel log analysis and diagnostic reporting for versions 9, 10, and 11.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    log analyzer laravel

    Example session with this skill installed

    Analyze this log: [2024-05-20 14:10:05] production.ERROR: Illuminate\Database\QueryException: SQLSTATE[HY000] [2002] Connection refused (SQL: select * from users) in /var/www/vendor/laravel/framework/...

    • Read your context and instructions
    • Compiled the log analyzer laravel
    • Generated the document

    I have analyzed the provided Laravel log entry. The error indicates a database connectivity issue in a production environment.

    REPORTE DE ANÁLISIS DE LOG — LARAVEL

    FieldDetails
    TecnologíaLaravel 10.x / PHP 8.2
    Entornoproduction
    Componente(s)app / Eloquent
    Período log2024-05-20 14:10:05
    Total eventos1 Crítico
    DiagnósticoDatabase connection refused. The application cannot reach the database server at the specified host.

    🔴 HALLAZGOS CRÍTICOS

    QueryException (SQLSTATE 2002): The database driver failed to establish a socket connection. This usually means the DB server is down, the port is blocked by a firewall, or the DB_HOST in .env is incorrect for the production network.

    Connection Refused: Specifically indicates that the host is reachable but not accepting connections on the configured port (default 3306).

    🟡 ADVERTENCIAS

    Sensitive Data Check: No sensitive keys found in the provided snippet. Ensure DB_PASSWORD is not logged in full stacktraces.

    🛠️ PRÓXIMOS PASOS

    1. Verify if the database service is running on the production host.
    2. Check DB_HOST and DB_PORT in your production .env file.
    3. Confirm that the web server IP is whitelisted in the database firewall rules.
    4. Run php artisan config:clear to ensure no stale configuration is being used.

    Next steps

    • Would you like me to check for specific failed_jobs related to this database outage?
    • Do you want this report exported as a Markdown file?

    log-analyzer-laravel.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Debugging production Laravel logs manually wastes hours of developer time. This skill parses laravel.log files and exception stacktraces to provide structured diagnostics. It identifies the root cause of failures across the Laravel ecosystem, from Eloquent query exceptions to Horizon queue bottlenecks.

    What it does

    • Exception parsing extracts real class names from Laravel wrappers and identifies the first application-level stacktrace frame.
    • Environment detection correlates errors with specific configurations across local, staging, and production setups.
    • Sensitive data redaction flags and masks leaked .env keys, PII, and session tokens within log contexts.
    • Subsystem analysis diagnoses specific failures in Artisan, Horizon, Octane, and the Service Container.
    • Database troubleshooting decodes QueryException SQLSTATE codes to separate syntax errors from infrastructure timeouts.

    How it works

    1. Log detection scans input for Illuminate\ namespaces or standard Laravel log timestamps.
    2. Context gathering requests missing data like APP_ENV, Laravel version, or the specific QUEUE_CONNECTION driver.
    3. Trace analysis isolates the faulting line of code by filtering out vendor/ directory noise.
    4. Report generation produces a structured diagnostic summary including critical findings and next steps.

    Frameworks & tools

    Laravel 9, 10, and 11 frameworks. PHP, Artisan, Eloquent, Horizon, Octane, Sanctum, and Passport.

    Why this beats prompting it yourself

    Generic AI often misses Laravel-specific nuances like Service Container binding errors or Octane-induced memory leaks. This skill enforces strict security by redacting APP_KEY and handles complex multi-line exception stacktraces that standard prompts often truncate or misinterpret.

    Use cases

    • Debugging Target class [X] does not exist errors in the Service Container.
    • Identifying memory leaks in Laravel Octane caused by static state.
    • Troubleshooting failed jobs and MaxAttemptsExceededException in Horizon.
    • Auditing logs for accidentally exposed database credentials or API keys.

    Known limitations

    Does not support raw PHP error logs without Laravel namespaces. Requires the full exception stacktrace for accurate trace analysis.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    What's inside

    Frequently Asked Questions