Operations | Monitoring | ITSM | DevOps | Cloud

The UK introduces a cybersecurity bill that enforces stricter regulations for critical infrastructure. As threat actors become more aggressive and utilize AI for advanced attacks, the legislation mandates organizations to respond quickly to incidents. Vendors must notify authorities within 24 hours, and emergency powers are created to improve cybersecurity responses. The emphasis is now on managing exposure in vulnerability practices.

How do you get developers to instrument their code? You stop asking! Instead, pitch the value of observability by building them dashboards and implementing the no-code change solutions first, demonstrating the value of instrumentation.

Over 30% of your production logs might be useless DEBUG logs! This "bad telemetry" is expensive noise. The KubeCon talk I attended introduced a project called the Instrumentation Score which helps you find and fix bad telemetry.

Learn more - https://ribboncommunications.com/solutions/service-provider-solutions/service-provider-type/rural-regional-service-providers

While observability practices have evolved in recent years, they have largely focused on application services and infrastructure. Yet it is data what powers our applications, businesses, and AI models. When data issues occur, the consequences can be far reaching, from poor product experiences to billing errors to misinformed AI outcomes. In this session, Jonathan Morin, Group Product Manager at Datadog, shares real-world examples of incidents and explains how data observability can address them, helping teams detect issues earlier, reduce costly downtime, and restore trust in their data.