Logo

    software engineering radio

    Explore "software engineering radio" with insightful episodes like "SE Radio 556: Alex Boten on Open Telemetry" and "Episode 550: J.R. Storment and Mike Fuller on Cloud FinOps (Financial Operations)" from podcasts like ""Software Engineering Radio - the podcast for professional software developers" and "Software Engineering Radio - the podcast for professional software developers"" and more!

    Episodes (2)

    SE Radio 556: Alex Boten on Open Telemetry

    SE Radio 556: Alex Boten on Open Telemetry

    Software engineer Alex Boten, author of Cloud Native Observability with Open Telemetry, joins SE Radio host Robert Blumen for a conversation about software telemetry and the OpenTelemetry project. After a brief review of the topic and the OpenTelemetry project's origins rooted in the need for interoperability between telemetry sources and back ends, they discuss the open telemetry server and its features, including transforms, filtering, sampling, and rate limiting. They consider a range of topics, starting with alternative topologies with and without the telemetry server, server pipelines, and scaling out the server, as well as a detailed look at extension points and extensions; authentication; adoption; and migration.

    Episode 550: J.R. Storment and Mike Fuller on Cloud FinOps (Financial Operations)

    Episode 550: J.R. Storment and Mike Fuller on Cloud FinOps (Financial Operations)

    J.R. Storment and Mike Fuller discuss cloud financial operations (FinOps) with host Akshay Manchale. They consider the importance of a financial operations strategy for cloud-based infrastructure. J.R. and Mike discuss the differences between operating your own data center and running in the cloud, as well as the problems that doing so creates in understanding and forecasting cloud spend. Mike details the Cloud FinOps lifecycle by first attributing organizational cloud spend through showbacks and chargebacks to individual teams and products. JR describes the two levers available for optimization once an organization understands where they're spending their cloud budget. They discuss complexities that arise from virtualized infrastructure and techniques to attribute cloud usage to the correct owners, and close with some recommendations for engineering leaders who are getting started on cloud FinOps strategy.