From netdata-skills
Use when building or modifying an OpenTelemetry Collector pipeline that forwards telemetry to Netdata. Covers receivers, processors, exporters, and three deployment patterns (DaemonSet, gateway, and OpenTelemetry Operator). Teaches how to shape chart dimensions via an OTLP attribute plus a mapping file, since Netdata does not expose producer-driven annotations for chart layout.
How this skill is triggered — by the user, by Claude, or both
Slash command
/netdata-skills:netdata-collector-configThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill builds an OpenTelemetry Collector pipeline whose exporter
This skill builds an OpenTelemetry Collector pipeline whose exporter is a Netdata Agent or Parent. The Collector runs where the raw data is (node, sidecar, or gateway) and hands a cleaned OTLP stream to Netdata.
filelog receiver alongside
their application's OTLP.otlp exporter is the one to use; set protocol: grpc.tls: block. Netdata's server-side config is covered
in the otel-setup skill.OpenTelemetryCollector CRD manages the
DaemonSet or Deployment. Best when you want declarative
lifecycle.resource or transform processors) and name
that attribute as dimension_attribute_key in the mapping file.
See the otel-setup skill.rules/*-deployment.md
files.otlp receiver (and any node-local receivers like
hostmetrics or filelog),memory_limiter, batch, optional
resource),otlp exporter pointing at Netdata.otlphttp exporter. Netdata
accepts gRPC only.memory_limiter before batch. Under pressure the
Collector OOMs; memory_limiter is the circuit breaker.hostmetrics without a matching mapping file on
Netdata. The stock hostmetrics-receiver.yaml mapping handles
most of these, but the Collector-side scope name must match the
mapping regex (.*hostmetricsreceiver.*cpuscraper$ etc.).Use otel/opentelemetry-collector-contrib rather than
otel/opentelemetry-collector. The contrib distribution includes
the hostmetrics, kubeletstats, k8sattributes, prometheus,
and filelog components that a Netdata-bound pipeline usually
needs. The core image omits them.
Pin to a minor version tag (for example 0.109.0) rather than
latest. Collector minor versions drop or rename components
occasionally; pinning avoids silent config breakage on a rolling
image update.
Back-of-the-envelope:
memory_limiter should be 60%-75% of the container's memory
limit. Going higher gives the GC no room.batch.send_batch_size of 8192 suits most loads. Increase only
when exporter queue latency is the bottleneck.pprof endpoint in
staging if you need a real number.On the Netdata side, use the MCP integration skill's
verify-telemetry-flow.md patterns. A specific Collector-oriented
probe:
list_metrics filtered by attribute otel.scope.name matching
".*hostmetricsreceiver.*". Return distinct scope names.
If the hostmetrics scopes do not appear, the Collector is either not running, not scraping, or not exporting successfully.
A lower-level probe hits the Collector's own telemetry. Enable it in the Collector config:
service:
telemetry:
metrics:
readers:
- pull:
exporter:
prometheus:
host: "0.0.0.0"
port: 8888
Then:
curl -s http://COLLECTOR_HOST:8888/metrics \
| grep 'otelcol_exporter_sent_'
A non-zero otelcol_exporter_sent_metric_points counter for
exporter=otlp/netdata confirms metrics left the Collector. If
that number is rising but Netdata is not seeing them, the
problem is on the Netdata receiver side; run the otel-setup
troubleshooting ladder.
For end-to-end Collector configurations tested against Netdata, consult
the Netdata OpenTelemetry Collector Cookbook.
Each recipe directory in that repo ships a complete otelcol.yaml plus
a README.md explaining the use case and any required edits.
When the cookbook covers a pattern the user is asking for, fetch the
recipe directly from the source of truth rather than reconstructing it
here. See rules/recipes.md for how to look up
the current recipe list at the moment of use and the conventions each
recipe follows.
rules/receivers.mdrules/processors.mdrules/exporters-to-netdata.mdrules/daemonset-deployment.mdrules/gateway-deployment.mdrules/otel-operator.mdrules/recipes.mdnpx claudepluginhub netdata/skills --plugin netdata-skillsSearches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.