groundcover announced a major expansion with groundcover Dashboards, adding natural-language dashboard and widget creation built on its new query language, gcQL, alongside a deeper set of visualization and governance capabilities.
"The consensus right now is that agents make dashboards obsolete, that everything moves into a chat window," said Shahar Azulay, CEO and co-founder of groundcover. "For an agent, that's actually true. But dashboards aren't dead for people running production; they just need to be better, faster to build, easier to reason about, and ready in seconds instead of hours. That's what we spent this quarter on, and our customers are building more dashboards than before, not fewer."
Keeping telemetry inside a customer's own cloud rather than a vendor's is becoming a baseline requirement for any data-heavy operation. Dashboards make that requirement visible, but a visualization is only as good as the pipeline feeding it, and groundcover keeps that pipeline inside the customer's own infrastructure by default.
Features of this release include:
- Dashboards built by asking, not clicking. Ask Agent Mode for a dashboard and get back a complete, populated board on the first pass, built faster than creating one manually. Describe the outcome you want, such as the health of a workload, and the agent determines which panels are needed, pulling in infrastructure usage, error traces, and error logs as needed. You can sketch a dashboard on a whiteboard or napkin, snap a photo, and drop it into Agent Mode to have it built out automatically. There’s no need to describe it in words at all.
- Dashboards that are cheaper to build. Natural-language dashboard creation is now the default flow, with manual, start-from-scratch creation still available. Users can also generate individual widgets by describing them, preview them in an existing dashboard without rebuilding it, or add a visualization directly from the Data Explorer. A new dashboard catalog offers pre-built templates for CI/CD, databases, RabbitMQ, AWS cost, APM, and more, all previewable against the customer's own data.
- Dashboards that are more capable. groundcover added configurable thresholds on time series charts, displayed as lines or filled ranges with customizable labels. This feature is particularly useful for teams constructing SLO dashboards. A new tree map visualization shows where volume, errors, latency, or cost are concentrated. Stats widgets now support conditional color formatting and configurable decimal precision, while time series charts have gained new Y-axis controls, including scale, minimum and maximum bounds, always-include-zero, and log scale. Widget-level sharing lets a user copy a link that opens a dashboard scrolled to and focused on a specific widget, which is useful on dashboards containing 40 or 50 widgets. Hovering over a table row surfaces a drill-down into Explore, either for aggregate analysis or the underlying rows.
- Dashboards that are governable. groundcover reworked dashboard variables with a new interface and advanced settings, including cross-source key mapping, so a single variable can resolve across data sources with mismatched labels, such as cluster_id in logs and cluster.id in metrics. Dashboards can now be tagged for organization, with team ownership and permissions in progress to help ensure that a dashboard someone built can't be deleted by someone who didn't build it. Version history with revert and synced crosshairs across widgets are both included.
Teams migrating from Datadog will find that threshold visualizations and tree maps, two components with no prior equivalent in groundcover, now have parity, addressing a common reason migrated dashboards previously broke.
"These pull in the same direction," said Orr Benjamin, VP of Product Management at groundcover. "Every visualization we add is one the agent can reach for. When someone asks for a view of error rate against deploys, the quality of what comes back depends entirely on what the dashboard layer can express. Building better primitives is how you get better agent output. The two aren't a trade-off, and treating them as one is the mistake."
groundcover Dashboards, gcQL, and the capabilities described above are available now to all groundcover customers.
The Latest
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...
Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...
Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...
In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...
Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...
Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...
This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...
There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...