London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

How engineering teams regain visibility at scale

As the stream of telemetry data outpaces engineers’ capacity to review it, observability costs are skyrocketing.


Date & time

17:00

Register for the panel discussion

Login or join LeadDev.com to view this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register

Teams are drowning in noisy observability stacks, incidents buried inside distributed systems and “unknown-unknown” production failures.

AI monitoring adoption jumped from 42% to 54% year-on-year as teams raced to understand its increasing complexity.

This session is designed to give engineering leaders a practical operational playbook they can take back to their teams immediately. Using real-world scenarios, we’ll explore why traditional monitoring and review practices are no longer enough for frontier-level software.

Alongside the technical practices, we’ll focus on the leadership that effective systems require, with a focus on reducing alert fatigue and cognitive debt and creating shared operational language.

Key takeaways:

  • Replace static dashboards and reactive monitoring with approaches that surface production issues earlier
  • Build deployment pipelines that preserve traceability, so you can cut debugging time by linking issues back to the change behind them
  • Create review workflows that analyse system behaviour, lowering the cognitive load on engineers

panelists:

Moderator: