log analyzer web server

    1

    Diagnostic tool for nginx, Apache, Tomcat, and IIS logs that identifies root causes and flags sensitive data.

    $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 web server

    Example session with this skill installed

    Analyze this nginx error log from PROD: 2023/10/27 10:15:30 [error] 1234#0: *5678 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.50.

    • Read your context and instructions
    • Compiled the log analyzer web

    I have analyzed the nginx error log provided. The environment is marked as PROD, and I have identified a critical upstream timeout issue.

    REPORTE DE ANÁLISIS DE LOG — WEB SERVER

    SecciónDetalle
    Tecnologíanginx
    EntornoPROD
    ComponenteUpstream Proxy
    Período log2023/10/27 10:15:30
    Total eventos1 Crítico
    DiagnósticoEl servidor backend no respondió a tiempo la cabecera HTTP.

    🔴 HALLAZGOS CRÍTICOS

    1. Severidad: CRITICAL
    2. Mensaje: upstream timed out (110: Connection timed out)

    Causa raíz: El servicio backend (upstream) está sobrecargado o caído, o el tiempo de respuesta excede los límites configurados en nginx.
    4. Impacto: Los usuarios reciben errores HTTP 504 Gateway Timeout.
    5.

    Acción sugerida: Revisar el estado del servicio backend y considerar aumentar los valores de proxy_read_timeout y proxy_connect_timeout.

    ⚠️ DATOS SENSIBLES

    • IP del cliente: <span style="color:red;font-weight:bold">192.168.1.50</span> (PII/GDPR Risk)

    🛠️ PRÓXIMOS PASOS

    • ¿Tienes los logs del servicio backend al que se proxea la petición?
    • ¿Deseas verificar la configuración de proxy_read_timeout actual en el bloque location?

    Next steps

    • Provide the upstream service logs (e.g., Gunicorn, Node, or Tomcat logs) to find why the backend is slow.
    • Verify if this occurred during a high-traffic spike or a specific deployment window.

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

    About this skill

    Debugging web server crashes and 5XX errors is time-consuming when logs are fragmented across different formats. This skill parses raw log data from nginx, Apache, Tomcat, and IIS to generate structured diagnostics, identifying root causes like upstream timeouts, memory leaks, or configuration errors.

    What it does

    • Multi-Server Parsing interprets Nginx/Apache combined logs, Tomcat catalina.out stack traces, and IIS W3C Extended logs.
    • Root Cause Identification maps specific error codes like AH00957 or HTTP 500.19 to actionable infrastructure issues.
    • Sensitive Data Detection flags PII, internal IPs, and credentials in production logs for redaction.
    • Structured Reporting generates a standardized executive summary including severity, impact, and remediation steps.

    How it works

    1. Log Ingestion involves pasting raw log snippets from access or error files into the chat.
    2. Environment Contextualization requires specifying the environment (DEV/QA/PROD) to adjust severity and privacy sensitivity.
    3. Automated Diagnosis processes the input against known patterns like ANCM failures, Java Heap Space issues, or worker crashes.

    Frameworks & tools

    Nginx, Apache httpd, Tomcat, IIS, ASP.NET Core ANCM, Java (catalina.out), and W3C Extended log formats.

    Why this beats prompting it yourself

    Generic prompts often miss the nuances of specific server error codes or fail to link an access log 502 with the specific error log upstream timeout. This skill uses a hard-coded diagnostic framework that enforces PII safety and standardized reporting for professional hand-offs.

    Use cases

    • Debugging 502/504 Bad Gateway errors in Nginx/Apache proxy setups.
    • Troubleshooting Tomcat application startup failures and OutOfMemory errors.
    • Resolving IIS web.config permission issues or App Pool crashes.
    • Auditing logs for exposed tokens and sensitive query parameters.

    Known limitations

    Requires specific log formats like Combined, W3C Extended, or standard error logs. Truncated stack traces may prevent full Java root cause 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