caching-dotnet-otel-redis

What problem does it solve?

Redis cache operations in .NET backend applications built with the Jarvis framework lack built-in distributed tracing visibility, making it difficult to debug latency issues, track cache hit/miss flows, and diagnose cross-service cache invalidation failures.

Core Features & Use Cases

• Dual Redis Instrumentation: Separately instruments distributed Redis cache connections and memory cache invalidation Redis connections to avoid merged, confusing trace data.
• Seamless Jarvis Integration: Works with existing Jarvis OpenTelemetry setup via dedicated extension methods, no manual trace configuration required.
• Use Case: For a multi-service e-commerce backend using Jarvis caching, this skill lets you trace every Redis call to identify slow cache lookups or failed inventory invalidation events across services.

Quick Start

Use the caching-dotnet-otel-redis skill to add OpenTelemetry tracing to your Jarvis .NET application's Redis cache connections by registering the required instrumentation methods in your ConfigureTrace pipeline.