Observability Summit Europe

Continuous profiling connects resource consumption to the code responsible for it, adding a code-level view alongside metrics, logs, and traces. The OpenTelemetry eBPF Profiler extends that view across Linux systems, crossing languages, runtimes, and shared libraries without requiring application changes or restarts. Alongside the profiler, the community is shaping the OpenTelemetry Profiles signal to create a common way to represent and transport profiling data. This talk explores what profiling adds to observability, what we are learning by building the profiler and signal collaboratively, and how together they can make profiling open, portable, and broadly accessible.

AI is changing how engineers build, operate, and troubleshoot software. But AI is only as effective as the production context it can access. Today, that context is fragmented across traces, logs, metrics, infrastructure, deployments, and runtime behavior, leaving AI systems without the complete picture needed to understand what's actually happening in production. This keynote explores why runtime context is becoming the foundation of the next generation of software operations. We'll discuss how OpenTelemetry has standardized telemetry collection, why eBPF is making production visibility dramatically easier, and how organizations are moving beyond simply collecting more data toward delivering rich, connected runtime context that both engineers and AI systems can reason about. Attendees will learn: Why runtime context is becoming the new operational data layer. How OpenTelemetry and eBPF are reducing friction in production visibility. Why dynamic telemetry matters more than static instrumentation. How rich runtime context enables AI to troubleshoot, investigate, and automate production operations with greater confidence. As AI becomes part of every engineering workflow, organizations that can provide complete, trustworthy runtime context will be best positioned to unlock the next generation of intelligent operations.

OpenTelemetry helps us measure latency, errors, and availability. But as sustainability moves into engineering, one question remains unanswered: how do we observe carbon? This talk explores Software Carbon Intensity (SCI) through the lens of OpenTelemetry semantic conventions. Rather than focusing on sustainability reporting, we examine the technical challenge of modeling carbon as telemetry: what entities should emissions be attributed to, which attributes should be standardized, and whether carbon belongs in metrics, traces, resource metadata, or all three. We will explore how carbon-related signals can be collected, enriched, and visualized alongside traditional observability data. Attendees will gain a deeper understanding of semantic conventions, telemetry design trade-offs, and the opportunities for OpenTelemetry to support a new generation of operational signals. The audience will leave with these take-aways: * Understanding SCI as an observability signal * Designing semantic conventions for carbon telemetry * Trade-offs between metrics, traces, and resource attributes * Practical implementation patterns using OpenTelemetry * Future directions for green observability