OpsCruise announced contextual tracing support (CTS) in OpsCruise platform.
CTS leverages existing CNCF tracing tools, such as Jaeger, OpenTelemetry, and others, to complement OpsCruise’s eBPF based flow analytics application graph without distributed tracing.
While distributed tracing is a powerful tool for in-depth application performance monitoring, analyzing high volumes of trace data to find the relevant traces is very challenging because it is time consuming, labor intensive, and requires resources with a complex skill set, slowing down the MTTR.
OpsCruise resolves the challenge and makes distributed tracing usable in real-time by providing a Trace-Service Graph. The Trace-Service Graph captures the execution path of each trace and aggregates them into trace path signatures thus providing engineers a real-time view of each trace path’s performance. In addition, it extends OpsCruise’s ML-based behavior model used for microservices to predictively detect problems in the trace path. It also complements OpsCruise’s currently available flow analytics application graph that is generated without distributed tracing using only eBPF. CTS provides click-through from the trace-service graph to actual traces. Trace Ids are added to Logs so they can also be used to retrieve contextually relevant traces in problem contexts.
“This is a perfect example of how OpsCruise takes traditionally siloed telemetry - in this case eBPF networking data, distributed traces and K8s/container object metadata - and combines it in a powerful, declarative approach to automate troubleshooting of cloud native application issues,” said Scott Fulton, Co-Founder & CEO of OpsCruise. “Further, the long-term storage of your raw traces remain in your infrastructure at a fraction of the cost a typical SaaS monitoring vendor would charge you.”
CTS and its related extensions are available now as part of the standard OpsCruise subscription. OpsCruise supports OpenTelemetry, Jaeger, OpenZipkin, and any other OpenTelemetry Compliant tracing library, with additional libraries coming over Time.
The Latest
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...
Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...
Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...
As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...
For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...
I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...