skills.rest
netdata
netdataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

netdata-instrumentation

Configure OpenTelemetry SDK instrumentation to export OTLP/gRPC metrics to Netdata.

1|Updated Apr 17, 2026
Search Tags:#instrumentation#opentelemetry#netdata#sdk setup#auto-instrumentation#resource attributes#otlp grpc
One-click install
npx skills add https://github.com/netdata/skills --skill netdata-instrumentation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: netdata-instrumentation
Source: https://github.com/netdata/skills/tree/main/skills/netdata-instrumentation
Command: npx skills add https://github.com/netdata/skills --skill netdata-instrumentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Adding observability to application code is hard, especially when you need OpenTelemetry SDK setup that exports the right signals to Netdata reliably.

Core Features & Use Cases

  • OTLP/gRPC metrics export to Netdata: Configures OTLP metrics delivery to the Netdata OTLP port (default 4317) with correct endpoint handling.
  • Signal guidance and guardrails: Ensures traces are not exported to Netdata (Netdata accepts metrics and logs, not traces yet).
  • Resource attributes that Netdata and MCP rely on: Establishes required attributes like service.name and commonly used fields like service.version and deployment.environment.
  • Language-specific wiring patterns: Supports common approaches for Node.js, Python, Java, Go, .NET, Ruby, and PHP, including auto-instrumentation where available.

Quick Start

Tell your AI agent: "Add OpenTelemetry instrumentation to my service so it exports metrics (and logs if supported) to my Netdata via OTLP/gRPC on port 4317, using OTEL_SERVICE_NAME, OTEL_RESOURCE_ATTRIBUTES, and the correct OTEL exporter environment variables for my language."

Frequently Asked Questions about netdata-instrumentation

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

FAQPage Schema
How do I configure OpenTelemetry SDK to export metrics to Netdata via OTLP gRPC?▼

To export OpenTelemetry metrics to Netdata, configure the OTLP gRPC exporter to target port 4317, set the correct endpoint formatting, and define required OTEL resource attributes like service.name for proper data delivery.

Does Netdata support OpenTelemetry traces export?▼

Netdata does not support OpenTelemetry traces export yet. You must explicitly disable tracing export in your SDK configuration, as Netdata currently accepts only OTLP metrics and logs delivered via the gRPC endpoint.

What OTEL resource attributes are required for Netdata to receive application metrics?▼

Netdata requires the service.name OTEL resource attribute to properly receive and display application metrics. You should also configure commonly used fields like service.version and deployment.environment for complete observability context.

Can I use auto-instrumentation to send OTLP metrics from Node.js or Python to Netdata?▼

Yes, you can use auto-instrumentation to send OTLP metrics to Netdata across Node.js, Python, Java, Go, .NET, Ruby, and PHP. The setup supports common auto-instrumentation wiring patterns where available in each language.

What is the best way to migrate vendor-specific application instrumentation to OpenTelemetry for Netdata?▼

The best way to migrate vendor-specific instrumentation to OpenTelemetry for Netdata is to wire language-specific OTel SDKs to export metrics via OTLP gRPC on port 4317, replacing proprietary agents with standard OTEL environment variables.

Why are my OTLP metrics not showing up in Netdata after SDK setup?▼

OTLP metrics may not show up in Netdata if the gRPC endpoint is not correctly set to port 4317, or if required resource attributes like service.name are missing. Ensure tracing export is explicitly disabled since Netdata only accepts metrics and logs.

Related Skills

Explore More Software Engineering Skills→
netdatanetdata
1

netdata-migration

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

Official
Intermediate
netdatanetdata
1

netdata-collector-config

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

Official
Intermediate
signalfxsignalfx
12

otel-instrument

Add OpenTelemetry tracing and metrics to applications via SDK and auto-instrumentation.

Official
Advanced
333-333-333333-333-333

go-observability

Configure OpenTelemetry logging, tracing, and metrics for Go services.

Community
Advanced