netdata-skills

Plugin netdata-skills from marketplace netdata-skills in netdata/skills. Commands read from the repo's manifest — 1 month ago.

Skills (57)

• netdata-alert-migration

  Use when migrating alerting rules from VictoriaMetrics (vmalert), Prometheus, Thanos Ruler, or Mimir/Cortex to Netdata health alerts. These tools share the same Prometheus alerting-rule YAML and PromQL/MetricsQL, so the method is identical. Covers the stock-first decision (Netdata already ships aler

• netdata-collector-config

  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 f

• netdata-config-from-requirements

  Use when a customer or prospect has sent a written requirements document, architecture brief, or RFP and the deliverable is a config bundle (Netdata otel.yaml, OpenTelemetry Collector pipelines, per-language instrumentation handoff, verification playbook) that the customer applies themselves. Unlike

• netdata-custom-collector

  Use when you need Netdata to collect metrics from something it does not already monitor, such as a custom application, an internal service, the output of a script or CLI tool, or a device. Covers the decision tree from the built-in StatsD server (zero collector code) through writing a collector in a

• netdata-instrumentation

  Use when adding OpenTelemetry instrumentation to application code that will report to Netdata. Covers SDK setup, resource attributes, auto-instrumentation, and patterns for Node.js, Python, Java, Go, .NET, Ruby, and PHP. Emits metrics, logs, and traces via OTLP gRPC to Netdata. Traces need a Netdata

• netdata-mcp-integration

  Use when an AI coding agent needs to connect to a Netdata Agent, Parent, or Netdata Cloud via MCP to verify telemetry, query live metrics, cross-reference instrumentation with infrastructure signals, or troubleshoot services. Covers Claude Code, Cursor, Codex, and Gemini CLI client configs for both

• netdata-migration

  Use when migrating observability from Datadog, New Relic, Dynatrace, or Prometheus to Netdata. Covers SDK replacement, exporter reconfiguration, Prometheus endpoint passthrough, and dashboard parity expectations.

• netdata-otel-setup

  Use when enabling the Netdata otel.plugin, writing /etc/netdata/otel.yaml, defining metric-to-chart mappings, configuring TLS on the OTLP receiver, setting log or trace retention, or debugging OTLP ingestion issues with Netdata. Covers OTLP gRPC ingestion for metrics (v2.7.0+), logs (v2.9.0+, curren

• troubleshoot-activemq

  Use when diagnosing issues with Apache ActiveMQ Classic 5.x: memory pressure cascade, store exhaustion spiral, gc pause death spiral, poison message / dlq storm, or connection/thread exhaustion. Queries Netdata via MCP for Apache ActiveMQ Classic 5.x health signals, applies the diagnostic tree from

• troubleshoot-apache-httpd

  Use when diagnosing issues with Apache HTTPD: worker exhaustion, memory exhaustion, listen queue overflow, slow backend cascade, or log disk full / pipe stall. Queries Netdata via MCP for process presence, critical-path reachability, requests per second, bytes served per second, request processing d

• troubleshoot-apache-pulsar

  Use when diagnosing issues with Apache Pulsar: availability, latency, saturation & resource utilization, or backlog & consumer health degradation. Queries Netdata via MCP for broker process health, bookie process health, bookie journal sync latency, metadata store request latency, bookie add entry i

• troubleshoot-bind-dns

  Use when diagnosing issues with BIND DNS: recursive client exhaustion, cache pressure spiral, upstream dependency failure, udp packet drops, or zone staleness cascade. Queries Netdata via MCP for BIND DNS health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends

• troubleshoot-cassandra

  Use when diagnosing issues with Apache Cassandra: gc death spiral, compaction death spiral, tombstone storm, disk space exhaustion, or hint overflow. Queries Netdata via MCP for node liveness (failure detector), native transport active, client request rate (read/write), client request latency (coord

• troubleshoot-ceph

  Use when diagnosing issues with Ceph: capacity exhaustion, stuck pgs, slow requests, mon quorum loss, or osd flapping. Queries Netdata via MCP for Ceph health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediation.

• troubleshoot-clickhouse

  Use when diagnosing issues with ClickHouse: merge debt spiral, memory exhaustion, replication lag cascade, zookeeper/keeper saturation, or disk space collapse. Queries Netdata via MCP for server process liveness, replicated table read/write availability, active part count per table, merge activity a

• troubleshoot-cockroachdb

  Use when diagnosing issues with Cockroachdb: lsm compaction death spiral, raft liveness failure, clock skew crisis, hot range, or intent accumulation. Queries Netdata via MCP for Cockroachdb health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediation.

• troubleshoot-consul

  Use when diagnosing issues with Consul: leader instability, gossip partition / flapping, catalog bloat / memory exhaustion, blocking query accumulation, or certificate/ca failures. Queries Netdata via MCP for Consul health signals, applies the diagnostic tree from the Netdata operator playbook, and

• troubleshoot-coredns

  Use when diagnosing issues with CoreDNS: upstream black hole, cache collapse (thundering herd), kubernetes api disconnect, memory blowout, or forwarding loop. Queries Netdata via MCP for CoreDNS health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediatio

• troubleshoot-docker-engine

  Use when diagnosing issues with Docker Engine: Docker Engine operational issues. Queries Netdata via MCP for Docker Engine health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediation.

• troubleshoot-docker

  Use when diagnosing issues with Docker: disk exhaustion, oom cascade, daemon hang/lockup, log explosion, or network isolation failure. Queries Netdata via MCP for Docker health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediation.

• troubleshoot-elasticsearch

  Use when diagnosing issues with Elasticsearch: heap pressure death spiral, shard overallocation, disk watermark cascade, mapping explosion, or merge storms. Queries Netdata via MCP for Elasticsearch health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remedi

• troubleshoot-envoy

  Use when diagnosing issues with Envoy: connection pool exhaustion cascade, memory pressure spiral, xds control plane disconnect, retry amplification, or stats cardinality explosion. Queries Netdata via MCP for server state, upstream host health, upstream request rate, downstream request rate, upstre

• troubleshoot-fluentd

  Use when diagnosing issues with Fluentd: buffer saturation (backpressure), retry storm, memory bloat / oom, poison pill crash loop, or silent data loss. Queries Netdata via MCP for fluentd process alive, monitor agent api responsiveness, input emit records rate, output emit records rate, cumulative

• troubleshoot-haproxy

  Use when diagnosing issues with HAProxy: connection saturation, backend collapse, tls resource exhaustion, buffer starvation, or reload storms. Queries Netdata via MCP for process liveness, backend server health status, frontend session rate, http request rate, queue time (qtime), applies the diagno

• troubleshoot-kafka

  Use when diagnosing issues with Kafka: \"the isr shrinks\", \"the partition goes leaderless\", \"the consumer falls behind\", \"the controller is overwhelmed\", or \"the broker runs out of disk\". Queries Netdata via MCP for Kafka health signals, applies the diagnostic tree from the Netdata operator

• troubleshoot-kubernetes-api-server

  Use when diagnosing issues with Kubernetes API Server: the webhook stall, the list storm, the etcd latency cascade, the memory cliff, or the rbac/auth slow bleed. Queries Netdata via MCP for Kubernetes API Server health signals, applies the diagnostic tree from the Netdata operator playbook, and rec

• troubleshoot-kubernetes-cluster-state

  Use when diagnosing issues with Kubernetes Cluster State: control plane unavailable, control plane slow, reconciliation stall, node failures, or admission blockage. Queries Netdata via MCP for api server health, etcd leader existence, api server request latency (p99), etcd wal fsync latency, etcd le

• troubleshoot-kubernetes-kube-proxy

  Use when diagnosing issues with Kubernetes Kube Proxy: \"stale rules / zombie watch\", \"conntrack table full\", \"sync loop storm\", \"iptables lock starvation\", or \"silent conntrack leak\". Queries Netdata via MCP for Kubernetes Kube Proxy health signals, applies the diagnostic tree from the Net

• troubleshoot-kubernetes-kubelet

  Use when diagnosing issues with Kubernetes Kubelet: pleg stall, resource pressure cascade, api server disconnection, volume mount stuck, or silent new-pod outage. Queries Netdata via MCP for Kubernetes Kubelet health signals, applies the diagnostic tree from the Netdata operator playbook, and recomm

• troubleshoot-logstash

  Use when diagnosing issues with Logstash: Logstash operational issues. Queries Netdata via MCP for Logstash health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediation.

• troubleshoot-lvm

  Use when diagnosing issues with LVM (Linux Logical Volume Manager): space exhaustion, device loss, silent redundancy loss, metadata corruption, or snapshot collapse. Queries Netdata via MCP for physical volume accessibility, lv activation state, volume group free space, thin pool data usage, mirror/

• troubleshoot-memcached

  Use when diagnosing issues with Memcached: availability, throughput, hit rate & efficiency, or connections degradation. Queries Netdata via MCP for process liveness, unexpected restart (uptime reset), command rates (cmd_get, cmd_set, cmd_touch), flush all events (cmd_flush), cache hit ratio, applies

• troubleshoot-microsoft-sql-server

  Use when diagnosing issues with Microsoft SQL Server: log full / disk full, memory pressure spiral, worker thread exhaustion, tempdb contention, or blocking cascade. Queries Netdata via MCP for Microsoft SQL Server health signals, applies the diagnostic tree from the Netdata operator playbook, and r

• troubleshoot-mongodb

  Use when diagnosing issues with MongoDB: cache pressure cascade, oplog window collapse, connection storm spiral, checkpoint stall write freeze, or silent index regression. Queries Netdata via MCP for MongoDB health signals, applies the diagnostic tree from the Netdata operator playbook, and recommen

• troubleshoot-mysql

  Use when diagnosing issues with MySQL: redo log stall, connection exhaustion, purge lag explosion, metadata lock cascade, or replication lag spiral. Queries Netdata via MCP for mysql server availability, connection utilization, query throughput (questions), slow query rate, active execution queue (t

• troubleshoot-nats

  Use when diagnosing issues with NATS: slow consumer cascade, file descriptor exhaustion, jetstream raft instability, memory pressure / oom, or silent message loss (core nats). Queries Netdata via MCP for NATS health signals, applies the diagnostic tree from the Netdata operator playbook, and recomme

• troubleshoot-nginx

  Use when diagnosing issues with nginx: connection exhaustion, file descriptor exhaustion, backend cascade failure, buffer spill to disk, or ssl cpu saturation. Queries Netdata via MCP for worker process count, stub status endpoint availability, requests per second, active connections, request proces

• troubleshoot-nvidia-dcgm

  Use when diagnosing issues with NVIDIA DCGM: hbm degradation, thermal runaway/throttling, nvlink errors, gpu hang (xid 13/31/43/79), or silent performance degradation. Queries Netdata via MCP for NVIDIA DCGM health signals, applies the diagnostic tree from the Netdata operator playbook, and recommen

• troubleshoot-nvidia-gpu

  Use when diagnosing issues with Nvidia Gpu: memory exhaustion (oom), thermal runaway then throttling cascade, silent hardware degradation, interconnect degradation (straggler), or gpu hang / fallen off bus. Queries Netdata via MCP for gpu reachability (driver communication), management path latency

• troubleshoot-nvme

  Use when diagnosing issues with NVMe: availability, health & critical warnings, errors, or endurance & wear degradation. Queries Netdata via MCP for controller state, smart critical warning; read-only mode (bit 3), smart critical warning; nvm subsystem reliability degraded (bit 2), media and data in

• troubleshoot-oracle-database

  Use when diagnosing issues with Oracle Database: \"lgwr can't keep up\", \"archive destination full\", \"space exhaustion\", \"lock contention cascade\", or \"parse storm\". Queries Netdata via MCP for Oracle Database health signals, applies the diagnostic tree from the Netdata operator playbook, an

• troubleshoot-pgbouncer

  Use when diagnosing issues with PgBouncer: pool exhaustion, client connection limit, file descriptor exhaustion, backend unreachable, or pool mode mismatch. Queries Netdata via MCP for PgBouncer health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediatio

• troubleshoot-php-fpm

  Use when diagnosing issues with PHP-FPM: worker exhaustion, slow request cascade, memory leak spiral, socket backlog overflow, or session lock serialization. Queries Netdata via MCP for service liveness (ping/health check), listen queue depth, active worker count, slow requests, per-worker request d

• troubleshoot-postfix

  Use when diagnosing issues with Postfix: availability domain, throughput domain, latency domain, or errors domain degradation. Queries Netdata via MCP for postfix master daemon running, smtp listener port accessibility, messages received per minute, messages delivered per minute, queue dwell time (a

• troubleshoot-postgresql

  Use when diagnosing issues with PostgreSQL: connection exhaustion, lock contention cascade, autovacuum starvation / bloat spiral, transaction id wraparound emergency, or checkpoint storms. Queries Netdata via MCP for process liveness, recovery state, transaction rate (commits and rollbacks), row ope

• troubleshoot-proxysql

  Use when diagnosing issues with Proxysql: backend connection starvation, multiplexing collapse, monitor false decisions, query rule cpu overload, or configuration drift. Queries Netdata via MCP for backend server health status, monitor health check results, backend connection pool usage, client conn

• troubleshoot-rabbitmq

  Use when diagnosing issues with RabbitMQ: availability, resource alarms, throttling & backpressure, or throughput degradation. Queries Netdata via MCP for node availability status, network partition status, memory alarm status, disk free alarm status, connection flow control state, applies the diagn

• troubleshoot-redis

  Use when diagnosing issues with Redis: the fork/cow storm, the event loop wedge, the replication backlog overflow, the memory pressure spiral, or the connection exhaustion cascade. Queries Netdata via MCP for redis reachability, uptime and unexpected restarts, memory usage ratio, memory fragmentatio

• troubleshoot-smartctl-disk-monitoring

  Use when diagnosing issues with smartctl (S.M.A.R.T. Disk Health): gradual media degradation, sudden mechanical failure, ssd wear-out cliff, interface/transport failure, or thermal damage. Queries Netdata via MCP for smartctl (S.M.A.R.T. Disk Health) health signals, applies the diagnostic tree from

• troubleshoot-tomcat

  Use when diagnosing issues with Apache Tomcat: thread pool exhaustion, heap exhaustion / gc death spiral, classloader leak on redeploy, stuck threads, or connection saturation. Queries Netdata via MCP for thread pool utilization, jvm process alive, request throughput, bytes sent/received rate, reque

• troubleshoot-traefik

  Use when diagnosing issues with Traefik: Traefik operational issues. Queries Netdata via MCP for Traefik health signals, applies the diagnostic tree from the Netdata operator playbook, and recommends remediation.

• troubleshoot-uwsgi

  Use when diagnosing issues with Uwsgi: worker exhaustion, harakiri storm, memory creep, stuck workers, or reload failure. Queries Netdata via MCP for accepting worker count, worker busy ratio, request throughput (delta requests), average response time (avg_rt), worker running time, applies the diagn

• troubleshoot-varnish

  Use when diagnosing issues with Varnish Cache: thread pool exhaustion, cache stampede (thundering herd), ban list explosion, storage exhaustion, or workspace overflow. Queries Netdata via MCP for session and request drop rate, backend health state, cache hit ratio, backend request rate, thread pool

• troubleshoot-vmware-vcsa

  Use when diagnosing issues with VMware vCenter Server Appliance (vCSA): certificate expiry cascade, disk space exhaustion on a specific partition, database bloat / stats table growth, vpxd memory exhaustion / crash loop, or service dependency deadlock. Queries Netdata via MCP for VMware vCenter Serv

• troubleshoot-vmware-vsphere

  Use when diagnosing issues with VMware vSphere: cpu starvation, memory pressure cascade, storage latency cliff, numa penalty, or snapshot accumulation. Queries Netdata via MCP for cpu ready time (per vm), cpu co-stop (per vm), memory balloon (per vm and host), host swap activity (vmkernel-level swap

• troubleshoot-zfs

  Use when diagnosing issues with Zfs: pool state degradation, capacity-fragmentation cliff, txg sync hang, arc memory starvation, or silent data corruption. Queries Netdata via MCP for pool health state, per-vdev state and error counts (data-bearing vdevs), pool i/o operations and bandwidth, pool i/o

• troubleshoot-zookeeper

  Use when diagnosing issues with Apache ZooKeeper: quorum loss, write pipeline stall, gc pause cascade, session expiration storm, or heap exhaustion / oom. Queries Netdata via MCP for server state (role), service liveness, request latency (aggregated), write latency (update latency), outstanding requ

Similar plugins