Operations | Monitoring | ITSM | DevOps | Cloud

Coralogix has spent years building metrics infrastructure that handles high cardinality and high dimensionality without flinching, with governance, usage visibility, and cost optimization built into the platform, and recognized industry delivery to show for it. Today that infrastructure takes its biggest step yet. We have rebuilt the metrics engine from the ground up, with a new pricing model, a set of new capabilities, and a tripled fair usage allowance to enjoy them in.

We got a little behind on updating our changeLOG, so we’re dumping it all into this bLOG post instead. Think of it as one giant, retroactive changelog entry or, if you want to be dramatic about it, one massive prompt injection straight into your feed. Either way: here’s everything that shipped for Sentry Logs this summer. Would you rather listen to the team talk about what they built? Check out this video where Kyle and Josh talk about the latest updates on Logs.

If you are leading technology strategy today, you face consequential choices about how to manage your enterprise telemetry. Your decisions determine not only where logs, metrics, traces, and events are stored, but also who controls how operational data is collected, shaped, governed, and put to work in an optimal way for the security, observability, analytics, and AI systems that power your business.

Originally written by Paul Stefanski, updated by Dylan Myers. Data costs fill a large column in many organizations' accounting sheets. Data pipeline setup and management is a significant time sink for DevOps, IT, and SRE. Setting up telemetry pipelines to reduce unwanted data often takes even more time, which could better be spent creating value rather than reducing costs. This post will show you how to quickly set up your data pipeline to filter unnecessary telemetry data.