Operations teams have lived with the same frustrating tradeoff for years: the data exists, but getting to the right answer often takes too much time and too much expertise.
Engineers are expected to know platform-specific query languages, navigate layers of dashboards, and understand exactly where the right visualization lives before they can even begin troubleshooting. That approach can work in smaller environments, but as infrastructure grows more distributed and complex, it becomes a bottleneck.
Selector’s published U.S. patent application, US20250278401A1, introduces a different model. Titled “Dashboard Metadata as Training Data for Natural Language Querying,” the application describes how dashboard metadata, aliases, and user interactions can be used to train a system to understand natural language questions about infrastructure and application performance. Instead of forcing operators to write rigid structured queries, the system enables them to ask questions in plain English and receive relevant operational insight.
The problem with traditional dashboard-based operations
Traditional dashboards are useful, but they place a heavy burden on the user.
To get value from a dashboard, operators typically need to know where data lives, how it is labeled, which filters to apply, and how to translate a real-world issue into a query the system can understand. That means the process of investigation often depends as much on platform fluency as on technical judgment.
As environments scale, that model becomes harder to sustain. Teams move faster, systems become more heterogeneous, and the people who need answers are not always the same people who built the dashboards in the first place.
What Selector’s patent changes
Selector’s patent reframes the dashboard as more than a visualization layer. It treats the dashboard as a source of operational intelligence.
What Selector has discovered is that dashboard metadata can be used to generate alias datasets that map natural language expressions to operational context. In practical terms, that means the platform learns from how dashboards are already structured, labeled, and used. Instead of starting from scratch each time a user submits a question, the system can use that accumulated context to determine intent, build the appropriate structured query, and return the relevant data.
That is an important shift. The dashboard is no longer just where users go to see information. It becomes a part of how the system learns to understand what users mean.
How natural language querying improves the operator experience
The benefit of this approach is straightforward: operators can think like operators instead of thinking like query engines.
Instead of writing something like:
interface_errors where region=west and device_type=core_router
a user could ask:
Why is packet loss increasing in the west region?
The platform then interprets the request, identifies teh likely operational context, generates the necessary underlying queries, and surfaces the relevant performance data.
This changes the interaction model in a meaningful way. Rather than forcing users to translate operational problems into strict machine syntax, the system does more of the translation work itself.
Why dashboard metadata matters as training data
One of the most compelling ideas in the patent is that dashboards already contain valuable training signals.
Metadata, aliases, labels, and usage patterns reflect how teams organize and interpret their environments. They encode the language people use, the metrics they care about, and the relationships they rely on when diagnosing issues. By using that existing structure as training data, the platform can build a more domain-aware natural language layer without depending entirely on manual labeling.
The patent also points to a more adaptive approach than many traditional natural-language-to-query systems. Instead of requiring constant retraining whenever terminology changes, the system can use dashboard metadata and user-entered language to update or recreate alias datasets over time. That makes the model more relevant to the customer’s environment and reduces the burden of manual annotation.
Why this matters for operations teams
For operations teams, the value is practical and immediate.
First, troubleshooting becomes faster. Users can ask direct questions instead of spending time navigating dashboards or constructing queries.
Second, the skill barrier drops. Junior team members do not need deep knowledge of dashboard hierarchy or query syntax just to investigate an issue.
Third, institutional knowledge becomes more durable. In many organizations, the most valuable operational knowledge lives in the heads of senior engineers. They know which metrics matter, which dashboards are reliable, and which terms different teams use for the same problem. Selector’s approach helps convert that tribal knowledge into a system that can learn from it and reuse it.
That matters because operational scale increasingly depends on making expertise more accessible, not just hiring more experts.
Why this is relevant to AIOps and observability
This patent is also important in the broader context of AIOps and observability.
Natural language querying only becomes truly useful when it sits on top of a platform that already understands the underlying operational data model. The patent describes an operations management system that ingests heterogeneous data from multiple sources, normalizes and labels that data, generates queries against it, and presents the resulting metrics to users.
In other words, the conversational layer is only powerful if the foundation beneath it is already capable of correlation, normalization, and contextual retrieval.
That is why this matters beyond dashboard usability. It points to a future where observability platforms are not just passive systems of record, but active systems of interaction.
From static dashboards to conversational operations
For most of their history, dashboards have been passive tools. They wait to be searched, filtered, and interpreted.
Selector’s approach suggests something more dynamic: an operational system that can be queried conversationally because it has already learned from the structure and behavior embedded in the environment. Instead of asking people to adapt to the system’s language, the system adapts to theirs.
That is the larger message behind this patent. It is not simply about making dashboards easier to use. It is about turning operational data into something teams can talk to, not just something they have to search.
Final takeaway
Selector’s natural language querying approach reflects a broader change in how operational platforms can capture and apply knowledge. By learning from dashboard metadata and user interactions, the system can reduce friction, lower the expertise barrier, and make infrastructure insights more accessible across the organization.
If that vision continues to mature, the future of operations may look less like searching through dashboards and more like having a conversation with the system itself.
Stay Connected
Selector is helping organizations move beyond legacy complexity toward clarity, intelligence, and control. Stay ahead of what’s next in observability and AI for network operations:
- Subscribe to our newsletter for the latest insights, product updates, and industry perspectives.
- Follow us on YouTube for demos, expert discussions, and event recaps.
- Connect with us on LinkedIn for thought leadership and community updates.
- Join the conversation on X for real-time commentary and product news.
