KEYNOTE: Splunk -- Making Your Applications Observable with OpenTelemetry


Chris Riley
Splunk, Inc., Sr DevOps Advocate

Chris Riley (@hoardinginfo) is obsessed with bringing modern technologies, culture, and practices to tech-enabled enterprises.

As a bad-coder-turned-technology-advocate, Chris understands the challenges and needs of modern engineers, as well as how technology fits into the broader business goals of companies in a demanding high-tech world.

Chris speaks and engages with end-users regularly in the areas of Transformation, SRE, DevOps, SecOps, and App Dev. He works for Splunk as a Tech Advocate and is a regular speaker, contributor to industry blogs such as ContainerJournal.com, DevOps.com and Sweetcode.io, and overall technical adviser. He is also the host of the podcast, Developers Eating the World, Dissecting DevOps, & Tech A’Sketch.


The CNCF project OpenTelemetry is increasingly becoming the standard for getting reliable and consistent application and machine data to your monitoring and observability tools. Many organizations are realizing the power of decoupling their metric, log, traces and span data collection from their monitoring stack. Giving them more freedom, and capabilities, to improve the observability of their application. Allowing organizations to be more consistent and have more confidence in supporting their applications. In this session learn about.

1.) What is OpenTelemetry
2.) What is the architecture of the OpenTelemetry Collector (OTel)
3.) How do you build a strategy around OpenTelemetry
4.) How do you get started with OTel

Standardizing on OpenTelemetry makes your application more observable, and helps your organization implement better observability and monitoring practices.