As the holiday season comes to an end and we step into 2025 with renewed energy and excitement, Coralogix kicks off the year with a remarkable gift of achievements! In the G2 Winter 2025 Reports, we are thrilled to announce that we’ve been recognized with a phenomenal 126 badges across multiple categories and market segments. This remarkable feat is a testament to the trust and love of our customers and the dedication of our team.

So, there I was, a newbie to.NET 9.0, Blazor, and Coralogix, standing on the precipice of observability in a world of production bugs and development mysteries. As an Agile enthusiast, I’m well versed in all things “observability” and how it’s a game-changer for root cause analysis, especially in today’s rapid, iterative development cycles. Observability is like getting X-ray vision into your application to understand what’s truly happening based on system outputs.

As we gear up for AWS re:Invent this December, we’re excited to share some of the latest innovations that make our platform stand out. Coralogix continues to evolve with powerful new capabilities designed to simplify observability, improve performance monitoring, and deliver actionable insights across your systems. From advanced visualization tools to AI-powered troubleshooting, these updates reflect our commitment to empowering teams with smarter, faster ways to solve complex challenges.

When discussing what makes a product different, what makes it unique, we are led down the path of feature comparison. It is a natural thing to break down a product into its component parts to ease the process of weighing and measuring each layer. Does the authentication layer support SAML? Can platform components be defined in code? Beneath each of these features, however, is a foundational strata. A golden thread that enables and constrains each and every piece.

As the official implementation date approaches for the Digital Operational Resilience Act (DORA) – financial institutions and their information and communication technology (ICT) service providers, across the European Union are gearing up for a significant shift in their operational landscape.

When we talk about Real User Monitoring (RUM), it’s easy to get wrapped up in metrics—the hard numbers that tell us about our users’ experiences. But RUM is more than just data; it’s the foundation for improving performance, an essential key to user experience. The big question is: how do you accurately measure that experience across different kinds of applications?

In a world where microservices rule and distributed architectures are the norm, understanding how a single request flows through your system can be an overwhelming challenge. But don’t worry—there’s light at the end of the tunnel! And not just one light, but four.

As your data continues to grow and time remains critical, making data-driven decisions has never been more important (and let’s face it, that’s no small feat). Luckily, our new Scheduled Reporting feature is here to help—automatically delivering your logs, metrics, and tracing data in visually-rich custom dashboards, exactly when you need them, directly to the inboxes of your chosen recipients.

tldr: This post discusses how to measure CDN request locality without indexing a single log. The function of a CDN is to bring cacheable data, like pictures & videos, physically closer to your customers. This reduces latencies, and load on your backend servers. When measuring CDNs, there are some very common metrics.