Do I need to manually configure TracerProvider?

No, the skill uses AddElasticOpenTelemetry() which handles the configuration of TracerProvider and MeterProvider automatically.

Can I run this alongside the classic Elastic APM agent?

No, you should never run both on the same application. This skill provides the modern path using the OpenTelemetry-based SDK.

What is EDOT for .NET?

The Elastic Distribution of OpenTelemetry (EDOT) is an optimized SDK that simplifies the collection of traces, metrics, and logs specifically for the Elastic Stack.

Does this skill support ASP.NET Core?

Yes, it includes specialized support for ASP.NET Core instrumentation using the OpenTelemetry.Instrumentation.AspNetCore package.

Which environment variables are mandatory?

You must configure OTEL_SERVICE_NAME, OTEL_EXPORTER_OTLP_ENDPOINT, and OTEL_EXPORTER_OTLP_HEADERS (containing your API key or token).

Elastic OpenTelemetry for .NET

Name: Elastic OpenTelemetry for .NET
Author: elastic

byelastic

•

452

•

분석 및 모니터링

Instruments .NET applications with the Elastic Distribution of OpenTelemetry (EDOT) for automated tracing, metrics, and logs.

This skill streamlines the process of adding robust observability to .NET services using the Elastic Distribution of OpenTelemetry (EDOT) SDK. It provides specific guidance for installing necessary NuGet packages, registering the SDK within the application startup logic, and configuring essential environment variables for OTLP endpoints. By following these standardized patterns, developers can ensure high-quality telemetry collection while avoiding common pitfalls like manual provider configuration or conflicts with legacy Elastic APM agents.

주요 기능

01Automated SDK registration via AddElasticOpenTelemetry

02Zero-code instrumentation for ASP.NET Core services

03Standardized OTLP environment variable configuration

04452 GitHub stars

05Automatic conflict prevention with legacy APM agents

06Simplified NuGet package dependency management

사용 사례

01Standardizing telemetry collection across multiple ASP.NET Core projects

02Adding observability to a new .NET microservice without existing APM

03Migrating .NET applications from legacy Elastic APM to OpenTelemetry

주요 기능

01Automated SDK registration via AddElasticOpenTelemetry

02Zero-code instrumentation for ASP.NET Core services

03Standardized OTLP environment variable configuration

04452 GitHub stars

05Automatic conflict prevention with legacy APM agents

06Simplified NuGet package dependency management

사용 사례

01Standardizing telemetry collection across multiple ASP.NET Core projects

02Adding observability to a new .NET microservice without existing APM

03Migrating .NET applications from legacy Elastic APM to OpenTelemetry