
Observability Edot Dotnet Migrate
- 2 installs
- 31 repo stars
- Updated May 28, 2026
- elastic/cursor-plugins
observability-edot-dotnet-migrate skill documents Migrate a .
About
observability-edot-dotnet-migrate skill documents Migrate a .NET application from the classic Elastic APM .NET agent to the EDOT .NET SDK. Use when switching from Elastic.Apm. packages to Elastic.OpenTelemetry.. name: observability-edot-dotnet-migrate description: >
- Migrate a .
- Platform-specific setup patterns for observability-edot-dotnet-migrate.
- Evidence-backed steps from upstream SKILL.md.
- When-to-use criteria for observability-edot-dotnet-migrate versus alternatives.
Observability Edot Dotnet Migrate by the numbers
- 2 all-time installs (skills.sh)
- Ranked #1,786 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Jul 24, 2026 (Skillselion catalog sync)
observability-edot-dotnet-migrate capabilities & compatibility
- Capabilities
- observability edot dotnet migrate quick start · observability edot dotnet migrate when to use gu · observability edot dotnet migrate integration pa
- Works with
- elasticsearch
- Use cases
- security audit
What observability-edot-dotnet-migrate says it does
Migrate a .NET application from the classic Elastic APM .NET agent to the EDOT .NET
SDK. Use when switching from Elastic.Apm.* packages to Elastic.OpenTelemetry.
npx skills add https://github.com/elastic/cursor-plugins --skill observability-edot-dotnet-migrateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 31 |
| Last updated | May 28, 2026 |
| Repository | elastic/cursor-plugins ↗ |
How do I use observability-edot-dotnet-migrate correctly?
Migrate a .NET application from the classic Elastic APM .NET agent to the EDOT .NET SDK. Use when switching from Elastic.Apm.* packages to Elastic.OpenTelemetry.
Who is it for?
Teams implementing observability-edot-dotnet-migrate workflows from the catalog.
Skip if: Skip when requirements clearly match a different specialized stack.
When should I use this skill?
User asks about observability-edot-dotnet-migrate, migrate a .net application from the classic elastic apm .net agent to the edot .net sdk. u.
What you get
Working observability-edot-dotnet-migrate setup with validated configuration and next steps.
Files
EDOT .NET Migration
Read the migration guide before making changes:
Guidelines
1. Remove ALL classic APM references: Elastic.Apm.* NuGet packages (including Elastic.Apm.NetCoreAll), UseAllElasticApm() / AddAllElasticApm() calls, the ElasticApm section from appsettings.json, and all ELASTIC_APM_* env vars 1. Add NuGet packages: Elastic.OpenTelemetry and OpenTelemetry.Instrumentation.AspNetCore (for ASP.NET Core apps) 1. Register EDOT in startup: call builder.AddElasticOpenTelemetry() on the IHostApplicationBuilder (in Program.cs or equivalent). Without this, no telemetry is collected 1. Set exactly three required environment variables:
OTEL_SERVICE_NAME(replacesELASTIC_APM_SERVICE_NAME/ElasticApm:ServiceName)OTEL_EXPORTER_OTLP_ENDPOINT— must be the managed OTLP endpoint or EDOT Collector URL. Do NOT reuse the
old ELASTIC_APM_SERVER_URLS value. Never use an APM Server URL (no apm-server, no :8200, no /intake/v2/events)
OTEL_EXPORTER_OTLP_HEADERS—"Authorization=ApiKey <key>"or"Authorization=Bearer <token>"(replaces
ELASTIC_APM_SECRET_TOKEN) 1. Do NOT set OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, or OTEL_LOGS_EXPORTER — the defaults are already correct 1. Never run both classic Elastic APM agent (Elastic.Apm.*) and EDOT on the same application
Examples
See the EDOT .NET migration guide for complete examples.
Related skills
FAQ
What does observability-edot-dotnet-migrate do?
observability-edot-dotnet-migrate skill documents Migrate a .
When should I use observability-edot-dotnet-migrate?
User asks about observability-edot-dotnet-migrate, migrate a .net application from the classic elastic apm .net agent to the edot .net sdk. u.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.