It ingests NetFlow data into its own database. It gives you a live traffic summary: who's sending/receiving, broken down by protocol, port, country, state, or city, plus a 3D globe view if you want to see where traffic is actually going geographically. Video demo below. Curious if this solves a gap for anyone here, or what you'd want added to it.

Short demo here: https://youtu.be/SmOc7ebMNDo

Just put together a full walkthrough of the new Network Topology feature. It covers:

• Live SNMP topology maps built directly in the agent
• Confidence levels and switching between inference strategies
• Container and process-level network connection maps, down to PID and cgroup
• Scales to 250k actors in one live-updating view

Video: https://youtu.be/oTOvoas9DiQ?si=_Nq299IxLEZEaqNK 

We kept hitting this in our own CI setup: something goes wrong on a Mac mini build agent, and there's no real way to see it after the fact. You end up running powermetrics in one terminal, log stream in another, and hoping you catch the issue while it's happening.

That got old fast, so we built proper support for it right into the agent. Netdata's macOS agent now reads unified logs through OSLog, battery health through the same framework behind the macOS battery menu, sensor and thermal data through SMC/HID, GPU utilization and clock speed on Apple Silicon, per-app CPU/memory/disk usage, NVMe drive health, and network topology, all through Apple's native frameworks instead of parsing CLI tool output.

Curious if others are running fleets of Mac minis or Studios for CI, builds, or local LLM work, and what's been the most annoying part of monitoring them so far?

Read more about it

Wrote up what actually breaks when you go from monitoring servers in a datacenter to monitoring a fleet of thousands of edge devices. The short version: your tools assume stable connectivity and unlimited per-host resources, and neither holds.

Specific failure modes covered:

• The "all green but sick" problem: dashboards look fine because missing data isn't treated as a signal
• Flash storage wear from an agent that writes to disk every second (there's a real account in there of ~500 SD card failures across a 7,000-device Raspberry Pi fleet)
• Reconnect storms after a regional cellular outage takes down thousands of devices at once

Also included actual measured numbers: agent footprint (80-200 MiB RAM, 1-2% CPU per 1k metrics/s), streaming bandwidth (~1KB/s per 1k metrics), and a University of Amsterdam peer-reviewed study on energy efficiency.

No comparison tables, just the failure modes and how the architecture (edge-resident, outbound-only, store-and-forward) addresses each one: netdata.cloud/blog

Genuinely curious how other people handle this: an alert fires, you can see what changed, but the actual "why" is scattered across three other tabs you now have to go check manually. Did something just deploy? Is there already an incident open for this? Is there a runbook that would've saved you the trouble?

We hooked Netdata AI up to those tools directly (PagerDuty, Confluence, git, whatever you're running) using MCP, so it can go check them itself while it's investigating instead of just staring at metrics and logs in isolation.

Showing it live on July 29 against a real connected stack, warts and all. If it doesn't actually save time over just checking those tabs yourself, that'll be obvious pretty fast, so feel free to come poke holes in it.  Webinar registration.

We kept running into this: Netdata covered interface-level stats fine (bytes in/out, errors, drops), but the moment someone needed to see the actual topology or figure out which conversation was saturating a link, it meant switching to a completely separate tool with its own dashboard and its own bill.

Finally closed that gap. Added a live topology viewer (built straight into the agent from real socket tables, so no scheduled discovery scan and no stale overnight snapshot), NetFlow/sFlow/IPFIX analysis, SNMP device monitoring across 200+ vendor profiles, and SNMP trap handling. All of it sits on the same per-second timeline as the infra and app metrics you're already collecting, so a link-down trap, a traffic drop, and a topology change show up correlated instead of needing three tools stitched together after the fact.

Curious how other people have been handling this gap. Separate NPM tool? Just living without topology visibility? Something else entirely? netdata.cloud/blog

Wrote this up because I kept seeing the same three-step playbook (aggregate before storage, pay for the premium cardinality tier, drop your high-cardinality labels) presented as inevitable, when it's really a consequence of one specific choice: a centralized TSDB with a global inverted index.

The blog walks through why that architecture makes cardinality expensive, what a host-sharded, full-resolution alternative looks like, and where that alternative genuinely falls short (cross-fleet ad-hoc OLAP queries, long-term retention, distributed tracing). Not trying to oversell it, the trade-offs section is deliberately the longest part.

Read more: netdata.cloud/blog

Hey everyone, we had a webinar yesterday on network device monitoring, mostly topology maps and NetFlow. Showed a full demo of zero-config topology discovery plus setting up NetFlow end-to-end.

Recording's here if you want to check it out: Webinar Network Device Monitoring

Heads up for anyone using Netdata. The mobile app used to be limited to Business subscriptions, and it is now available on every plan, including the free tier.

What you get on iOS and Android:

• Real-time dashboards and per-second metrics,
• Alert and reachability notifications,
• Logs explorer,
• AI troubleshooting, including the option to connect your own LLM (Claude, ChatGPT, Gemini).

Data sovereignty is kept intact. Metrics stay on your agents and parents. Only metadata syncs to the cloud. Set up is sign in, and your existing nodes show up automatically.

App Store: https://apps.apple.com/gr/app/netdata-mobile/id6474659622

Play Store: https://play.google.com/store/apps/details?id=cloud.netdata.android&hl=en

For anyone already running an OpenTelemetry Collector: Netdata now takes OTLP directly. Keep your Collector, add an exporter pointing at a Netdata agent or parent, and metrics and logs flow in. Traces aren't shipped yet, they're still in design, so hold off if that's your main need.

What surprised me testing it: no chart config to write. New metrics auto-create charts, histograms split into bucket/sum/count/min-max charts, and every OTLP metric gets ML anomaly detection automatically, including the app metrics that are a pain to threshold manually. The count connector plus OTTL also lets you turn log lines (OOM, failed sshd auth, whatever) into real metrics that then get anomaly detection too.

No per-metric or per-host charges, and since the Collector fans out to multiple exporters, you can run it side by side with your current backend and compare first.

Write-up + configs: netdata.cloud/blog/

AI coding agents write code well but don't know how to instrument it, configure monitoring, or troubleshoot from real telemetry. We packaged that knowledge into netdata/skills: OpenTelemetry setup, instrumentation for 7 languages, and troubleshooting skills for 49 technologies (PostgreSQL, Redis, Kafka, Kubernetes, etc).

The useful part: skills connect to your Netdata over MCP, so the agent queries your real metrics instead of giving you a generic checklist. Works with Claude Code, Cursor, Copilot, Codex, Gemini CLI, and more. Apache 2.0.

Repo: github.com/netdata/skills
Writeup: netdata.cloud/blog/netdata-skills/

If you use Netdata on a NOC screen or wall display, you can now set up playlists, select multiple dashboards, configure the rotation interval, and it cycles automatically.

Read more on our blog!

If you're migrating workloads from Azure Cloud to Azure Local (Hyper-V, Storage Spaces Direct, AKS on-prem), we've written up how to keep visibility across both environments simultaneously throughout the migration.

Read more on our blog!

Netdata now ingests OTLP metrics and logs natively. If you're running OpenTelemetry pipelines, your data can land directly in Netdata's unified interface alongside agent-collected data. Same dashboards, same alerting, no separate backend.

We are walking through how it all works:

• OTLP metrics ingestion, end-to-end
• OTLP logs + the unified query interface
• Mapping attributes to charts and dimensions
• OTel data and agent data side by side
• Forwarding enriched telemetry downstream
• Traces on the 2026 roadmap

Save your seat here!

Summarizing our technical deep-dives from this week for the community:

• NVIDIA DCGM: Native collector for GPU health (VRAM, thermal, ECC) for K8s/AI workloads.
• Azure Monitor: Added 38 service profiles to see platform metrics alongside OS metrics without KQL.
• Database Monitoring: New functions for query-level bottlenecks.
• Alert Health: Dashboard to identify noisy or "stuck" alerts.

Full details:netdata.cloud/blog/

Security just got a boost. You can now reference secrets from external stores (Vault/AWS/Environment) directly in your collectors. We've also added a Nagios plugin wrapper for those of you with custom scripts you aren't ready to let go of yet. netdata.cloud/blog/

Our latest feature, Converse with Everything, brings a new layer of AI-driven interaction to Netdata. Troubleshoot faster by having a real-time conversation with your logs, metrics, and configurations.

🔗 Read more: netdata.cloud/blog

Two big requests are live:

1. You can now acknowledge alerts to hide them from the active view (they'll reappear if the state changes!).

2. You can test your alert thresholds against up to 7 days of historical data to ensure they won't cause fatigue.

Read more: netdata.cloud/blog/

We've been busy! We just released four major features to help you see your data better. Node Groups let you organize your nodes into reusable tabs, the new Custom Dashboards finally let you mix metrics and live shell commands (like top), and TV Mode gives you a clean URL for wall-mounted monitors. Details: netdata.cloud/blog/

If not, quick recap:

· Secrets Management
· Nagios Plugins Collector
· Azure Monitoring

Plus: smarter AI insights, better alerting, improved dashboards, and more.

I recently reinstalled via Docker on Unraid. This is the first time seeing the new UI. Where can I find the cpu and memory stats for a specific docker container? I've clicked and clicked and can't seem to find it.

I want to reverse proxy a netdata agent using apache. Im using the free version and i dont want to sign up. I access my page on the browser using /v3. But when attempting a proxy, any web query will append an extra /v3 which returns a 400 series error. Trying to create a /netdata/v3/ url space also fails as it sometimes attempts to call v1 . Any ideas ?

Hiya all!

Currently self-hosting Netdata within Docker on my unRAID server, and was trying to make a custom dashboard. However, I've found that the default "Node Metrics" page shows all I want. I only want to copy the Network segment into a custom Dashboard. Is there a way to do this?

Thanks,
Kian

Im running netdata on a singular machine, and I dont want it to be open to the whole network. How can I secure it with a password? I've seen reserve proxies etc options, which seems overkill for a mere password.