Operations | Monitoring | ITSM | DevOps | Cloud

Join this livestream for a behind the scenes with the engineers who made it happen: 150 plus customer-requests were turned into enhancements to our core incident management and more across PagerDuty.

Fast front-end and back-end code alone won’t guarantee low end-to-end latency as hidden bottlenecks in the database can undermine even the best engineering efforts. In this session, Oleksii Serhiienko, Senior Site Reliability Engineer at GetYourGuide, will share how his team put database performance at the center of their monitoring strategy. He will highlight how they identified and fixed slow queries, uncovered load balancing issues that drove significant cost savings, and built monitoring practices that improved both reliability and investigation workflows.

​This session will focus on the agent based features of Sentry for debugging an issue in a web application. We'll move through the broken issue - and show how tools like Sentry Seer and the GitHub repo integration make it easy to determine the root cause of an issue by bringing all the context of Sentry and code in GitHub together, and how the Sentry MCP makes it easy to pull all that context down into GitHub CoPilot to fix it locally.

The new Dynamic Stage allows you to import and execute an entire pipeline's YAML definition inside a single stage of your current pipeline. It is essentially running a pipeline within a stage. The pipeline YAML can either be generated and transformed at runtime in a previous stage, or be directly provided to the source input of the Dynamic Stage in encoded form. Dynamic Stages work seamlessly across Harness CI and CD modules.

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.