netdata-migration

Name: netdata-migration
Availability: InStock
Author: netdata

Migrate observability from Datadog, New Relic, Dynatrace, or Prometheus to Netdata via OpenTelemetry and OTLP/gRPC.

1|Updated Apr 17, 2026

Search Tags:#prometheus #opentelemetry #datadog #otlp #netdata #observability migration #alert migration

Ready to run

npx skills add https://github.com/netdata/skills --skill netdata-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: netdata-migration
Source: https://github.com/netdata/skills/tree/main/skills/netdata-migration
Command: npx skills add https://github.com/netdata/skills --skill netdata-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you migrate metrics and logs from Datadog, New Relic, Dynatrace, or Prometheus into Netdata using OpenTelemetry and OTLP/gRPC, while setting correct expectations for what will and will not carry over.

Core Features & Use Cases

Choose a migration strategy (parallel run vs cutover) to validate parity safely before decommissioning the old vendor.
Map vendor concepts to OpenTelemetry signals including resource attributes, metric naming expectations, and log/metric ingestion patterns.
Rebuild dashboards and alerts with Netdata in mind by translating alert logic and acknowledging that metric/chart parity is usually not 1:1.

Quick Start

Ask an AI agent to migrate your Datadog or Prometheus setup to Netdata by switching your services to OpenTelemetry, forwarding metrics to Netdata via OTLP/gRPC, and outlining the required alert and dashboard parity work.

Frequently Asked Questions about netdata-migration

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

FAQPage Schema

How do I migrate observability data from Datadog to Netdata using OpenTelemetry?▼

To migrate observability data from Datadog to Netdata, replace vendor SDKs with OpenTelemetry and configure exporters to send metrics via OTLP/gRPC to Netdata's endpoint. You must map resource attributes and rebuild dashboards and alerts, as metric parity is not 1:1.

What is the best way to switch Prometheus monitoring to Netdata?▼

Switching Prometheus monitoring to Netdata involves utilizing Prometheus reuse paths by reconfiguring exporters to forward metrics via OTLP/gRPC. You will need to handle resource attribute mapping and translate alert logic to achieve metric parity within Netdata.

Can I run Datadog and Netdata in parallel during an observability migration?▼

Yes, you can run Datadog and Netdata in parallel during an observability migration. This parallel-run strategy allows you to validate metric parity and alert logic safely before fully decommissioning the old vendor through a final cutover.

Does Netdata support historical metric backfill when migrating from Dynatrace?▼

No, Netdata does not accept traces or provide a historical backfill tool when migrating from Dynatrace or other vendors. You must forward new metrics via OTLP/gRPC and rebuild dashboards without importing historical data.

What OTLP endpoint does Netdata use for ingesting exported metrics?▼

Netdata uses the default OTLP/gRPC endpoint on port 4317 for ingesting exported metrics. You must reconfigure your OpenTelemetry exporters to target this endpoint and ensure resource attributes are correctly mapped.