telemetry-dotnet

What problem does it solve?

Manually configuring production-ready OpenTelemetry for ASP.NET Core applications built with the Jarvis framework is time-consuming, error-prone, and often lacks proper guardrails for PII safety, sampling, and common dependency instrumentation. This skill eliminates that overhead with structured, validated workflows for both new and existing projects.

Core Features & Use Cases

• New Project Initialization: Quickly set up full OpenTelemetry support (tracing, metrics, logging) for new Jarvis-based .NET projects with pre-built configuration templates.
• Existing Project Extension: Add targeted observability for Redis, Entity Framework Core, and custom trace/metric/log plugins to projects that already have core Jarvis OpenTelemetry wired up.
• Production Best Practices: Includes guidance for secure OTLP secret management, PII-safe header allowlisting, sampling configuration, and excluded health check paths to avoid common observability pitfalls.
• Background Worker Support: Provides built-in patterns for adding trace and log context to scheduled cron jobs running in the Jarvis framework.

Quick Start

Use the telemetry-dotnet skill to configure OpenTelemetry tracing, metrics, and logging for your Jarvis-based ASP.NET Core application, choosing the initialization workflow for new projects or the add workflow to extend existing telemetry with Redis, EF Core, or custom instrumentation.