
Selector AI announced its Spring 2024 release. Innovations include a GenAI-powered network-oriented LLM, native full-stack monitoring capabilities, and event correlation with root cause analysis.
A unified monitoring, observability, and multi-domain AIOps platform – Selector, provides a single pane of glass with key functionality that historically required multiple tools.
With this release, Selector can not only act on top of existing tools, but can directly collect configuration, metric, event, and log telemetry with its native monitoring capabilities.
"Operations teams have long struggled with tool sprawl in their pursuit of actionable monitoring and observability," said Kannan Kothandaraman, CEO at Selector. "Today's release enables organizations to drive efficiency through tools consolidation while providing insights into the health and performance of their network and IT environments through Selector's innovations in AI and ML."
Key highlights of the new release include:
- Integrated GenAI: Leverage Selector Copilot to instantly access more meaningful incident summaries, assist with troubleshooting, and automate remediation.
- Monitoring and Observability: NetOps, DevOps, and SRE teams can now collect and analyze telemetry from the network up to their applications and everything in between.
- Root-Cause Analysis: An innovative causal approach identifies the root cause of an incident, fast-tracking the investigation and remediation of incidents.
- Digital Twin: With Selector, users can build and leverage digital representations of their network and IT infrastructure.
- GCP Marketplace: Selector is coming to the GCP marketplace in Q2, providing customers with frictionless software procurement, simplified vendor management, streamlined pricing, and the ability to burn down cloud commits.
"Gartner reports that, by 2027, more than 40% of operational activities will be performed using tools enhanced by GenAI, dramatically reducing the labor involved," said Nitin Kumar, CTO at Selector." Assistive troubleshooting, automated incident remediation, and incident summarization are key features that operations leaders have been demanding for years."
The Latest
"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...
Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...
Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...
The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...
Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...
Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...
The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...
Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...
Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...
We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...