log analyzer database

    1

    Structured log diagnostics and remediation for PostgreSQL, Oracle, and SQL Server with PII redaction.

    $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 database

    Example session with this skill installed

    Analyze these Postgres logs from PROD: 2023-10-27 10:00:05 UTC [1234] postgres@mydb FATAL: remaining connection slots are reserved for non-replication superuser connections.

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

    Analysis complete. The log indicates a critical connection limit exhaustion on a production PostgreSQL instance.

    REPORTE DE ANÁLISIS DE LOG — BASE DE DATOS

    ╔══════════════════════════════════════════════════════════════╗
    ║ REPORTE DE ANÁLISIS DE LOG — BASE DE DATOS ║
    ╚══════════════════════════════════════════════════════════════╝

    📋 RESUMEN EJECUTIVO
    Tecnología: PostgreSQL (Versión no declarada)
    Entorno: PROD
    Componente(s): mydb
    Período log: 2023-10-27 10:00:05 UTC
    Total eventos: 1 crítico | 0 warnings | 0 notables
    Diagnóstico breve: Agotamiento de slots de conexión disponibles. La instancia solo permite conexiones administrativas.

    🔴 HALLAZGOS CRÍTICOS

    FATAL: remaining connection slots are reserved: El parámetro max_connections ha sido alcanzado. Solo usuarios con privilegios de superusuario pueden conectarse para realizar tareas de mantenimiento.

    ⚠️ DATOS SENSIBLES

    • Usuario: <span style="color:red;font-weight:bold">postgres</span>
    • Base de Datos: <span style="color:red;font-weight:bold">mydb</span>

    🛠️ PRÓXIMOS PASOS
    1.

    Urgente: Implementar o revisar la configuración de un pooler de conexiones como

    PgBouncer para reducir la carga de conexiones persistentes.
    2.

    Diagnóstico: Ejecutar SELECT * FROM pg_stat_activity; para identificar sesiones inactivas o "idle in transaction" que estén ocupando slots.
    3.

    Configuración: Revisar si el valor de max_connections es adecuado para los recursos de hardware disponibles (memoria RAM/CPU).

    ¿Deseas el reporte como documento entregable (Word/Markdown)?

    Next steps

    • Provide the output of SHOW max_connections; and SHOW shared_buffers;.
    • Check if there are any long-running transactions blocking the autovacuum process.
    • Confirm the current connection pooler settings if one is in use.

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

    About this skill

    Troubleshooting database outages or performance degradation from raw logs is slow and error-prone. This skill parses logs from PostgreSQL, Oracle, and SQL Server to identify severity levels, internal error codes, and resource exhaustion.

    What it does

    • Multi-engine parsing identifies specific formats like PostgreSQL DETAIL/HINT, Oracle ORA-XXXXX codes, and SQL Server spid/Severity levels.
    • Critical event triage categorizes logs into executive summaries, ranging from PANIC/Fatal errors to informational notices.
    • PII redaction flags sensitive data including user credentials, connection strings, hostnames, and real values in deadlock traces.
    • Root cause diagnostics maps errors to specific infrastructure issues like WAL disk saturation, UNDO retention, or transaction log overflows.
    • Remediation guidance suggests specific commands like DBCC CHECKDB or ALTER USER based on the detected failure.

    How it works

    1. Engine Detection: Provide the log snippet for the skill to identify the database engine and environment (DEV/PROD).
    2. Context Validation: The skill asks for missing data such as version, connection pool details (HikariCP/PgBouncer), or supplementary trace files.
    3. Structured Diagnosis: It generates a standardized report including executive summaries and sensitivity warnings.

    Frameworks & tools

    PostgreSQL (all versions), Oracle Database (alert logs, trace files), and Microsoft SQL Server (Extended Events, spid logs).

    Why this beats prompting it yourself

    Generic prompts often confuse severity levels between engines (e.g., SQL Server Severity 16 vs PostgreSQL FATAL). This skill uses engine-specific logic to prevent incorrect recovery suggestions that could lead to data loss or further downtime.

    Use cases

    • Outage analysis for rapid identification of full disks or replication failures.
    • Security audits to find PII leaks caused by high-verbosity logging configurations.
    • Performance tuning to detect slow queries and autovacuum lock contention.
    • Application debugging to trace deadlock graphs and cursor leaks.

    Known limitations

    Does not support NoSQL databases or cloud-native wrappers like Snowflake/DynamoDB. Requires manual provision of .trc files for deep Oracle stack 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