Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Vargr Log Format Advisor

    1

    Score your logging out of 100 and get the exact fixes that make incidents faster to debug.

    Free

    1 useSecurity scanned
    Vargr Log Format Advisor

    Vargr Log Format Advisor

    Example session with this skill installed

    Audit the logging in this repo. It's a FastAPI service that ships logs to Elasticsearch.

    • Read your context and instructions
    • Compiled the vargr log format

    ✅ Worked

    Summary
    Logging score: 58/100. Diagnosable with effort: logs are JSON but have no trace ids and no service version, and one endpoint leaks emails.

    ⚠️ Privacy (must fix)
    • app/routes/auth.py:41 logs the full request body on login failures → emails and passwords reach Elasticsearch. Log user_id (opaque) and the reason instead.

    Top 3 fixes by incident impact

    1. Add service.version to every line (from the image tag) → version correlation becomes one query.
    2. Add trace.id/span.id from OpenTelemetry → follow one request across services.
    3. Log exceptions once, in the exception handler, as error.type / error.message / error.stack_trace fields.

    Findings

    AreaWhereProblemFix
    Correlationlogging_config.pyno trace.idecs_fields processor
    Errorsorders/service.py:88exception logged at 3 layerslog at the boundary only
    Levelsmiddleware.py:20404s logged as ERRORWARN or INFO
    Noisehealth.py:12/health logged every 5 s (31% of volume)drop or sample

    Proposed change: logging_config.py (structlog + ECS fields), shown as a diff.

    Next steps
    • Apply the diff? I can open a draft PR.

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

    About this skill

    Good logs turn a two-hour incident into a ten-minute one. This skill audits how your code writes logs, scores it out of 100 for diagnosability, and proposes concrete changes in your own language and logger.

    It checks structure (JSON), ECS / OpenTelemetry field names, trace and span ids, service version, how exceptions are captured, event naming, log levels, noise, and privacy leaks (tokens, passwords, emails, card and ID numbers).

    Includes ready-to-use logger configurations for Python (structlog / ecs-logging), Node.js (pino), Java (Spring Boot / Logback), .NET (Serilog) and Go (slog), plus a redaction script to check real log samples for leaks.

    Part of Vargr: Vargr Tracer finds the root cause of incidents and opens the fix; Vargr Hunter spots attacks and anomalies.

    Requires access to logger configuration files and source code call sites. Privacy scanning for sample logs requires the redact.py script included in the Vargr plugin 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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 26 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files
    Environment Variables

    • Read files in the current repository. • Optional: run scripts/redact.py (Python standard library, no network access) on log samples you provide. • Writes files only if you ask it to apply changes.

    Listed26 days ago

    What's inside

    Frequently Asked Questions

    This skill conducts a 100-point audit to transform messy text logs into structured, machine-readable data. It specifically fixes missing trace IDs for service-to-service correlation, identifies PII leaks, and suggests ways to reduce log ingest costs by filtering out high-volume noise.

    The skill is language-agnostic and supports major logging libraries including pino (Node.js), structlog (Python), zap (Go), Logback (Java), and Serilog (.NET). It is designed to work within your existing framework rather than forcing you to switch to a new library.

    Yes, the skill is designed to map your logs to industry-standard schemas like the Elastic Common Schema (ECS) and OpenTelemetry. It ensures your logs include standardized fields like `trace.id` and `span.id` for seamless integration with tools like Datadog, Honeycomb, or Loki.

    You receive the full 'tracer log format' diagnostic engine, a suite of automated remediation scripts for common logging libraries, and the `redact.py` utility for local privacy scanning of production log samples.

    While the skill performs a deep static analysis of your code, it also includes a local script to process your actual log outputs. This helps identify runtime issues like sensitive data leaks (PII) or expensive payloads that static analysis alone might miss.

    New in DevOps & Cloud