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.

Working at Coralogix, a leading full-stack observability platform, I recently faced an interesting challenge. The team I am part of is building the DataPrime query language and query engine, used to easily query logs and other observability data on the platform, usually in the form of Parquet files on AWS S3. Inside the engine, our DataPrime queries are transformed into query plans with SQL-like expressions, for example in filters.

Network infrastructure is the hidden glue between servers. In AWS, it takes skill, knowledge and experience to build a network that can be monitored, will perform and is secure. A key source of information to determine the health of a network is the logs, but network logs suffer from a serious problem. They’re noisy, and they’re often difficult to parse, but by leveraging indexless observability, Coralogix customers can drive insights from data that would previously have been untouchable.

AWS MediaTailor provides a wealth of information via metrics, but one key feature that is very difficult to track is the Transcoding performance. What is transcoding and why is performance important?