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?