Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Log Anomaly Detection Parser

    1

    Parse JSON, Logfmt, and Syslog to detect error clusters, stack trace fingerprints, and performance bottlenecks.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Log Anomaly Detection Parser

    Log Anomaly Detection Parser

    Example session with this skill installed

    Analyze these logs for anomalies: [2024-05-20T10:15:01Z] ERROR: Connection timeout in db_pool. [2024-05-20T10:15:05Z] WARN: Retrying connection. [2024-05-20T10:15:10Z] HTTP 504: Gateway Timeout.

    • Read your context and instructions
    • Compiled the log anomaly detection

    I have analyzed the provided log excerpts. I detected a correlated failure pattern where a database connection pool exhaustion directly preceded the external gateway timeouts.

    Log Forensic Analysis Report

    MetricDetail
    Primary AnomalyDB Connection Timeout Spike
    Correlated ImpactHTTP 504 Gateway Timeouts
    Error Fingerprintdb_pool_timeout_err_01
    Frequency2 occurrences in 9-second window
    Root CauseDownstream dependency latency causing pool exhaustion

    Actionable Debugging Checklist

    • Check max_connections setting in database configuration.
    • Verify if connection leak exists in the db_pool initialization logic.
    • Monitor network latency between the application server and DB instance.

    FluentBit Parser Regex

    [PARSER]
        Name   app_log_anomaly
        Format regex
        Regex  ^\[(?<time>[^\]]+)\] (?<level>[A-Z]+): (?<message>.*)$
        Time_Key time
        Time_Format %Y-%m-%dT%H:%M:%SZ
    

    Next steps

    1. Review the connection pool limit in your .env or config file.
    2. Apply the provided regex to your FluentBit configuration to monitor this pattern in production.
    3. Check for recent infrastructure changes affecting DB network routes.

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

    About this skill

    Log analysis often fails when humans try to spot patterns across thousands of lines of unstructured text. This skill parses complex application logs to isolate silent failures, performance bottlenecks, and error clusters that manual inspection misses.

    What it does

    • Multi-format parsing processes raw JSON, Logfmt, Syslog, and Apache/Nginx stderr streams.
    • Error clustering groups stack traces by fingerprint to identify high-frequency root causes.
    • Anomaly detection spots spikes in error rates and identifies slow query bottlenecks.
    • Signal correlation links disparate events, such as database timeouts leading to gateway errors.
    • Config generation outputs ready-to-use regex for FluentBit or Vector collectors.

    How it works

    1. Input your raw log excerpts or point the agent to log files within your project workspace.
    2. The agent parses the entries and categorizes them by severity and service origin.
    3. It generates a diagnostic report identifying frequency, fingerprints, and system correlations.
    4. You receive a debugging checklist and the specific regex needed for production observability tools.

    Frameworks & tools

    Works with JSON, Logfmt, Syslog, Apache, and Nginx formats. Compatible with observability pipelines like FluentBit and Vector.

    Why this beats prompting it yourself

    Generic prompts often miss the relationship between consecutive log lines or fail to group similar stack traces effectively. This skill applies a deterministic forensic workflow to ensure system signals are correlated rather than just listed.

    Use cases

    • Debugging intermittent HTTP 504 errors by tracing upstream database connection issues.
    • Identifying the most frequent unhandled exceptions after a production deployment.
    • Generating log parsing rules for a new service to be ingested by FluentBit.
    • Finding slow database queries hidden within high-volume application logs.

    Known limitations

    Analysis is read-only and restricted to log excerpts or files within the current project workspace. It does not support live streaming log tailing or remote server access.

    Read-only analysis on local files or excerpts. No live tailing or remote SSH log access. Workspace restricted to project root.

    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 4 days ago

    Requires

    File System Read/Write (strictly scoped to current project workspace `./`).
    Zero global installation or elevated privileges required.

    Permissions

    Read Files

    Target Use Cases: - Parse these server logs to diagnose 502 bad gateway errors. - Analyze application log traces for recurring exception patterns. - Detect anomalies and slow database queries from access logs.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    This skill supports a wide range of common formats including JSON, Logfmt, Syslog, and standard Apache/Nginx stderr streams, ensuring it can handle most modern application and infrastructure logs.

    Unlike generic prompts that treat logs as simple text, this skill uses a forensic workflow to correlate disparate events and cluster stack traces by their unique fingerprints to find root causes faster.

    The skill is designed to work within your AI agent's workspace; simply provide raw log excerpts or point the agent to local log files for immediate analysis.

    No, this tool operates on a read-only basis within your project workspace and does not support live log tailing or direct remote access to external servers.

    Beyond just identifying errors, the skill generates ready-to-use regex and configuration rules specifically formatted for popular collectors like FluentBit and Vector.

    You receive the full agent skill capability, including its specialized diagnostic reporting, error clustering logic, and the ability to generate production-ready parsing configurations.