What problem does it solve?
Manually configuring OpenTelemetry for .NET applications to send traces, metrics, and logs to Maple's ingest endpoint is time-consuming and prone to misconfiguration, especially when ensuring trace context propagates correctly across services and coexists with existing observability tools.
Core Features & Use Cases
- Pre-configured OpenTelemetry Bootstrap: Provides ready-to-use configuration for ASP.NET Core applications using official OpenTelemetry packages, with inline Maple endpoint and ingest key authentication to eliminate manual OTLP exporter setup.
- Custom Business Span Instrumentation: Includes patterns for creating bounded business spans via ActivitySource to track domain-specific operations like order processing, with automatic exception and status tagging.
- Unified Logging Context: Automatically propagates trace and span IDs through ILogger calls, so log entries are correlated with corresponding traces without modifying existing logging code.
- Use Case: A .NET e-commerce orders API can use this skill to quickly send all traces, metrics, and logs to Maple, add custom spans for order submission workflows, and retain existing Application Insights exports without conflict.
Quick Start
Use the maple-csharp-style skill to configure your ASP.NET Core application to send OpenTelemetry traces, metrics, and logs directly to Maple's ingest endpoint using your project's Maple endpoint and ingest key.