skills.rest
yeeehaooo
yeeehaoooCOMMUNITY
Explore all skills by this author →
GitHub

execution-tracking

Track .NET handler execution with correlation IDs and configurable tracking levels.

Updated Feb 20, 2026
Search Tags:#observability#dotnet#performance-monitoring#execution-tracking#audit-trail#correlation-id#decorator
One-click install
npx skills add https://github.com/yeeehaooo/WorkSpace --skill execution-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execution-tracking
Source: https://github.com/yeeehaooo/WorkSpace/tree/main/skills/dotnet/patterns/execution-tracking
Command: npx skills add https://github.com/yeeehaooo/WorkSpace --skill execution-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track handler execution for observability, auditing, and debugging in .NET applications.

Core Features & Use Cases

  • Track execution time for performance monitoring
  • Record input parameters and results (sanitized)
  • Track errors and exceptions
  • Support correlation IDs for request tracing
  • Configurable tracking levels (none, errors only, full)
  • Tracking interface defined in Application layer
  • Tracking implementations in Infrastructure layer

Quick Start

Integrate an IExecutionTracker into a command handler and verify that operation duration and correlation IDs are tracked.

Frequently Asked Questions about execution-tracking

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

FAQPage Schema
How do I track handler execution time for observability in .NET?▼

Track handler execution time in .NET by integrating an IExecutionTracker interface into your command handlers, verifying that operation duration and correlation IDs are recorded for performance monitoring.

What is the best way to implement an audit trail for command handlers in .NET?▼

An audit trail for .NET command handlers is implemented by defining an IExecutionTracker interface in the Application layer and a LoggingExecutionTracker in the Infrastructure layer to record sanitized inputs and outputs.

Can I trace requests across Application and Infrastructure layers using correlation IDs?▼

Yes, you can trace requests across Application and Infrastructure layers using correlation IDs, which are supported by the execution tracking mechanism to enable end-to-end request observability and debugging.

How do I configure tracking levels to log only errors in a .NET application?▼

Configure tracking levels in your .NET application by selecting from none, errors only, or full tracking options, allowing you to control the volume of execution data recorded for observability and auditing.

Does execution tracking sanitize input parameters and results before logging?▼

Yes, execution tracking sanitizes input parameters and results before logging, ensuring that sensitive data is protected while still providing sufficient context for debugging and audit trails.

Why do I need separate tracking interfaces in the Application and Infrastructure layers?▼

Separate tracking interfaces are needed because the Application layer defines the IExecutionTracker contract while the Infrastructure layer provides the LoggingExecutionTracker implementation, maintaining clean separation of concerns in .NET.

Related Skills

Explore More Software Engineering Skills→
partme-aipartme-ai
610

ddd-cola

Guide COLA architecture implementation across adapter, application, domain, and infrastructure layers.

Official
Intermediate
gouravsingh311gouravsingh311

python-observability

Unify logs, metrics, and traces in Python applications with OpenTelemetry and Prometheus.

Community
Advanced
GabeujinGabeujin

dotnet-best-practices

Validate .NET/C# code against best practices for design patterns and dependency injection.

Community
Advanced
AGIBuildAGIBuild
10

dotnet-observability

Integrate OpenTelemetry tracing, metrics, and structured logging into .NET applications.

Community
Advanced