caching-dotnet-otel-redis

Instrument Redis cache connections with OpenTelemetry tracing in .NET 9 projects.

12|2|Updated May 4, 2020
One-click install
npx skills add https://github.com/hoangnh2412/jarvis --skill caching-dotnet-otel-redis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caching-dotnet-otel-redis
Source: https://github.com/hoangnh2412/jarvis/tree/main/.opencode/skills/caching-dotnet/providers/otel-redis
Command: npx skills add https://github.com/hoangnh2412/jarvis --skill caching-dotnet-otel-redis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Jarvis.Caching.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.

Frequently Asked Questions about caching-dotnet-otel-redis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add OpenTelemetry distributed tracing to Redis cache operations in .NET?

You can instrument Redis cache operations for OpenTelemetry by registering dedicated Redis instrumentation extension methods in your application's ConfigureTrace pipeline to capture trace data for all individual Redis connection calls.

Why are my Redis cache and memory cache invalidation traces merging in ASP.NET Core OpenTelemetry?

Redis cache and memory invalidation traces merge without separate instrumentation. Dual instrumentation isolates distributed Redis cache connections from memory cache invalidation connections to prevent confusing, merged trace data.

Can I use this Redis cache instrumentation with any .NET 9 project?

No, this Redis cache instrumentation applies specifically to Jarvis framework-based .NET 9 projects using Redis for distributed caching and memory cache invalidation, requiring existing Jarvis OpenTelemetry pipelines.

What is the best way to track cache hit and miss flows across multi-service .NET backends?

The best way to track cache hit and miss flows across multi-service .NET backends is to instrument Redis cache operations for OpenTelemetry traces, capturing individual connection calls to identify slow lookups or invalidation failures.

Do I need manual trace configuration to instrument Redis connections in the Jarvis framework?

No, you do not need manual trace configuration to instrument Redis connections in the Jarvis framework. The integration works seamlessly via dedicated extension methods with the existing Jarvis OpenTelemetry setup.