telemetry-dotnet

Automate OpenTelemetry tracing, metrics, and logging integration for ASP.NET Core applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about telemetry-dotnet

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

FAQPage Schema
How do I add OpenTelemetry tracing and metrics to an ASP.NET Core app?

OpenTelemetry tracing and metrics are added to ASP.NET Core apps by initializing telemetry instrumentation and configuring OTLP export. This skill automates that setup for Jarvis framework projects, including pre-built configuration templates for traces, metrics, and logging.

Can I configure Redis and Entity Framework Core instrumentation with OpenTelemetry in .NET?

Redis and Entity Framework Core instrumentation can be configured with OpenTelemetry in .NET. This skill provides targeted workflows to extend existing telemetry setups with dependency-specific instrumentation for Redis, EF Core, and custom trace or metric plugins.

What is the best way to secure OTLP telemetry export and prevent PII leakage in .NET?

Securing OTLP telemetry export and preventing PII leakage in .NET requires configuring PII-safe header allowlisting and secure secret management. This skill includes production best practices for sampling configuration and excluding health check paths to avoid common observability pitfalls.

How do I propagate trace context in background worker cron jobs using .NET?

Propagating trace context in background worker cron jobs using .NET requires scoped trace and log context patterns. This skill provides built-in patterns for adding trace and log context to scheduled cron jobs running within the Jarvis framework.

Does this OpenTelemetry setup work with existing .NET projects or only new ones?

This OpenTelemetry setup works with both new and existing .NET projects. It offers a new project initialization workflow for full setup and an extension workflow to add targeted Redis, EF Core, or custom observability instrumentation to projects already wired with core telemetry.

Why are my ASP.NET Core health check endpoints generating noisy trace data?

ASP.NET Core health check endpoints generate noisy trace data when not excluded from telemetry collection. This skill configures excluded health check paths and applies sampling rules to ensure production-ready observability without unnecessary telemetry overhead.