Netdata now supports distributed tracing. In this webinar, we'll demo the new tracing capabilities for the first time: OpenTelemetry trace ingestion, the new tracing dashboard, and the UI built to let you move from a metric anomaly to the exact span that caused it. For years, teams have asked us to close the gap between infrastructure monitoring and application performance. This release does that. Netdata can now ingest traces via OTEL, correlate them with the metrics and logs you already collect, and surface them in a purpose-built interface designed for speed and clarity.

A walkthrough of monitoring a distributed fleet with Netdata, using a simulated fleet of about 1,000 devices spread across regions. We show how the whole fleet reports into a single view: per-second metrics from every node, grouping by region and by customer, a map view that colors each device by health, filtering and saved views for different teams, and an AI-assisted investigation that scans the fleet for anomalies and points to likely causes.

Modern infrastructure doesn't only live in data centers anymore. It's in retail stores, factory floors, vehicles, cell sites, kiosks, and robots, thousands of nodes across hundreds of locations, connected over links you don't control, in places your team can't easily reach. Traditional observability wasn't built for this. Centralizing every metric from every device gets expensive fast, degrades over constrained links, and goes blind exactly when a remote node needs attention most. In this webinar, we'll show how Netdata inverts the model by putting intelligence at the edge.

A look at Netdata's new NetFlow analyzer: see exactly what's flowing through your network, with no packet capture and no separate appliance.

Netdata now builds live network topology maps directly in the agent: no scheduled scans, no stale picture the next morning. In this walkthrough, we cover both sides of the new Topology view: Network device discovery (SNMP): Container & process network connections.

An alert tells you what changed. It rarely tells you why. That answer usually lives somewhere else: the pull request that shipped minutes earlier, the incident already open in PagerDuty, the runbook sitting in Confluence. Netdata AI can now reach those systems directly. Through the Model Context Protocol, it connects to the tools your team already runs and reads from them while it investigates. It pulls that context alongside the metrics, logs and anomalies Netdata detects on every node, then reasons across both.

Netdata started as a lightweight agent you install across your systems to collect and visualize metrics in real time. In this clip, we walk through how that model evolved as OpenTelemetry became the industry standard, and why logs pushed that evolution even further.

OTLP (the OpenTelemetry Protocol) gives telemetry data a common format, so it can travel from one system to another without extra massaging or remapping. In this clip, we break down how that standard applies to metrics and logs, and how that data can land directly in Netdata.

Most teams run one tool for SNMP polling, another for topology, and a third for flow analysis, then spend their time stitching the views together. This webinar shows how Netdata brings all three into a single dashboard, with 100+ vendor profiles out of the box, automatic Layer 2 topology mapping, and a flow collector that auto-detects NetFlow, IPFIX, and sFlow on a single port.

If you've standardized on OpenTelemetry (or you're heading that way), you probably know the collector gets your data out, but where it lands and how useful it is once it gets there are separate problems. Netdata now ingests both OTLP metrics and OTLP logs natively, so your OTel pipelines feed directly into the same monitoring experience as everything else in your infrastructure: same dashboards, same alerting, same query interface. No separate backends, no context switching.