Operations | Monitoring | ITSM | DevOps | Cloud

We’re excited to announce the release of Coroot 1.11! This version comes with powerful new features designed to give you more control over your observability data and make your troubleshooting process faster and more intuitive. Let’s dive into what’s new.

At Mezmo, we’ve always believed that observability should empower innovation, not hold it back with complexity and unpredictable costs. However, as organizations scale and data volumes continue to explode, the old ways of managing telemetry data aren’t sustainable.

Mobile apps are a little different from services run on servers. You build your mobile app, you ship it off to the world, and then it gets run by the end user on their own machine. If your app is running poorly on some percentage of users’ devices, you may never know. That’s where observability comes in. There are certain important metrics that every mobile app has in common.

Observability platforms want to do it all—from data collection to incident response. Their pitch is appealing: one platform to eliminate context switching and reduce overhead. But when critical systems fail—and they will fail—, add-on incident management modules won’t save you. You need an end-to-end system built specifically for high-stakes incident management.

Modern engineering teams spend a lot of time and resources in setting up monitoring of their production systems - tracking uptime, catching errors, and responding to incidents before customers ever notice. But what about the journey before code reaches production? For most teams, observing the CI/CD pipeline is either an afterthought or completely overlooked. While we recognize its importance, do we truly understand how well our CI/CD process is functioning?

Observability isn’t about collecting more telemetry — it’s about making that telemetry data meaningful. Contextual observability transforms raw telemetry into actionable insights by enriching it with consistent tagging and metadata. Without context, telemetry data remains fragmented, troubleshooting slows, and aligning with business priorities is nearly impossible.

Temporal lets you orchestrate complex, reliable workflows, but when something breaks or slows down, the built-in dashboards only give you a list of events and some basic filters. You can see what happened and filter by attributes like workflow type or namespace, but you can't drill deeper. There's no way to jump straight from a metric spike to the exact trace or log line you care about.

There’s a problem in engineering culture that we don’t talk about enough: observability is an afterthought. It’s treated as tooling, not thinking. As a checkbox, not a habit. And that mindset gap creates real consequences: longer outages, frustrated teams and massive business costs. Atlassian’s Incident Management for High-Velocity Teams overview cites a 2014 study by Gartner, that the average cost of IT downtime is $5,600 per minute.

The last few months have been wild. Some of the busiest of my life, actually: For context: I’m Canadian, and all of this happened during the continued threats of annexation. All this to say, it’s been rough. I anticipated this would be a challenging time and that I would be exhausted. So, the plan became: do all the demanding things, take my sabbatical in May, and use April as an ‘in-between’ period with a bit less pressure.

For today’s enterprises, ensuring optimized network connectivity and robust network security represent key imperatives. Given that, it makes sense that there’s rapidly growing use of solutions like secure access service edge (SASE). In fact, the SASE market is expected to grow to $5.9 billion by 2028. SASE delivers converged network and security capabilities. SASE is a cloud-based offering that is primarily delivered on an as-a-service basis.