maple-csharp-style

Configure ASP.NET Core OpenTelemetry exports to Maple's ingest endpoint.

1.6k|107|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/MapleTechLabs/maple --skill maple-csharp-style-mapletechlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maple-csharp-style
Source: https://github.com/MapleTechLabs/maple/tree/main/skills/maple-csharp-style
Command: npx skills add https://github.com/MapleTechLabs/maple --skill maple-csharp-style-mapletechlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about maple-csharp-style

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

FAQPage Schema
How do I configure OpenTelemetry for ASP.NET Core to send traces and logs to a custom OTLP endpoint?

You can configure OpenTelemetry for ASP.NET Core by using pre-configured bootstrap settings that provide ready-to-use OTLP HTTP export with inline endpoint and ingest key authentication, eliminating manual exporter setup.

How does ILogger trace context propagation work with OpenTelemetry in .NET?

ILogger trace context propagation works by automatically injecting trace and span IDs into log entries, correlating logs with corresponding traces without requiring any modifications to your existing logging code.

Can I use a custom OpenTelemetry setup alongside existing Application Insights exporters in .NET?

Yes, the custom OpenTelemetry setup supports coexistence with third-party observability exporters, allowing you to route traces to a new endpoint while retaining existing Application Insights exports without conflict.

How do I create custom business spans for domain-specific operations in .NET OpenTelemetry?

You create custom business spans using ActivitySource to track domain-specific operations like order processing, with automatic exception and status tagging applied to each bounded span.

What's the best way to bootstrap .NET observability without manual OpenTelemetry misconfiguration?

The best way to bootstrap .NET observability is using pre-configured OpenTelemetry packages with inline authentication, which eliminates manual configuration effort and prevents routing errors for traces, metrics, and logs.