
OpsRamp announced the launch of its new OpsRamp Partner Program to equip a growing global ecosystem of channel partners and resellers.
This new, enhanced program includes sales and technical training, marketing, demand generation, and selling resources, as well as go-to-market support. The OpsRamp Partner Program is designed to help both technology and solution partners build expertise around hybrid and multi-cloud infrastructure management, with a deep product and customer focus, so they can expertly serve their customers, differentiate their practices and grow a profitable hybrid infrastructure monitoring and AIOps business worldwide.
OpsRamp’s new partner program utilizes a single partner portal with simple, globally consistent membership requirements. The partner portal provides centralized access to marketing, sales, and technical resources, enablement, and training.
Key benefits include:
- Enhanced Partner Support: Partner education, sales support, and customer onboarding and implementation support for expediting partner and customer adoption, maximizing partner revenue and value delivered to customers.
- Increased Co-marketing: New go-to-market strategies, assets, event opportunities, and co-branded initiatives for demand generation.
- Increased Operational Support: Streamlined systems for accelerated deal registration, quotes, and orders, as well as account management and customer support.
“The new, enhanced OpsRamp Partner Program demonstrates our commitment to the success of our channel partners, ” said Mike Munoz, Chief Revenue Officer for OpsRamp. “A critical mass of large enterprises are in the midst of digital transformation and need a platform that can discover, monitor and optimize hybrid, multi-cloud, and cloud native infrastructure. This program allows partners to capture this momentum and quickly deliver value for their customers.”
The Latest
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 ...
Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...
For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...
In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ...
A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...
AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...
Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...
Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...