log analyzer web server
Diagnostic tool for nginx, Apache, Tomcat, and IIS logs that identifies root causes and flags sensitive data.
$1
Works with the AI Agents you already use
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ón | Detalle |
|---|---|
| Tecnología | nginx |
| Entorno | PROD |
| Componente | Upstream Proxy |
| Período log | 2023/10/27 10:15:30 |
| Total eventos | 1 Crítico |
| Diagnóstico | El servidor backend no respondió a tiempo la cabecera HTTP. |
🔴 HALLAZGOS CRÍTICOS
- Severidad: CRITICAL
- 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_timeoutactual en el bloquelocation?
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
- Log Ingestion involves pasting raw log snippets from access or error files into the chat.
- Environment Contextualization requires specifying the environment (DEV/QA/PROD) to adjust severity and privacy sensitivity.
- 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.
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
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by 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 scan
Security scan passed 28 days ago