CNCF-hosted Co-located Events North America 2024

The OpenTelemetry (OTel) Operator is a great tool that helps make your life a little easier by managing OTel for you in your Kubernetes cluster, by: Managing the deployment of the OpenTelemetry Collector Managing the configuration of a fleet of OpenTelemetry Collectors via OpAMP integration Injecting and configuring auto-instrumentation into your pods But what happens when THINGS. DON’T. WORK??

In this talk, Adriana and Reese will cover:

• An overview of the OTel Operator 
• Common installation issues
• Common auto-instrumentation issues
• Common OTel Collector deployment issues
• * …and how to tackle them all

Attendees will walk away from this session with a better understanding of how they can leverage the Operator, and be empowered to use it with confidence.

Continuous profiling is a technique to collect stack trace granularity insight into production resource usage. It is something SREs and other engineers can enable without changes to the app, or knowing how it was compiled. This year, this powerful signal and a polyglot eBPF profiling agent were added to OpenTelemetry. Our talk explores how an existing OpenTelemetry system is better with profiling, specifically how distributed tracing fits into the picture. You'll see both tools in action on Kubernetes, including cross-service requests and how correlation of distributed traces and profiles let you answer more questions, specifically code level causality. We'll show how to leverage this data for resource utilization and even monitoring your carbon footprint. You'll leave with a concrete understanding of continuous profiling, how it relates to OpenTelemetry and how these tools combine to reduce time while adding more understanding of your Kubernetes workloads, from kernel to code.

Learning how to use a new tool, and using it well enough to get value out of it quickly is really important. Configuring OpenTelemetry SDKs and instrumentation is essential, but programmatic configuration is cumbersome and environment variables are limited. OpenTelemetry file configuration is the community’s next generation config tool. Building on the original flattened environment variable based scheme, file configuration introduces tooling for configuring SDKs and instrumentation which accommodates the complexities of how people use OpenTelemetry in practice.

Come learn about:

• What the OpenTelemetry Configuration Schema is and why it exists. 
• How language agnostic file configuration provides OpenTelemetry adopters the tools needed to support complex scenarios.
• How various components in OpenTelemetry have adopted the configuration schema.
• Using a single configuration to configure OpenTelemetry SDKs in multiple languages and the Collector.

In this talk I will highlight some of the key issues end users face getting started with OpenTelemetry, and some possible ways to solve for this. Some common questions we see are: 1. What is the right way to deploy otel collectors for my scale? 2. I have instrumented my applications but I don't see my telemetry data data ( esp. around tracing) 3. Questions around manual instrumentation or any use cases which are not covered by auto instrumentation are tough to get help and guidance on This is more of an introspective talk on what we can do better as a community and derives from our experience of helping 1000s of users get started with OpenTelemetry.

Reading logs from a file is a very simple concept to understand, but implementing it is a whole other story. This lightning talk will dive into the full process of how Fluent Bit file logging works: detecting file changes, reading new lines from files, tracking state, handling file rotations, and more. This talk will be a brief glimpse into just one of the many deep challenges of implementing efficient observability data collection.