netdata-instrumentation

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."