Operations | Monitoring | ITSM | DevOps | Cloud

It’s been a while since the last update on “What’s New” series, so I will try and keep it short yet informative. Stay tuned for upcoming content on anomaly detection.

When a team, division or organization is assessing a new vendor, there are some basic questions that must be answered. At Coralogix, we look at migrations in a different way. It isn’t about transporting the current state of play into a new vendor, often called a “lift and shift”. These are the basics. There is a whole new level of onboarding and support that doesn’t just replicate value across platforms – it expands it.

Automation has become more than just a "nice to have" choice. It's an essential part of the modern business landscape, promising increased efficiency, reduced costs, and improved accuracy. However, despite its potential benefits, many organizations struggle when trying to implement automation. In this article, we'll explore some of the most common implementation mistakes we've encountered and how to navigate them effectively.

We know that AI has been transformational for engineering and it will continue to be, so stop me if this sounds familiar. Imagine an engineering lead opening a pull request for a critical security patch and finding five hundred lines of AI-generated code. While the solution is (mostly) usable, it follows a pattern no one on the team recognizes. This shift away from manually writing every line of logic has introduced a unique level of complexity for teams.

London, February 3, 2026 — Canonical and AWS are pleased to announce the release of the new snap for AWS IoT Greengrass, making the deployment of your IoT solutions easy and seamless all the way from silicon to the cloud. With the AWS IoT Greengrass agent now available as a snap package from the Canonical Snap Store, Ubuntu Core has become the ideal operating system for all your AWS IoT edge workloads and data ingress.

It’s 2026, and developers have more tools at their disposal than at any point in the industry’s history: CI/CD platforms are richer; observability stacks are deeper; security, data, and AI tooling have exploded into crowded, competitive ecosystems. And yet, delivery is still slow, incidents are still noisy, workflows are still brittle. The problem is no longer tool scarcity or feature depth. It’s integration debt.

Today, we’re launching a new approach to running disaster recovery tests, validating failover processes, and ensuring compliance with regulations such as DORA. With Disaster Recovery Testing, you can run zone, region, and datacenter-scale experiments across your entire Gremlin organization simultaneously. ‍

Over the past couple of weeks, as snowstorms and extreme cold swept across much of the Northeast, something interesting started happening on our end at OnPage. Our phones lit up. Not from healthcare teams or IT operations/tech teams, which is where many people expect us to be used, but from HVAC companies, contractors, and property management firms scrambling to prepare for what they knew was coming.

This guide shows you how to implement OpenTelemetry’s auto-instrumentation for complete distributed tracing across your microservices, from initial setup through production optimization and troubleshooting.

OpenTelemetry instrumentation is the foundation of modern microservices observability, but getting it right in production requires more than just enabling auto-instrumentation. This guide covers production-tested OpenTelemetry best practices that help engineering teams achieve reliable distributed tracing, control observability costs, and extract maximum value from their telemetry data.