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. TV mode does exactly this.

Alerts are meant to help teams respond quickly to problems, but too often they arrive without enough context to be immediately useful. An alert that says “CPU usage is high” still leaves the on-call engineer asking critical follow-up questions: Which service? Which environment? Where do I look next? Validating the alert and triaging the situation is the first step for every engineer. It's a manual step that takes time, extending every potential incident.

ServiceNow holds a wealth of operational data—but turning that data into dashboards people actually use is a different challenge altogether. Most teams start with what’s available out of the box. Then come the requests: At that point, dashboarding stops being simple. It then has to be “augmented” - with easy shareability, ease of use, contextualization and hierarchy.

In the race to provide full-stack visibility, many modern SaaS platforms have inadvertently created a new problem: information overload. High-end enterprise solutions are designed for companies with dedicated Site Reliability Engineering (SRE) teams that spend their entire day inside a dashboard. But for many businesses, this level of granularity is a distraction. The real question isn’t whether a tool is powerful; it’s whether it fits the everyday needs of your team.

When you identify CPU or memory spikes in your services, it’s critical to understand why they’re happening. But switching between tools or crafting complex queries can slow you down when trying to pinpoint a root cause. This is why we’re excited to share that Profiles Drilldown, an application that lets you easily explore profiling data through an intuitive, point-and-click interface (no queries required), is now integrated with Grafana Cloud Knowledge Graph.

The Kubernetes Monitoring Helm chart is the easiest way to send metrics, logs, traces, and profiles from your Kubernetes clusters to Grafana Cloud (or a self-hosted Grafana stack). And version 4.0 is the biggest update the chart has ever received. Representing nearly six months of planning and development, it's designed to solve real pain points that users have hit as their monitoring setups have grown.

As teams scale, managing synthetic monitoring checks manually in the UI becomes difficult and error-prone. When you're dealing with dozens of checks across multiple environments, teams experience inconsistent configurations, lack of version control, and difficulty tracking changes.

The public cloud has revolutionized IT by making infrastructure on-demand, scalable, and self-service. However, this convenience comes at a price. In the cloud, engineers can instantly spin up resources and spend company money with the click of a button or a line of code, bypassing traditional procurement and finance approval processes.

Custom dashboards in Netdata have always let you pull charts together on-the-fly into a single view. That’s useful, but it’s also limited. In practice, when you’re running an incident or reviewing a service, you don’t just want charts. You want to see the output of top alongside your CPU metrics. You want slow query logs next to your database latency charts.