telemetry-dotnet-redis

Instrument Redis command traces for .NET applications using OpenTelemetry.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort of configuring Redis trace instrumentation for .NET applications using OpenTelemetry, filling the gap of missing Redis operation visibility in distributed traces.

Core Features & Use Cases

  • Dual Implementation Options: Supports both Jarvis framework plug-in integration and native OpenTelemetry.Instrumentation.StackExchangeRedis configuration for flexible adoption.
  • Multi-Connection Support: Instruments specific keyed IConnectionMultiplexer instances without interfering with other Redis connections in the same application.
  • Caching Integration: Includes built-in tracing for Jarvis caching memory invalidation Redis connections to cover all cache-related operations.
  • Use Case: A backend team running .NET microservices with Redis caching can use this Skill to trace all Redis commands, debug cache latency issues, and correlate cache hit/miss rates with end-user request traces.

Quick Start

Use the telemetry-dotnet-redis skill to add Redis trace instrumentation to your .NET application's OpenTelemetry pipeline.

Frequently Asked Questions about telemetry-dotnet-redis

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

FAQPage Schema
How do I add Redis trace instrumentation to my .NET OpenTelemetry pipeline?

Redis trace instrumentation for .NET uses OpenTelemetry to capture Redis command spans, supporting both native StackExchangeRedis configuration and Jarvis framework integration to monitor cache operations within distributed traces.

Can I instrument specific Redis connections without interfering with other IConnectionMultiplexer instances?

Yes, Redis instrumentation supports keyed IConnectionMultiplexer instances, allowing you to trace specific connections while avoiding cross-instrumentation interference between multiple Redis connections in the same application.

Does OpenTelemetry StackExchangeRedis instrumentation work with the Jarvis caching framework?

Yes, the instrumentation includes built-in tracing for Jarvis caching memory invalidation Redis connections, alongside native OpenTelemetry.Instrumentation.StackExchangeRedis support for comprehensive cache operation visibility.

What is the best way to trace Redis cache latency issues in .NET microservices?

Tracing Redis cache latency involves capturing Redis command spans via OpenTelemetry instrumentation, correlating cache activity with application traces to debug performance bottlenecks and monitor cache hit/miss rates.

Why are my Redis operations missing from distributed traces in .NET?

Missing Redis operations in distributed traces indicate missing instrumentation; applying OpenTelemetry Redis tracing captures command spans and correlates cache activity with end-user request traces for full visibility.