Configure Netdata's otel-plugin to ingest OTLP/gRPC metrics and logs.
npx skills add https://github.com/netdata/skills --skill netdata-otel-setup
Please help me install this Agent Skill. Skill: netdata-otel-setup Source: https://github.com/netdata/skills/tree/main/skills/netdata-otel-setup Command: npx skills add https://github.com/netdata/skills --skill netdata-otel-setup
It helps you configure Netdata to receive OpenTelemetry data over OTLP/gRPC and get it correctly mapped into usable charts and logs instead of failing to ingest or appearing generic.
otel-plugin so collectors and SDKs can connect to the correct endpoint.otel.yaml: Set the OTLP bind address, troubleshoot connectivity, and enable TLS (including mTLS with a client CA)./etc/netdata/otel.d/v1/metrics/ so dimensions and chart shapes are meaningful; logs are ingested via the journal.store_otlp_json) to pinpoint where data is being dropped or misrendered.Use netdata-otel-setup to configure /etc/netdata/otel.yaml for OTLP/gRPC ingestion and add metric mappings so your OTLP metrics render with proper chart dimensions.
High-intent search queries and answers about installing and using this skill.
To ingest OTLP metrics and logs into Netdata, enable the built-in `otel-plugin` and edit the `/etc/netdata/otel.yaml` configuration file to set the OTLP/gRPC bind address. You must also add metric mapping files under `/etc/netdata/otel.d/v1/metrics/` to properly render chart dimensions.
Secure OpenTelemetry ingestion in Netdata by applying TLS or mTLS settings within the `otel.yaml` configuration. You can configure the server certificate and enable mutual TLS by specifying a client CA to authenticate collectors and SDKs connecting to the OTLP/gRPC receiver endpoint.
Netdata does not support OpenTelemetry traces via the OTLP receiver. The `otel-plugin` supports Linux-only OTLP/gRPC reception for metrics starting at Netdata v2.7.0+ and logs at v2.9.0+, but trace ingestion is currently unsupported.
OpenTelemetry metrics appear as generic charts in Netdata when metric-to-chart mappings are missing. To resolve this, create specific metric mapping files under the `/etc/netdata/otel.d/v1/metrics/` directory so the dimensions and chart shapes are meaningful on the dashboard.
The best way to troubleshoot dropped OpenTelemetry data in Netdata is to use the built-in troubleshooting workflow and enable the optional `store_otlp_json` log payload capture. This helps pinpoint where ingestion fails or data is misrendered before reaching the dashboard.
Yes, you can use environment variable overrides to configure the Netdata OTLP receiver. When editing `/etc/netdata/otel.yaml` or `/opt/netdata/etc/netdata/otel.yaml`, optional environment variables can be applied to manage endpoint binding and connectivity settings dynamically.
netdataConfigure OpenTelemetry Collector pipelines to export OTLP/gRPC telemetry to Netdata.
fmindConfigure ML observability with MLflow, Evidently, and SHAP for drift detection and alerting.
ccfosCreate alert subscription rules in Nightingale using severity, tags, and business groups.
kmshihab7878Monitor containerized Python services on AWS EKS with Grafana, Prometheus, Loki, and OpenTelemetry.