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+21 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.

    Requires tech-specific reference files. Truncated logs may lead to multiple hypotheses. Cannot diagnose without minimal context like environment or server role if not present in the log.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 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

    Permissions

    Network Access
    Read Files
    Write Files
    Listed28 days ago

    What's inside

    Frequently Asked Questions

    The skill supports a wide range of formats including .log, .out, and Windows .evtx files, covering stacks from legacy IIS and Windows Server to modern Kubernetes, Docker, and major cloud providers (AWS, Azure, GCP).

    Unlike generic prompts that might miss security risks, this skill includes a dedicated security auditing layer that flags exposed tokens, IPs, and credentials in red, ensuring sensitive data isn't overlooked during troubleshooting.

    The skill is designed to be plug-and-play with leading AI agent platforms; once imported, it functions as a specialized diagnostic tool that you can interact with via text or file uploads.

    You will receive the core logic for multi-stack detection, the diagnostic reporting engine, and access to the library of technical references used to verify root causes.

    If a log fragment is too short or lacks context, the agent will move from a single diagnosis to providing a list of potential hypotheses and will prompt you for specific missing environment details to narrow it down.

    New in DevOps & Cloud