SL announced monitoring as a service for Solace with RTView Cloud for Middleware Monitoring.
RTView Cloud provides users with a way to proactively monitor their distributed Solace environments to maximize uptime and reduce the time required to address incidents. The solution consists of pre-built dashboards for monitoring Solace PubSub+ Cloud, appliances and software. With dozens of pre-defined alerts and pre-built monitoring displays, users can quickly deploy a powerful monitoring solution without the time, skill and expense necessary to build or configure their own monitoring applications.
The new RTView Cloud designer provides additional capability for users to create custom monitoring displays from a browser and without the need to do any custom programming. This enables middleware support teams to offer custom displays to their end users that provide them with the exact metrics they need in the exact way they would like to see them.
Data security with RTView Cloud is enhanced through the use of a hybrid architecture which ensures all monitoring data stays securely behind the firewall. Performance metrics and alert data are accessed directly from users’ browsers and never pushed out to the Cloud.
“As more and more applications and data move to the cloud, the need for a robust monitoring system that can connect to Solace systems across hybrid and multi-cloud environments is important for maximizing performance,” said Denis King, COO of Solace Systems.
“SL already successfully monitors Solace PubSub+ Appliances, Software, and Cloud. We are now strengthening our cooperation with cloud-based monitoring as a service for Solace,” said Praful Bhayani, VP of Strategic Projects and Business Development at SL Corporation.
SL now offers three ways to monitor Solace:
- RTView Cloud for Solace Monitoring hosted in the Cloud
- RTView Solace Monitor AMI deployed in your AWS account
- RTView Enterprise Edition deployed on premise
The Latest
For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...
Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...
Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...
Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...
I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...
The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...
For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...
The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...
44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...
Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...