Mezmo unveiled data profiling and responsive pipelines for Kubernetes telemetry data.
Now, site reliability engineers (SREs), platform engineers, and other infrastructure teams can understand telemetry data clearly, optimize with ease, and respond to incidents rapidly — ultimately cuttting costs and improving management of their Kubernetes environments
Mezmo Telemetry Pipeline now features capabilities that help companies understand, optimize and respond to telemetry data. Mezmo Data Profiling categorizes data so teams can understand where their data originates, what it contains, and how to pull signals out of the noise. Such an understanding helps determine strategy for data reduction, metrics transformation and data routing — sending the right data in the right format to observaability tools. Mezmo Responsive Pipelines can be configured to respond to changes based on specific conditions, such as during an incident when capturing more data is critical or during data drift in source systems.
"Based on feedback from the many SREs we've spoken with, we know that the first step in getting the most from your telemetry data and your observability investments is to understand your data, which is why we've invested in Data Profiling," said Tucker Callaway, CEO of Mezmo. "We also believe that telemetry pipelines must be responsive, not static. Our platform recognizes data drift or incidents detected within observability tools and then adjusts data streams and recommends remediation steps, so that teams can take immediate actions that improve mean time to resolution."
These product additions build on recent innovations, including Mezmo Edge, for running telemetry pipelines in local environments while managing them centrally via the cloud. Mezmo Edge allows teams to gain the benefits of Telemetry Pipeline without sending data outside of their networks, reducing egress costs and honoring enterprise compliance requirements. Mezmo also offers Pipelines as Code via Terraform to support SRE-focused development and automation. Building and managing Pipelines as Code helps SREs increase change velocity and reduce toil while ensuring consistency across deployments.
The Latest
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 ...
77% of leaders say their teams need AI skills urgently. 64% say their organization plans to train current employees rather than hire new ones. So far, so reasonable. The part that surprised me is who's been put in charge: 34% of those leaders say IT and engineering own the AI skills mandate. Learning and Development or HR own it at 7% of organizations. That's roughly five-to-one in favor of the people who understand the tools, over the people whose actual job is teaching adults how to learn new ones ...
In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i ...