Query SNMP trap logs through Netdata Cloud or directly from a Netdata Agent. Use when the user asks about SNMP traps, trap journal entries, trap severities, trap categories, trap senders, deduplication summaries, decode errors, TRAP fields, TRAPVAR indexed varbind fields, TRAPJSON varbind audit data, or how to inspect…
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 alerts for most common…
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…
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…
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 any language via the…
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 and logs via OTLP gRPC to Netdata. Traces are not yet supported by Netdata; use an…
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 local…
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.
Use when enabling the Netdata otel.plugin, writing /etc/netdata/otel.yaml, defining metric-to-chart mappings, configuring TLS on the OTLP receiver, or debugging OTLP ingestion issues with Netdata. Covers OTLP gRPC ingestion for metrics (v2.7.0+) and logs (v2.9.0+). Traces are not yet supported.
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 the Netdata…
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 duration, applies…
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 in-progress count…
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 remediation.
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 (coordinator), applies…
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.
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 and progress, insert…
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.
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 recommends…
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 remediation.