# Netdata

Recent content in Blog on Netdata

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Distributed Tracing in Netdata: OpenTelemetry Traces, Stored Where They Were Collected

DevFeed: [Distributed Tracing in Netdata: OpenTelemetry Traces, Stored Where They Were Collected](<https://devfeed.tech/articles/distributed-tracing-in-netdata-opentelemetry-traces-stored-where-they-were-collected-65643.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/distributed-tracing-in-netdata/>)

Published: 2026-10-05T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [tracing](<https://devfeed.tech/topics/tracing.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collector](<https://devfeed.tech/tags/collector.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>)

### AI overview

Netdata introduces distributed tracing through OpenTelemetry. Its Agent receives, stores, and indexes traces locally, while Netdata Cloud provides charts and trace exploration. The article explains OTLP/gRPC setup, retention and security options, and current limitations, including no service maps, code profiling, or native Jaeger and Zipkin ingestion.

### Source excerpt

Back in 2020, when we laid out where Netdata was going, the plan listed anomaly detection, log collection and "application traces collection". The first two shipped years ago. Traces took longer, because we wanted them to work the way the rest of Netdata works: collected and stored on your own nodes, with no separate backend to stand up. Distributed tracing is now available in Netdata. The same Agent that receives your OpenTelemetry metrics and logs now receives, stores and indexes OpenTelemetry traces, and the new Traces tab in Netdata Cloud lets you go from a latency distribution to a single slow span in a few clicks.

## Who Built This Dashboard, and Are They Still Here?

DevFeed: [Who Built This Dashboard, and Are They Still Here?](<https://devfeed.tech/articles/who-built-this-dashboard-and-are-they-still-here-64998.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/server-monitoring-dashboard-you-never-built/>)

Published: 2026-10-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

### AI overview

The article argues that hand-built infrastructure monitoring dashboards create ongoing maintenance work and can leave teams without clear ownership during incidents. It presents Netdata's approach of structuring metrics at collection time so dashboards can be generated automatically, and describes built-in anomaly detection and integrations. The article also contrasts that approach with AI tools that generate dashboard panels, arguing that automation should help investigate incidents instead.

### Source excerpt

You have lived it, no? When production is down, and you have that chart that says something really strange and peculiar, and nobody knows who did it or when. Production is bleeding. There is a spike on screen. And the chart answers everything except the question you actually have: who built this panel, what did they mean by it, and are they still here? Ask the room and you get what one sysadmin got: "When I asked who is actually monitoring the dashboard... there was silence." (r/sysadmin) Ask the industry and you get the pattern one SRE described: the two people who understood the dashboards left the company, and the monitoring stack went with them. Another SRE, from a 1,000-person company: "the 2 guys looking after the LGTM stack left..." (r/sre) And after the page fires, the clock everyone knows starts: "We'd lose 10-15 minutes just getting oriented." (r/sre)

## Introducing Infrastructure Knowledge: Teach Netdata AI What Your Metrics Can't Show

DevFeed: [Introducing Infrastructure Knowledge: Teach Netdata AI What Your Metrics Can't Show](<https://devfeed.tech/articles/introducing-infrastructure-knowledge-teach-netdata-ai-what-your-metrics-can-t-show-44932.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/infrastructure-knowledge/>)

Published: 2026-09-08T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [context](<https://devfeed.tech/topics/context.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [change](<https://devfeed.tech/tags/change.md>), [environment](<https://devfeed.tech/tags/environment.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [it-infrastructure](<https://devfeed.tech/tags/it-infrastructure.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [migrations](<https://devfeed.tech/tags/migrations.md>), [services](<https://devfeed.tech/tags/services.md>)

### AI overview

Netdata introduces Infrastructure Knowledge, a shared Markdown context document and AI Memory for teaching Netdata AI about service importance, expected infrastructure behavior, ownership, business context, maintenance, and architecture. This context is used in conversations, investigations, and reports to improve interpretation of metrics and alerts.

### Source excerpt

Netdata AI sees everything your infrastructure does: every metric, every anomaly, every alert. It does not see what your infrastructure is: which services matter, which host is supposed to run hot, who owns what, what your team considers normal. Without that context, "CPU at 91%" is just a finding. With it, it might be a machine doing exactly its job. Two places to put it Infrastructure Knowledge holds that context. The more you tell Netdata AI about your environment, the more accurate its answers get.

## Chart Annotations: Pin the Deploy, the Incident, or the Config Change Right on the Chart

DevFeed: [Chart Annotations: Pin the Deploy, the Incident, or the Config Change Right on the Chart](<https://devfeed.tech/articles/chart-annotations-pin-the-deploy-the-incident-or-the-config-change-right-on-the-chart-44888.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/chart-annotations/>)

Published: 2026-08-17T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [dashboards](<https://devfeed.tech/topics/dashboards.md>), [context](<https://devfeed.tech/topics/context.md>), [incident](<https://devfeed.tech/topics/incident.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [cause](<https://devfeed.tech/tags/cause.md>), [color](<https://devfeed.tech/tags/color.md>), [context](<https://devfeed.tech/tags/context.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [incident](<https://devfeed.tech/tags/incident.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [slack](<https://devfeed.tech/tags/slack.md>)

### AI overview

The article explains how chart annotations in Netdata Cloud add persistent context to metrics by marking deployments, incidents, configuration changes, and maintenance windows directly on charts. Annotations can be scoped to a chart, shared globally, or temporarily synchronized across visible charts, and can support metric correlation and dashboard sharing.

### Source excerpt

A chart shows you that CPU jumped at 15:57. It doesn't show you that a deploy went out at 15:56. Chart annotations let you pin a note to the exact moment on a chart, and it stays there for everyone in your Space, permanently, the next time anyone looks at that chart. Pin a note to a moment Deployments, incidents, config changes, maintenance windows: these events explain the shape of your metrics, but they usually live somewhere your dashboard can't see, like a deploy log, a ticket, or a Slack thread someone will eventually delete. Chart annotations put that context on the chart itself, so you don't have to cross-reference a separate system by hand.

## Introducing MCP Connections: Netdata AI Now Reads From the Tools You Already Run

DevFeed: [Introducing MCP Connections: Netdata AI Now Reads From the Tools You Already Run](<https://devfeed.tech/articles/introducing-mcp-connections-netdata-ai-now-reads-from-the-tools-you-already-run-44968.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/netdata-ai-mcp-connections/>)

Published: 2026-08-03T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [github](<https://devfeed.tech/tags/github.md>), [incident](<https://devfeed.tech/tags/incident.md>), [latency](<https://devfeed.tech/tags/latency.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-connections](<https://devfeed.tech/tags/mcp-connections.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>)

### AI overview

Netdata introduces MCP Connections, allowing Netdata AI to act as an MCP client that reads context from GitHub, PagerDuty, Atlassian Cloud, and custom HTTPS MCP servers during monitoring investigations. The feature correlates metrics and anomalies with deployments, incidents, pull requests, and runbooks.

### Source excerpt

Netdata AI can now connect outward to the tools your team already runs, like GitHub, PagerDuty, Atlassian, or any custom MCP server, and read from them during an investigation. We call this MCP Connections. It's the missing piece in the middle of every root-cause investigation: the alert tells you what changed, but the why is usually somewhere else entirely. The missing context A latency spike fires an alert. The metrics show exactly when it started and which service it hit. They don't show the deploy that went out four minutes earlier, the PagerDuty incident already open for the same symptom, or the runbook someone wrote for this exact failure mode six months ago. That context exists. It's just scattered across a pull request, a ticketing system, and a wiki page, in tools your monitoring platform has never been able to see.

## Native macOS Monitoring: Logs, Sensors, GPU & Hardware Health

DevFeed: [Native macOS Monitoring: Logs, Sensors, GPU & Hardware Health](<https://devfeed.tech/articles/native-macos-monitoring-logs-sensors-gpu-hardware-health-44947.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/macos-monitoring/>)

Published: 2026-07-15T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [logs](<https://devfeed.tech/tags/logs.md>), [macos](<https://devfeed.tech/tags/macos.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

Netdata's latest release expands macOS monitoring with logs, hardware telemetry, sensor data, GPU metrics, power and thermal readings, storage health, and network mapping. It uses Apple frameworks and bounded queries to help users investigate application and operating-system errors and detect hardware issues.

### Source excerpt

We've overhauled macOS monitoring in the latest Netdata release. Netdata already collects system metrics on Macs at per-second resolution; this release completes the picture with logs and hardware telemetry, areas that previously required users to run CLI tools like log show and powermetrics. The new collectors read this data through Apple's own frameworks, allowing users to trace application and OS errors and catch hardware issues early.

## Fleet Observability: Linux Edge Device Monitoring

DevFeed: [Fleet Observability: Linux Edge Device Monitoring](<https://devfeed.tech/articles/fleet-observability-linux-edge-device-monitoring-44908.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/fleet-observability/>)

Published: 2026-06-28T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>), [Server](<https://devfeed.tech/topics/server.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [dashboard](<https://devfeed.tech/tags/dashboard.md>), [devices](<https://devfeed.tech/tags/devices.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [iot](<https://devfeed.tech/tags/iot.md>), [linux](<https://devfeed.tech/tags/linux.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

This article explains fleet observability for thousands of distributed Linux edge devices, including the architecture, resource requirements, streaming model, energy efficiency, liveness tracking, and pricing considerations described for Netdata.

### Source excerpt

It feels less like managing devices and more like remote babysitting. You check the dashboard, everything is green, and then a customer in the field tells you a device has been down for two days. At a handful of servers, the rare failure is an event. Across thousands of distributed Linux endpoints -- robots in warehouses, EV chargers across a city, kiosks in retail, IoT gateways in the field -- the rare failure becomes a daily occurrence, and the tools built for a datacenter quietly stop telling you the truth.

## Real Time Network Monitoring: Topology, NetFlow, SNMP

DevFeed: [Real Time Network Monitoring: Topology, NetFlow, SNMP](<https://devfeed.tech/articles/real-time-network-monitoring-topology-netflow-snmp-45015.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/network-monitoring/>)

Published: 2026-06-24T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [netflow](<https://devfeed.tech/topics/netflow.md>), [Network](<https://devfeed.tech/topics/network.md>), [network device monitoring](<https://devfeed.tech/topics/network-device-monitoring.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [flat network topology](<https://devfeed.tech/topics/flat-network-topology.md>), [Network Operations Center](<https://devfeed.tech/topics/network-operations-center.md>)

Tags: [dashboard](<https://devfeed.tech/tags/dashboard.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [netflow](<https://devfeed.tech/tags/netflow.md>), [network](<https://devfeed.tech/tags/network.md>), [network-monitoring](<https://devfeed.tech/tags/network-monitoring.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [snmp](<https://devfeed.tech/tags/snmp.md>), [topology](<https://devfeed.tech/tags/topology.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

Netdata describes expanded network monitoring capabilities, including live topology maps, NetFlow and sFlow analysis, SNMP device monitoring and traps, and a dedicated dashboard integrated with its existing infrastructure, application, and container metrics.

### Source excerpt

Interface counters tell you a port is busy. Bytes in, bytes out, errors, drops. That's enough to know a link is saturated, but not enough to know which conversations are saturating it, which devices are involved, or how a problem propagates across your network. For that you've traditionally needed dedicated network performance monitoring tools, usually expensive, usually a separate console from the rest of your monitoring. Today we're closing that gap. Netdata has had solid network interface monitoring for a long time through its native collectors and SNMP support. We've now built out the rest of the picture, and it adds up to NPM-class network monitoring: live network topology, NetFlow and sFlow traffic analysis, SNMP device monitoring across 200+ vendor profiles, SNMP trap handling, and a dedicated network monitoring dashboard. All of it runs alongside the infrastructure, application, and container metrics Netdata already collects, on the same timeline, in the same platform.

## SolarWinds Price Increases 2026: What Customers Need to Know

DevFeed: [SolarWinds Price Increases 2026: What Customers Need to Know](<https://devfeed.tech/articles/solarwinds-price-increases-2026-what-customers-need-to-know-45049.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/solarwinds-price-increases-2026/>)

Published: 2026-06-23T00:00:00Z

Content type: opinion

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [solarwinds](<https://devfeed.tech/topics/solarwinds.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [acquisitions](<https://devfeed.tech/tags/acquisitions.md>), [business](<https://devfeed.tech/tags/business.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customers](<https://devfeed.tech/tags/customers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [licensing](<https://devfeed.tech/tags/licensing.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [platform](<https://devfeed.tech/tags/platform.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [solarwinds](<https://devfeed.tech/tags/solarwinds.md>), [subscriptions](<https://devfeed.tech/tags/subscriptions.md>)

### AI overview

This article examines reported SolarWinds pricing and licensing changes following its 2025 acquisition by Turn/River Capital. It discusses reported renewal increases, the shift to subscription-only licensing, multi-year commitments and escalators, and the implications for organizations evaluating monitoring alternatives.

### Source excerpt

If you're a SolarWinds customer facing renewal, you've likely noticed significant changes to pricing and licensing terms in 2024-2025. You're not alone. At Netdata, we've been speaking with dozens of SolarWinds customers who are reassessing their monitoring strategies in light of these changes. This post provides factual information about what's changed, the real impact on organizations, and a practical framework for evaluating your path forward. What's Happening with SolarWinds Pricing? In February 2025, SolarWinds was acquired by private equity firm Turn/River Capital in a $4.4 billion transaction. As is common with PE-backed acquisitions, this has led to significant changes in pricing and business terms. Based on customer reports and public information, renewal prices have increased by 100-300% for many customers. One customer on the SolarWinds community forum reported their renewal more than doubled, a 225% increase from the previous year.

## 5 Best SolarWinds Alternatives for 2026

DevFeed: [5 Best SolarWinds Alternatives for 2026](<https://devfeed.tech/articles/5-best-solarwinds-alternatives-for-2026-45048.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/solarwinds-alternatives-2026/>)

Published: 2026-06-23T00:00:00Z

Content type: comparison

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [distributed-systems](<https://devfeed.tech/topics/distributed-systems.md>), [Network](<https://devfeed.tech/topics/network.md>), [Server](<https://devfeed.tech/topics/server.md>), [Database](<https://devfeed.tech/topics/database.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [auto-scaling](<https://devfeed.tech/tags/auto-scaling.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [containerized](<https://devfeed.tech/tags/containerized.md>), [databases](<https://devfeed.tech/tags/databases.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [servers](<https://devfeed.tech/tags/servers.md>), [solarwinds](<https://devfeed.tech/tags/solarwinds.md>)

### AI overview

This comparison examines alternatives to SolarWinds for organizations modernizing monitoring across cloud-native and distributed infrastructure. It highlights SolarWinds' polling intervals, complex licensing, configuration overhead, centralized architecture, and security concerns, while describing demand for real-time visibility and predictable pricing.

### Source excerpt

As organizations modernize their infrastructure and embrace cloud-native architectures, traditional monitoring solutions are showing their age. SolarWinds, while a long-established player in IT management, was designed for an era of static, on-premise infrastructure. In 2026, teams are seeking alternatives that can keep pace with dynamic, distributed systems--and they're finding better options. What Is SolarWinds? Is It Still The Right Choice? SolarWinds Platform (formerly Orion) has been a cornerstone of IT monitoring for decades, offering comprehensive coverage of network devices, servers, applications, and databases. It's particularly strong in traditional enterprise environments with extensive hardware monitoring needs.

## High-Cardinality Metrics in Observability: Tradeoffs of Centralized Time-Series Storage

DevFeed: [High-Cardinality Metrics in Observability: Tradeoffs of Centralized Time-Series Storage](<https://devfeed.tech/articles/high-cardinality-metrics-at-scale-a-better-playbook-44916.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/high-cardinality-metrics-observability-scale/>)

Published: 2026-05-30T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Time Series](<https://devfeed.tech/topics/time-series.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [cardinality](<https://devfeed.tech/tags/cardinality.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [observability](<https://devfeed.tech/tags/observability.md>), [scale](<https://devfeed.tech/tags/scale.md>), [time-series](<https://devfeed.tech/tags/time-series.md>)

### AI overview

The article argues that the cost of high-cardinality metrics depends on centralized time-series storage architectures whose indexes scale with unique series. It describes the resulting pricing and data-retention tradeoffs and introduces an alternative approach, though the supplied excerpt does not provide its implementation details.

### Source excerpt

The "high cardinality is expensive" sentence has become observability's version of "in this economy": said so often that nobody questions whether it's true. Every vendor pricing page invokes it. Every glossary article repeats it. Every architecture diagram shows aggregation buffers placed before the storage layer. "High cardinality is expensive" is not a fact about the universe; it's a fact about one architectural choice: centralizing time-series storage and querying it through an index that scales with unique series. Once you accept that choice, everything follows. You pay per metric, you drop labels you wish you'd kept, you pre-aggregate before storage, and you discover that the bug you were debugging only existed at the full resolution you already threw away.

## Netdata Skills: Teach Your AI Coding Agent To Monitor

DevFeed: [Netdata Skills: Teach Your AI Coding Agent To Monitor](<https://devfeed.tech/articles/netdata-skills-teach-your-ai-coding-agent-to-monitor-44999.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/netdata-skills/>)

Published: 2026-05-20T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agent](<https://devfeed.tech/tags/ai-coding-agent.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [codex](<https://devfeed.tech/tags/codex.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [skills](<https://devfeed.tech/tags/skills.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

Netdata has open-sourced netdata/skills, a collection of agent skills that gives AI coding agents operational guidance for monitoring and observability work. The skills cover Netdata setup, OpenTelemetry instrumentation, collector pipelines, troubleshooting technologies, and verification through live telemetry via MCP.

### Source excerpt

There's a growing ecosystem of AI coding agents: Claude Code, Cursor, Copilot, Codex, Gemini CLI, Windsurf, and others. They're good at writing code, but they don't inherently know how to instrument that code for observability, configure monitoring infrastructure, or troubleshoot production systems using real telemetry data. That knowledge lives in documentation, runbooks, and the heads of your senior SREs. We've open-sourced a repository that encodes this knowledge into a format AI agents can use directly. netdata/skills is a collection of agent skills, published in the open agentskills.io format, that teach AI coding agents how to set up Netdata, instrument applications with OpenTelemetry, build collector pipelines, troubleshoot 49 specific technologies, and verify everything against live data via MCP.

## Using OpenTelemetry Collector with Netdata for Metrics and Logs

DevFeed: [Using OpenTelemetry Collector with Netdata for Metrics and Logs](<https://devfeed.tech/articles/opentelemetry-and-netdata-today-45020.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/opentelemetry-metrics-and-logs-ingestion/>)

Published: 2026-05-15T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [collector](<https://devfeed.tech/tags/collector.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

This article explains how to use the OpenTelemetry Collector to ingest metrics and logs through standard receivers, export them over OTLP to Netdata, and use Netdata for storage, analysis, alerting, and visualization. It also notes that trace support is coming soon.

### Source excerpt

OpenTelemetry has become the default way to instrument applications and ship telemetry. The hard part has never been the data model. It's been picking a backend that handles OTLP without quietly turning into a per-metric bill or a black box that swallows your data. Netdata is a native OTLP backend. Stand up an OpenTelemetry Collector with any of its hundreds of receivers, point its OTLP exporter at Netdata, and you get per-second charts, ML anomaly detection on every signal, AI-assisted troubleshooting, and infrastructure correlation, with no per-metric, per-series, or per-host charges. Metrics and logs work today. Trace support is coming soon.

## Dashboard Playlists: Cycle Through Dashboards in TV Mode

DevFeed: [Dashboard Playlists: Cycle Through Dashboards in TV Mode](<https://devfeed.tech/articles/dashboard-playlists-cycle-through-dashboards-in-tv-mode-44897.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/dashboard-playlists/>)

Published: 2026-05-12T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [dashboards](<https://devfeed.tech/topics/dashboards.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Network Operations Center](<https://devfeed.tech/topics/network-operations-center.md>), [incident](<https://devfeed.tech/topics/incident.md>)

Tags: [dashboard](<https://devfeed.tech/tags/dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [incident](<https://devfeed.tech/tags/incident.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [network](<https://devfeed.tech/tags/network.md>), [noc](<https://devfeed.tech/tags/noc.md>), [operational](<https://devfeed.tech/tags/operational.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

A new dashboard playlist feature lets users cycle through selected dashboards in TV mode on a configurable interval. The feature is intended for infrastructure monitoring, NOC displays, incident response, team awareness, and operational visibility.

### Source excerpt

When we shipped TV mode, we heard almost immediately: "Great, but I have five dashboards and one screen." A single dashboard on a wall display covers one view of your infrastructure. If you want to rotate between your network overview, database health, application metrics, and infrastructure summary, someone has to walk over and click, or you're buying more screens. Dashboard playlists solve this. You can now select a sequence of dashboards to cycle through in TV mode, with a configurable rotation interval. Set it up once, open the TV mode URL on your display, and the screen rotates through your chosen dashboards on its own.

## Azure Local Migration: Monitor Both Sides In One View

DevFeed: [Azure Local Migration: Monitor Both Sides In One View](<https://devfeed.tech/articles/azure-local-migration-monitor-both-sides-in-one-view-44883.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/azure-local-migration/>)

Published: 2026-05-11T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [on-prem](<https://devfeed.tech/topics/on-prem.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [hyper-v](<https://devfeed.tech/topics/hyper-v.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cost-optimization](<https://devfeed.tech/tags/cost-optimization.md>), [database](<https://devfeed.tech/tags/database.md>), [hyper-v](<https://devfeed.tech/tags/hyper-v.md>), [latency](<https://devfeed.tech/tags/latency.md>), [migration](<https://devfeed.tech/tags/migration.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [on-prem](<https://devfeed.tech/tags/on-prem.md>)

### AI overview

The article explains why organizations migrate workloads from Azure public cloud to Azure Local, citing data sovereignty, latency, cost optimization, and regulatory constraints. It focuses on the monitoring challenge of operating workloads across both environments during migration and describes Netdata's approach to viewing Azure resources and Azure Local infrastructure together.

### Source excerpt

More organizations are moving workloads from Azure public cloud to Azure Local (formerly Azure Stack HCI) than most people realize. The reasons vary: data sovereignty requirements, latency-sensitive workloads that need to be closer to the edge, cost optimization for predictable workloads where reserved cloud capacity doesn't make financial sense, or regulatory constraints that require data to stay on-premises.

## Geo Maps: See Where Your Infrastructure Lives

DevFeed: [Geo Maps: See Where Your Infrastructure Lives](<https://devfeed.tech/articles/geo-maps-see-where-your-infrastructure-lives-44913.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/geo-maps/>)

Published: 2026-05-09T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Internet of things](<https://devfeed.tech/topics/iot.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [on-prem](<https://devfeed.tech/topics/on-prem.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Azure](<https://devfeed.tech/topics/azure.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [data-centers](<https://devfeed.tech/tags/data-centers.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [incident](<https://devfeed.tech/tags/incident.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [iot](<https://devfeed.tech/tags/iot.md>), [latency](<https://devfeed.tech/tags/latency.md>), [on-prem](<https://devfeed.tech/tags/on-prem.md>)

### AI overview

Netdata introduces geographic maps for monitoring infrastructure across regions, data centers, branch offices, and edge locations. Nodes with coordinate host labels appear on an interactive OpenStreetMap-based view, helping teams investigate incidents, regional failures, capacity patterns, and latency issues.

### Source excerpt

When your infrastructure is spread across regions, data centers, branch offices, or edge locations, knowing where a node is physically located matters more than people usually admit. During an incident, "the node in the Singapore POP" communicates faster than a hostname. When you're planning capacity, seeing geographic clustering tells you something that a flat list of nodes doesn't. When a subset of your fleet starts misbehaving, the first question is often "is this regional?"

## Netdata Introduces a Native NVIDIA DCGM Collector for GPU Monitoring

DevFeed: [Netdata Introduces a Native NVIDIA DCGM Collector for GPU Monitoring](<https://devfeed.tech/articles/nvidia-dcgm-collector-deep-gpu-monitoring-for-ai-45018.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/nvidia-dcgm-monitoring/>)

Published: 2026-05-04T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [GPU](<https://devfeed.tech/topics/gpu.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Nvidia](<https://devfeed.tech/topics/nvidia.md>), [data centers](<https://devfeed.tech/topics/data-centers.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>)

Tags: [dashboards](<https://devfeed.tech/tags/dashboards.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [fields](<https://devfeed.tech/tags/fields.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [gpu-monitoring](<https://devfeed.tech/tags/gpu-monitoring.md>), [inference](<https://devfeed.tech/tags/inference.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [jobs](<https://devfeed.tech/tags/jobs.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [nvidia](<https://devfeed.tech/tags/nvidia.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

The document introduces Netdata's native collector for NVIDIA Data Center GPU Manager (DCGM). It collects extensive GPU telemetry, organizes metrics by hardware scope, and provides dashboards, alerts, anomaly detection, and troubleshooting features for production GPU workloads.

### Source excerpt

GPU infrastructure is expensive and increasingly central to production workloads. Whether you're running ML training jobs, inference serving, video transcoding, or HPC workloads, understanding what your GPUs are actually doing, and what's going wrong when performance degrades, is not optional. The problem is that NVIDIA's Data Center GPU Manager (DCGM) exposes an enormous amount of telemetry, but getting that data into a monitoring system in a useful, organized way has traditionally required significant setup and custom dashboarding work.

## Misconfigured Alert Detection: Tuning Made Easy

DevFeed: [Misconfigured Alert Detection: Tuning Made Easy](<https://devfeed.tech/articles/misconfigured-alert-detection-tuning-made-easy-44928.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/identifying-misconfigured-alerts/>)

Published: 2026-04-28T00:00:00Z

Content type: article

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [site-reliability-engineering](<https://devfeed.tech/topics/site-reliability-engineering.md>), [notifications](<https://devfeed.tech/topics/notifications.md>)

Tags: [alert](<https://devfeed.tech/tags/alert.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [detection](<https://devfeed.tech/tags/detection.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [operational](<https://devfeed.tech/tags/operational.md>), [production](<https://devfeed.tech/tags/production.md>), [staging](<https://devfeed.tech/tags/staging.md>)

### AI overview

Netdata automatically detects alerts that may be misconfigured by analyzing their recent behavior. It flags alerts that fire too often, remain raised for extended periods, stay silenced, or fire without notifications, helping teams reduce alert fatigue and restore trust in monitoring.

### Source excerpt

Netdata ships with hundreds of stock alerts. They cover a wide range of infrastructure conditions and they're designed with sensible defaults. But "sensible defaults" and "correct for your environment" are not the same thing. A CPU threshold that's perfectly reasonable for a build server might generate constant noise on a machine running batch jobs. An alert that's critical for production might be irrelevant in staging, where it fires daily and everyone ignores it.

## Azure Monitor Collector: Monitor Azure Infrastructure

DevFeed: [Azure Monitor Collector: Monitor Azure Infrastructure](<https://devfeed.tech/articles/azure-monitor-collector-monitor-azure-infrastructure-44884.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/azure-monitor/>)

Published: 2026-04-27T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [monitor](<https://devfeed.tech/topics/monitor.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes-clusters](<https://devfeed.tech/tags/kubernetes-clusters.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>)

### AI overview

Netdata introduces an alpha Azure Monitor collector that brings Azure platform metrics into the broader Netdata monitoring stack. It automatically discovers Azure resources, applies built-in metric profiles, supports multiple subscriptions, and allows filtering by resource group, region, tags, or custom Azure Resource Graph queries.

### Source excerpt

If you're running infrastructure on Azure, you've probably dealt with the split between your Azure-native monitoring and the rest of your stack. Your VMs, databases, and Kubernetes clusters generate platform metrics through Azure Monitor, but those metrics live in a separate world from the OS-level, application, and on-prem metrics you're already watching in Netdata. You end up checking two (or more) places during incidents, building mental bridges between dashboards that don't talk to each other.

## Database Performance Monitoring: 14+ DBs Supported

DevFeed: [Database Performance Monitoring: 14+ DBs Supported](<https://devfeed.tech/articles/database-performance-monitoring-14-dbs-supported-44900.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/dbm/>)

Published: 2026-04-24T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [Database](<https://devfeed.tech/topics/database.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Deadlock](<https://devfeed.tech/topics/deadlock.md>), [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>)

Tags: [dashboard](<https://devfeed.tech/tags/dashboard.md>), [database](<https://devfeed.tech/tags/database.md>), [database-performance](<https://devfeed.tech/tags/database-performance.md>), [deadlock](<https://devfeed.tech/tags/deadlock.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-monitoring](<https://devfeed.tech/tags/performance-monitoring.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [queries](<https://devfeed.tech/tags/queries.md>)

### AI overview

Netdata adds interactive query analysis to its database collectors, allowing users to inspect top queries, running operations, deadlocks, and recent errors in the dashboard across 14 databases. The feature is available as a tech preview through the standard collectors.

### Source excerpt

Netdata has always collected database metrics: connections, throughput, replication lag, buffer cache hit ratios, and so on. These tell you that something is wrong, but they don't tell you why. When your PostgreSQL response time spikes, the metric alone doesn't tell you which query is responsible. For that, you've traditionally needed to SSH into the box, connect to the database, and run diagnostic queries manually. Or set up a separate database monitoring tool entirely.

## Nagios Plugins: Run Existing Checks & Custom Scripts

DevFeed: [Nagios Plugins: Run Existing Checks & Custom Scripts](<https://devfeed.tech/articles/nagios-plugins-run-existing-checks-custom-scripts-44964.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/nagios-plugins/>)

Published: 2026-04-22T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Script](<https://devfeed.tech/topics/script.md>), [Bash](<https://devfeed.tech/topics/bash.md>), [Python](<https://devfeed.tech/topics/python.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [PowerShell](<https://devfeed.tech/topics/powershell.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [bash](<https://devfeed.tech/tags/bash.md>), [go](<https://devfeed.tech/tags/go.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [powershell](<https://devfeed.tech/tags/powershell.md>), [python](<https://devfeed.tech/tags/python.md>), [scripts](<https://devfeed.tech/tags/scripts.md>), [ssl](<https://devfeed.tech/tags/ssl.md>)

### AI overview

Netdata's Nagios plugins collector runs existing Nagios-compatible checks and custom monitoring scripts on a schedule. It tracks check states and execution metrics, converts performance data into charts, and derives alerts from warning and critical thresholds.

### Source excerpt

A lot of teams have a collection of Nagios plugins and custom monitoring scripts that have been running reliably for years. Some are standard community plugins for checking disk health or SSL certificate expiry. Others are homegrown Bash or Python scripts that check something very specific to the business: whether an API endpoint returns the right payload, whether a batch job completed on time, whether a queue depth is within bounds. These scripts work, they're battle-tested, and nobody wants to rewrite them.

## Secrets Management: Remove Credentials From Configs

DevFeed: [Secrets Management: Remove Credentials From Configs](<https://devfeed.tech/articles/secrets-management-remove-credentials-from-configs-45040.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/secrets-management/>)

Published: 2026-04-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Security](<https://devfeed.tech/topics/security.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Environment Variables](<https://devfeed.tech/topics/environment-variables.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [configs](<https://devfeed.tech/tags/configs.md>), [docker](<https://devfeed.tech/tags/docker.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [hashicorp-vault](<https://devfeed.tech/tags/hashicorp-vault.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [secrets-management](<https://devfeed.tech/tags/secrets-management.md>)

### AI overview

Netdata introduces native secrets management for collectors, allowing credentials to be resolved at runtime from environment variables, files, commands, or centralized secret stores such as HashiCorp Vault and AWS Secrets Manager.

### Source excerpt

If you're running Netdata collectors that connect to databases, APIs, or other authenticated services, there's a good chance you have passwords sitting in plain-text configuration files right now. It works, but it's the kind of thing that makes security teams nervous and makes credential rotation painful. Every password change means editing config files and restarting collectors. Netdata now supports secrets management natively. Instead of putting credentials directly in your collector configurations, you reference them using a resolver syntax, and Netdata resolves the actual values at runtime from whatever source you choose: environment variables, files on disk, the output of a command, or a centralized secret store like HashiCorp Vault or AWS Secrets Manager.

## Smarter Alerts: Test, Review & Preview Schedules

DevFeed: [Smarter Alerts: Test, Review & Preview Schedules](<https://devfeed.tech/articles/smarter-alerts-test-review-preview-schedules-45044.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/smarter-alerts/>)

Published: 2026-04-16T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [incident](<https://devfeed.tech/topics/incident.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [notifications](<https://devfeed.tech/topics/notifications.md>)

Tags: [alert](<https://devfeed.tech/tags/alert.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [exercise](<https://devfeed.tech/tags/exercise.md>), [incident](<https://devfeed.tech/tags/incident.md>), [metric](<https://devfeed.tech/tags/metric.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [production](<https://devfeed.tech/tags/production.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

Netdata introduces three alerting improvements: historical evaluation of alert definitions before deployment, a timeline of alert state transitions, and schedule previews for recurring silencing rules. The features are intended to reduce alert fatigue and support safer, data-driven tuning.

### Source excerpt

Alert fatigue usually isn't caused by one thing. It's the accumulation of thresholds that are slightly too sensitive, alerts that fire during known maintenance windows, and historical patterns that nobody has the tools to review easily. Fixing it requires better visibility into how alerts actually behave over time, and a way to test changes before they hit production. We've shipped three improvements to alerting in Netdata that address different parts of this problem: the ability to evaluate alert definitions against historical data before deploying them, a timeline view of alert transitions, and a schedule preview for recurring silencing rules.

## TV Mode: Put Your Dashboards on the Big Screen

DevFeed: [TV Mode: Put Your Dashboards on the Big Screen](<https://devfeed.tech/articles/tv-mode-put-your-dashboards-on-the-big-screen-45065.md>)

Original publisher: [Read original article](<https://www.netdata.cloud/blog/tv-mode/>)

Published: 2026-04-14T00:00:00Z

Content type: release

Language: en

Sources: [Netdata](<https://devfeed.tech/sources/blog-on-netdata.md>)

Topics: [dashboards](<https://devfeed.tech/topics/dashboards.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Network Operations Center](<https://devfeed.tech/topics/network-operations-center.md>), [monitor](<https://devfeed.tech/topics/monitor.md>)

Tags: [custom-dashboard](<https://devfeed.tech/tags/custom-dashboard.md>), [dashboards](<https://devfeed.tech/tags/dashboards.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [noc](<https://devfeed.tech/tags/noc.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>)

### AI overview

Netdata's TV mode generates a secure, tokenized URL for a custom dashboard, allowing it to be displayed in a browser without requiring a signed-in Netdata Cloud session. The read-only view preserves the dashboard layout, widgets, and time window while removing editing controls and navigation.

### Source excerpt

One of the most common requests we've gotten since launching custom dashboards is deceptively simple: "How do I put this on a TV?" Teams want their dashboards on wall-mounted screens in NOCs, war rooms, and open office spaces. The dashboard is already built. The data is already there. They just need a way to display it on a screen that nobody is logged into, without exposing the full Netdata Cloud interface.

[Next page](<https://devfeed.tech/sources/blog-on-netdata.md?cursor=WyIyMDI2LTA0LTE0VDAwOjAwOjAwKzAwOjAwIiwgIjk2MDdlMTc2LTQ5MWYtNDA4OS04MGZhLTJiMjA3YTQ5MWEzZiJd>)