Operations | Monitoring | ITSM | DevOps | Cloud

Your telemetry data can reduce engineering complexity AND make your software more sustainable - find out how in this episode! Welcome to Episode 5 of Live Laugh Logs, the podcast from the Coralogix Developer Relations team. This week, Annie is joined by Wilco Burggraaf, Principal Lead at HighTech Innovators and host of the Sustainable IT Action Netherlands meetup.

Cribl gives security teams control over their data: what they collect, where to send it and how much to keep. The rest of the SecOps stack hasn’t kept pace. Detections, parsers and configurations spread across SIEMs, pipelines and data lakes still change by hand, so every cost cut, migration or new source turns into weeks of manual validation, and plenty of planned changes never happen at all. SecOps as Code closes that gap: every change ships like software, with testing, version control and rollback across the entire infrastructure.

Sentry offers both "Application Metrics" and "Logs", but both can seem pretty similar. Both logs and metrics are just a collection of attributes attached to a name in your code. Both can be counted, visualized, or alerted on. Both are not sampled by default. So how do you know which to choose? In this video, we'll briefly go over a few examples of when to use logs and when to use metrics. TLDR; Logs are designed for debugging and may be temporary or likely to change when problems arise. Metrics on the other hand are stable, purposely placed events used to track user behaviors.