SigNoz Cloud dashboards are now agent-native SigNoz Cloud dashboards now feature a strict, well-defined schema built on the open CNCF Perses specification, making agentic operations faster, more reliable, and lighter on tokens. The company also rebuilt the dashboard list page with custom views, pinning, and a query DSL for easier management of large collections. The new schema supports PATCH operations for efficient edits and includes a built-in JSON editor, keeping JSON and UI in sync. SigNoz Cloud dashboards are now agent-native TL;DR SigNoz Cloud dashboards now have a strict, well-defined schema built on the open CNCF Perses specification, making agentic operations on dashboards more reliable and efficient. We've also rebuilt the dashboard list page, so managing hundreds of dashboards is easier.Agents are creating a growing share of SigNoz Cloud dashboards as observability becomes agent-driven. A few months ago, we shipped agent-native observability https://signoz.io/blog/introducing-agent-native-observability/ with the SigNoz Cloud MCP server and Noz, our in-app AI assistant. As part of building observability for the AI era https://signoz.io/blog/observability-for-the-ai-era/ , we’re going a level deeper by redesigning the dashboard data model with agents as first-class users. The SigNoz Cloud dashboard schema is now structured and strictly validated. Agents write against a defined schema instead of inferring field names. Creating and editing dashboards is faster, more reliable, and lighter on tokens. We’ve also revamped the dashboard list with custom views, pinning, and search powered by a query DSL, making large dashboard collections easier to organize and navigate. Let’s look at both changes. An agent-native dashboard schema As more agents started operating dashboards, we found the existing JSON was not fully optimized for agents. It was largely free-form and worked well with the UI as the consumer. For an agent, inferring the schema, constructing or modifying JSON, and validating a change could become a bit challenging. The new SigNoz Cloud dashboard schema treats agents as first-class users. Agentic operations on dashboards are now faster, more reliable, and lighter on tokens. A structured, validated schema. The schema now has a defined hierarchy, with a place for every field. An agent knows where to look instead of inferring. Creating a panel, editing a query, or adding a variable means writing to a known path, validated on the way in. dashboard ├── tags key:value pairs on the dashboard ├── sections groups of panels │ └── panels one visualization each │ └── queries what data the panel fetches └── variables filter across panels The new dashboard schema An open format. The new schema is built on the open CNCF Perses dashboard specification, extended with SigNoz-native plugins for queries and panels. Existing Perses dashboards can be migrated with a lightweight conversion, and your dashboards aren't locked into a proprietary format. Dashboards as code. A built-in editor lets you read, edit, and format a dashboard's JSON in the app, with the panel updating as you change it. Agents can edit dashboards using the same JSON, and can change many panels in a single request. Panel styling is part of the schema too, so a fill mode change is one field. More efficient edits by agents. An agent now sends only the field it is changing, whether that is updating a filter inside a panel query or adding a new panel. That means a single PATCH operation instead of rewriting the entire dashboard. Smaller writes use fewer tokens and reduce the risk of agent errors. curl --location --request PATCH '