netdata-collector-config

Name: netdata-collector-config
Availability: InStock
Author: netdata

Configure OpenTelemetry Collector pipelines to export OTLP/gRPC telemetry to Netdata.

1|Updated Apr 17, 2026

Search Tags:#deployment #kubernetes #opentelemetry #netdata #otel-collector #otlp grpc #chart mapping

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you configure an OpenTelemetry Collector to forward metrics (and logs) to Netdata correctly, including the right exporter setup and Kubernetes deployment shape.

Core Features & Use Cases

OTLP-to-Netdata exporter configuration: Ensures the Collector uses OTLP/gRPC (not OTLP/HTTP) when exporting to Netdata.
Kubernetes deployment patterns: Guides DaemonSet, gateway (Deployment), and OpenTelemetry Operator-managed approaches.
Correct chart dimension shaping: Teaches how to control Netdata chart dimensions via an OTLP attribute plus a Netdata mapping file, rather than relying on Collector annotations.

Quick Start

Ask the agent to generate a minimal OpenTelemetry Collector config that forwards hostmetrics and filelog to Netdata using the DaemonSet pattern, with gRPC enabled and the correct mapping approach for dimension attributes.

Frequently Asked Questions about netdata-collector-config

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

FAQPage Schema

How do I configure an OpenTelemetry Collector to export metrics to Netdata?▼

To export metrics to Netdata, configure your OpenTelemetry Collector with an OTLP exporter using the gRPC protocol, set the endpoint and TLS transport options, and shape chart dimensions using an OTLP attribute plus a mapping file.

Can I use OTLP HTTP to send telemetry data from the Collector to Netdata?▼

No, Netdata requires the OTLP gRPC protocol for telemetry ingestion. You must explicitly set the exporter protocol to grpc in your OpenTelemetry Collector configuration instead of using OTLP HTTP.

How do I deploy an OpenTelemetry Collector pipeline for Netdata in Kubernetes?▼

You can deploy the OpenTelemetry Collector pipeline for Netdata in Kubernetes using a DaemonSet, a gateway Deployment, or the OpenTelemetry Operator CRD to ingest end-to-end metrics and logs.

How do I map OpenTelemetry metrics to Netdata chart dimensions correctly?▼

To map metrics to Netdata chart dimensions, use a specific OTLP dimension attribute alongside a Netdata mapping file rather than relying on Collector annotations to shape the visual dimensions.

Does Netdata support OpenTelemetry trace pipelines from the Collector?▼

No, Netdata drops trace pipelines. You should exclude OpenTelemetry Collector trace pipelines from your configuration and only forward metrics and logs to Netdata.

What is the best way to collect hostmetrics and filelog for Netdata using the Collector?▼

The best way is to generate a minimal OpenTelemetry Collector config using the DaemonSet pattern, enabling gRPC export to Netdata and applying the correct mapping approach for dimension attributes.