log analyzer dotnet

    1

    Structured diagnostic reports for .NET and C# logs, including EF Core, Serilog, and ASP.NET Core error tracing.

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

    Example session with this skill installed

    Analyze this log: fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1] An unhandled exception has occurred. System.NullReferenceException: Object reference not set to an instance.

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

    I have analyzed the provided log snippet. The failure originates from a NullReferenceException within the ASP.NET Core middleware pipeline.

    REPORTE DE ANÁLISIS DE LOG — .NET / C#

    SecciónDetalle
    Tecnología.NET 8 / ASP.NET Core (MEL)
    EntornoNo declarado (Posible DEV via DeveloperExceptionPage)
    ComponenteMicrosoft.AspNetCore.Diagnostics
    DiagnósticoExcepción de referencia nula no controlada en el middleware.

    🔴 HALLAZGOS CRÍTICOS

    1. Severidad: CRITICAL
    2. Ubicación: DeveloperExceptionPageMiddleware
    3. Mensaje: System.NullReferenceException: Object reference not set to an instance.

    Causa raíz: Intento de acceder a un miembro de un objeto que es null. Probablemente un servicio no inyectado o una propiedad de modelo vacía.
    5.

    Acción sugerida: Revisar el stack trace completo para identificar la línea exacta en el código de usuario. Verificar registros en Program.cs si el error ocurre al inicio.

    ⚠️ DATOS SENSIBLES

    • No se detectaron Connection Strings o Tokens en el fragmento proporcionado.

    ❓ PREGUNTAS ABIERTAS

    • ¿Puedes proporcionar el stack trace completo incluyendo las líneas de código de tu aplicación?
    • ¿Este error ocurre en todas las peticiones o solo en una ruta específica?

    Next steps

    • Verifique si todos los servicios requeridos están registrados en el contenedor de Dependency Injection.
    • Comparta el archivo appsettings.json (sin secretos) para validar la configuración del middleware.
    • Proporcione los logs de EF Core si la excepción ocurre durante una consulta a base de datos.

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

    About this skill

    Debug .NET and C# application failures faster by automating log parsing and diagnostic reporting. This skill identifies root causes across ASP.NET Core, Worker Services, and Entity Framework Core logs, including support for Serilog, NLog, and Microsoft.Extensions.Logging formats. It eliminates the manual effort of tracing long stack traces and identifying cascading failures.

    What it does

    • Trace Exception Chains by identifying the primary failure point and traversing Inner Exception blocks to find the root cause.
    • Analyze Framework Logs from Microsoft.AspNetCore, EF Core slow queries, and Dependency Injection resolution errors.
    • Sanitize Sensitive Data by flagging connection strings, JWT tokens, PII, and SQL parameters in red to prevent security leaks.
    • Correlate Requests using RequestId or TraceId to reconstruct the execution flow of failed operations.
    • Detect Performance Issues like N+1 queries, slow DB commands, and circuit breaker rejections from Polly.

    How it works

    1. Submit Log Snippet: Provide the raw log output containing System.*Exception, [ERR], or fail: markers.
    2. Context Validation: The skill asks for missing details regarding the .NET version, logging framework, or environment if not evident.
    3. Structured Diagnostics: It parses the content to build a formal report following a standardized executive summary format.

    Frameworks & tools

    Compatible with .NET 6/7/8 and Framework 4.x. Supports Serilog, NLog, log4net, Microsoft.Extensions.Logging, Entity Framework Core, and Polly.

    Why this beats prompting it yourself

    Generic prompts often miss the nuance of .NET-specific DI captive dependencies or EF Core sensitive data logging risks. This skill uses a structured diagnostic template that ensures every critical finding includes a hypothesis and actionable C# fix.

    Use cases

    • Debugging Unable to resolve service errors in complex DI containers.
    • Identifying deadlocks (SQL 1205) and timeouts in Entity Framework Core.
    • Auditing logs for accidentally exposed PII or credentials in non-prod environments.
    • Profiling slow ASP.NET Core endpoints using Hosting.Diagnostics data.

    Known limitations

    Requires full stack traces for accurate root cause analysis. Performance insights for EF Core require Executed DbCommand logs to be present.

    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