Daniel Dyla
Senior Open Source Architect - Dynatrace / OpenTelemetry Maintainer
Detroit, Michigan, United States
Actions
Daniel is a Senior Architect with 9 years of experience in observability. Daniel is a member of the W3C Distributed Tracing WG, maintainer of OpenTelemetry JS, former OTel Governance Committee member, and OTel specification sponsor, in addition to working on many other areas of the OTel project. Daniel currently works for Dynatrace, where he continues to help shape the future of open source observability.
Area of Expertise
Topics
OpenTelemetry: Project Updates, Next Steps, and AMA
Join us for the official OpenTelemetry session at KubeCon+CloudNativeCon. Governance committee members will provide insights into the latest developments since the last event in Chicago and offer a glimpse into the future of the project. This session is your chance to engage with OpenTelemetry contributors, ask questions about the project, and receive direct responses from maintainers who will be present at the event. Don't miss this opportunity to stay informed and contribute to the discussion on the exciting advancements within OpenTelemetry.
Observable Feature Rollouts with OpenTelemetry and OpenFeature
As software grows in size and complexity, rolling out new features in a highly distributed application, and understanding their impact, becomes an increasingly difficult task. OpenFeature and OpenTelemetry provide a set of vendor-agnostic and cloud-native APIs and SDKs for dynamic feature flag evaluation, and cloud-native observability.
In this session, we walk through the process of instrumenting an application with OpenTelemetry, rolling out a new feature with OpenFeature, and leveraging OpenTelemetry for feature analytics. We will discuss the tradeoffs between traces, metrics, and the new events API, when each is appropriate, and how to make the same decision for your own application. We show that by using OpenTelemetry and OpenFeature together, you can easily understand the impact a feature has on your users' experience across cohorts, regions, and environments to make informed, data-driven decisions.
OpenTelemetry: What's Next? Logs, Profiles, and More
This is the official OpenTelemetry session at Kubecon. OpenTelemetry started with distributed traces and metrics, but the project's vision has always been to provide whatever signals are needed from infrastructure, services, and more. This session will focus on what's coming next, including new signals and sources.
Join to learn about OpenTelemetry's new logging functionality, including its two logging paths, the benefits of each, and real-world production examples. We'll show the power of the next wave of OpenTelemetry enhancements, including profiling and the insights that this unlocks in combination with distributed traces, and how we're extending your observability to client applications. We'll wrap up with a Q&A of 10+ project maintainers, who can speak to these topics and more.
OpenTelemetry Contribfest
Join the OpenTelemetry maintainers in making OpenTelemetry better for everyone. OpenTelemetry will have several opportunities to contribute.
The OpenTelemetry Collector is vendor-agnostic implementation for receiving, processing and exporting telemetry data. The Collector is a large ecosystem, including individual components, a telemetry transformation language, helm charts, and a Kubernetes operator. Join the Collector maintainers and help fix bugs, add new features, and add new transformation functions.
OpenTelemetry JavaScript is an OTel client written in typescript which supports traces, metrics, and logs, but an observability client is only as good as the telemetry it collects. Help the OTel JS maintainers update the instrumentation libraries and ensure they are outputting semantic convention-compliant telemetry data.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top