log analyzer

    1

    Automated multi-stack log analysis and diagnostic reporting with sensitive data detection.

    $5

    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

    Example session with this skill installed

    Analyze this log: 2023-10-27 10:15:03.456 ERROR 1234 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Context initialization failed. Caused by: org.postgresql.util.PSQLException: Connection refused.

    • Read your context and instructions
    • Compiled the log analyzer

    The log provided indicates a Spring Boot application failing to connect to a PostgreSQL database. I have detected two layers: Spring Boot (application) and PostgreSQL (data source).

    REPORTE DE ANÁLISIS DE LOG — SPRING BOOT / POSTGRESQL

    📋 RESUMEN EJECUTIVO
    ────────────────────
    Tecnología: Spring Boot 2.x/3.x | PostgreSQL
    Entorno: No declarado (Pendiente confirmación)
    Componente(s): Web Service (Port 8080) / DispatcherServlet
    Período log: 2023-10-27 10:15:03.456
    Total eventos: 1 crítico | 0 warnings | 0 notables
    Diagnóstico breve: Falla crítica en la inicialización del contexto debido a la imposibilidad de establecer conexión con el socket de la base de datos.

    ─────────────────────────────────────────────────────────────────
    🔴 HALLAZGOS CRÍTICOS
    ─────────────────────────────────────────────────────────────────

    #1 Severidad: FATAL / ERROR
    Ubicación: o.s.web.servlet.DispatcherServlet
    Timestamp: 2023-10-27 10:15:03.456
    Mensaje: "Context initialization failed. Caused by: <span style="color:red; font-weight:bold">org.postgresql.util.PSQLException: Connection refused</span>"
    Causa raíz: El driver de PostgreSQL no recibe respuesta del host/puerto configurado.
    Impacto: La aplicación no inicia (Application Context Failure).
    Hipótesis:
    1. El servicio de PostgreSQL está caído en el host destino.
    2. El firewall bloquea el tráfico al puerto 5432.
    3. La connection string apunta a una IP incorrecta.
    Acción sugerida: Verificar estado del servicio postgresql y conectividad vía telnet/nc al host.

    ─────────────────────────────────────────────────────────────────
    ⚠️ DATOS SENSIBLES DETECTADOS
    ─────────────────────────────────────────────────────────────────
    Tipo: Exception Detail
    Ubicación: Stack Trace
    Valor: <span style="color:red; font-weight:bold">org.postgresql.util.PSQLException</span>
    Riesgo: Revela la pila tecnológica y el tipo de base de datos.

    ─────────────────────────────────────────────────────────────────
    ❓ PREGUNTAS ABIERTAS / CONTEXTO FALTANTE
    ─────────────────────────────────────────────────────────────────

    1. ¿Este error ocurre en un entorno local, QA o Producción?
    2. ¿La base de datos corre en el mismo contenedor/host o es un servicio externo (RDS/Azure SQL)?
    3. ¿Se realizaron cambios recientes en el application.properties o en las Network Policies?

    ─────────────────────────────────────────────────────────────────
    🛠️ PRÓXIMOS PASOS RECOMENDADOS
    ─────────────────────────────────────────────────────────────────

    1. Validar Servicio: Reiniciar el servicio de base de datos si está detenido.
    2. Prueba de Red: Ejecutar ping y nc -zv <db-host> 5432 desde el servidor de aplicaciones.
    3. Revisar Credenciales: Asegurar que el usuario no esté bloqueado por demasiados intentos fallidos.

    ¿Deseas que genere este reporte como documento entregable (Word / Markdown) para compartir con el equipo?

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

    About this skill

    Debugging complex systems requires more than just reading an error message. It requires correlating stack traces with environment context while maintaining security awareness. This skill automates the triage of logs across any technical stack, from legacy Windows Event Logs to modern Kubernetes clusters and cloud providers.

    What it does

    • Automatic detection identifies the technology stack (Spring Boot, Quarkus, .NET, PHP, Kafka, etc.) based on unique log patterns and signatures.
    • Contextual interrogation prompts for missing environment details (DEV/PROD, versions, server roles) before finalizing a diagnosis.
    • Security auditing scans for sensitive data like tokens, IPs, or credentials and highlights them in red for immediate visibility without masking.
    • Root cause analysis traces error chains through Caused by or Inner Exception blocks to find the deep origin of failures.
    • Standardized reporting generates structured technical reports including executive summaries, critical findings, and actionable remediation steps.

    How it works

    1. Input log by pasting text or attaching a file (e.g., .evtx, .log, .out).
    2. Confirm technology as the agent identifies the specific framework or infrastructure layer.
    3. Provide context by answering targeted questions about the environment and server role.
    4. Review report structured with severity levels, sensitive data warnings, and prioritized next steps.

    Frameworks & tools

    Supports Windows Server, Nginx, Apache, Tomcat, IIS, Spring Boot, Quarkus, .NET, Laravel, PostgreSQL, Oracle, SQL Server, Kafka, Docker, Kubernetes, OpenShift, IBM API Connect, MinIO, AWS, Azure, and GCP.

    Why this beats prompting it yourself

    Generic prompts often hallucinate causes or ignore version-specific nuances. This skill uses a strict library of technical references and a mandatory multi-step verification process to ensure the diagnosis matches the actual environment.

    Use cases

    • Incident response to quickly identify the root cause of a production outage across multiple service layers.
    • Security audits to detect if applications are logging sensitive credentials or PII in cleartext.
    • Deployment troubleshooting for diagnosing CrashLoopBackOff or OOMKilled events in Kubernetes clusters.
    • Performance tuning by analyzing database slow-query logs or Kafka broker bottlenecks.

    Known limitations

    Requires specific technical reference files to be present. Ambiguous or highly truncated log fragments may result in multiple hypotheses rather than a single definitive cause.

    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