Today we ran the workshop Choose Your Own CNCF Observability Project Adventure in Room 327. It was bring a laptop, pick a project, and go deep on whichever one you care about most: Fluent Bit for pipelines, Prometheus for metrics, OpenTelemetry for traces, OpenTelemetry for Java Developers if you want hands on instrumentation, or Perses for visualization.
Below are the slides I shared to introduce everyone to the cloud native observability workshop collection.
I really like the vibe of this conference with the local scene full of really engaged developers and observability enthusiasts. I submitted a few ideas around my own personal open source interests and they came back asking me to facilitate a hands-on workshop.
The workshop is the sum of all my personal explorations of the Cloud Native Computing Foundation (CNCF) projects over the last four years. For this event they will be expanded into the option of running and exploring all the projects on a lightweight Kubernetes for your personal machine (k3s).
Read on for more details
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, contributing to the Fluent Bit docs project. This is a follow-up to our previous article on contributing to the Fluent Bit project website, and this time we go a step further by tackling documentation contributions. If we can find something undocumented, clarify something confusing, or fix a gap between what the code does and what the docs say — that is a genuine contribution that the community notices.
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, contributing to the Fluent Bit project website. This article will be a hands-on exploration of how to get started contributing blog articles to the Fluent Bit project website, something that is very accessible to newcomers and a great way to become part of the community.
Today I'm excited to share that I've joined SUSE as Technical Advocacy Lead — and I couldn't be more energized about what lies ahead.
Let me back up a bit, because getting here is a story worth telling.
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, integrating Fluent Bit with Prometheus. In case you missed the previous article, check out the developer guide to monitoring health metrics with Prometheus where you explore how to monitor the health of your telemetry data pipelines.
This article will complete our hands-on exploration of Prometheus integration, helping developers leverage Fluent Bit's powerful metrics capabilities. We'll look at the final pattern for integrating Fluent Bit with Prometheus in your observability infrastructure.
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, integrating Fluent Bit with Prometheus. In case you missed the previous article, check out the developer guide to routing metrics to Prometheus where you explore how to collect and direct metrics telemetry data to your Prometheus instance.
This article will continue our hands-on exploration of Prometheus integration, helping developers leverage Fluent Bit's powerful metrics capabilities. We'll look at the second of three essential patterns for integrating Fluent Bit with Prometheus in your observability infrastructure.
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, integrating Fluent Bit with Prometheus. In case you missed the previous article, check out the developer guide to telemetry pipeline routing where you explore how to direct telemetry data to different destinations based on tags, patterns, and conditions.
This article will be a hands-on exploration of Prometheus integration that helps you as a developer leverage Fluent Bit's powerful metrics capabilities. We'll look at the first of three essential patterns for integrating Fluent Bit with Prometheus in your observability infrastructure.
This year, the focus for me and my teams remained on the four pillars of our role: speaking, publishing, socializing, and hands-on content generation.
While 2024 was about observability (o11y) taking center stage, 2025 was the year we put those theories into practice, accelerated our momentum, and stated to gain serious traction in the wild.
Read on to find out more!
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, using Fluent Bit routing for developers. In case you missed the previous article, check out the top three telemetry pipeline filters where you explore the most useful filters for manipulating and controlling your telemetry data.
This article will be a hands-on exploration of routing patterns that help you as a developer building sophisticated telemetry pipelines. We'll look at how to direct telemetry data to different destinations based on tags, patterns, and conditions in your Fluent Bit configurations.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, using Fluent Bit filters for developers. In case you missed the previous article, check out three tips for using telemetry pipeline multiline parsers where you explore how to handle complex multiline log messages.
This article will be a hands-on exploration of filters that help you as a developer testing out your Fluent Bit pipelines. We'll take a look at the top three filters you'll want to know about when building your telemetry pipeline configurations in Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, using Fluent Bit multiline parsers for developers. In case you missed the previous article, check out using telemetry pipeline processors where you explore the top three telemetry data processors for developers.
This article will be a dive into parsers that help developer testing of Fluent Bit pipelines when dealing with difficult and long multiline log messages. We'll take a look at using multiline parsers for your telemetry pipeline configuration in Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, using Fluent Bit processors for developers. In case you missed the previous article, check out the top tips on using telemetry pipeline parsers for developers where you get tips on cleaning up your telemetry data for better developer experiences.
This article will be a hands-on tour of the things that help you as a developer testing out your Fluent Bit pipelines. We'll take a look at the top 3 processors you'll want to know about when building your telemetry pipeline configurations in Fluent Bit.
This is a special update to the original Controlling Logs with Fluent Bit on Kubernetes article published previously that is no longer valid.
The issue requiring this update arose over last weekend when I discovered that Broadcom, who acquired VMWare, who were the custodians of the bitnami catalog, did something not so nice to all of us.
In this issue, they announced that the catalog would be moved in August 2025 to a legacy catalog in favor of a 'secure' catalog and no longer updated.
This meant that the current Logs Control Easy Install project, the workshop Controlling Logs with Fluent Bit on Kubernetes, and the original article had to all be updated. I spent this last weekend and most of this week bringing all three of these artifacts up to date with a new application workload to replace the use of Ghost CMS.
Let's take a look at what these changes meant to the original article and provide you with a new guide, using Fluent Bit to get control of logs on a Kubernetes cluster.
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, using Fluent Bit tips for developers. In case you missed the previous article, check out the top 3 telemetry pipeline output plugins for developers where you get tips on the best of Fluent Bit for your developer experiences.
This article will be a hands-on tour of the things that help you as a developer testing out your Fluent Bit pipelines. We'll take a look at the top tip when using a parser for your telemetry pipeline configuration in Fluent Bit.
I'm a big fan of the All Things Open conferences and meetups, as they have been a rock star organization since they started and always put on great events in the state of North Carolina. This year is the 13th edition and I've only missed the events across the pandemic years.
The selection committee was kind enough to select one of my favorite topics that I've been working on within my current team at Chronosphere, cloud metrics and cost-value equations. Today I was on-site and gave this burst-talk session. I wanted to share the slides and my thoughts on the attendee reactions.
Today I shared some insights into the executive signal and gave some important tips that everyone can use to cut through the noise and drive change. Below I share the slides from my talk.
As I mentioned previously, I was going to speak in June at Cloud Native Manchester, but due to transit strikes in my country I was unable to make the trip over to Manchester.
The meetup is described as, "A Northern outpost for all things Cloud Native - from Kubernetes to Etcd and everything in between... If you're interested in container orchestration and all its surrounding ecosystem, then we welcome you onboard!"
Tonight I shared a rather ambitious session where, after introducing the concepts of telemetry pipelines, I let the meetup attendees choose from a list of five examples (demo scenarios). I then proceeded to share live on stage the details of how things work; Fluent Bit pipelines, integration with OpenTelemetry, integration with Prometheus, controlling logs in a Kubernetes cluster, and AI observability.
As promised, I wanted to share both the slides and talk details below.
This series is a general purpose getting started guide for those of us wanting to learn about the Cloud Native Computing Foundation (CNCF) project Fluent Bit.
Each article in this series addresses a single topic by providing insights into what the topic is, why we are interested in exploring that topic, where to get started with the topic, and how to get hands-on with learning about the topic as it relates to the Fluent Bit project.
The idea is that each article can stand on its own, but that they also lead down a path that slowly increases our abilities to implement solutions with Fluent Bit telemetry pipelines.
Let's take a look at the topic of this article, using Fluent Bit tips for developers. In case you missed the previous article, check out the top 3 telemetry pipeline input plugins for developers where you get tips on the best of Fluent Bit for your developer experiences.
This article will be a hands-on tour of the things that help you as a developer testing out your Fluent Bit pipelines. We'll take a look at the top three output plugins for your telemetry pipeline configuration.
This is SRECon25 EU and with it being in Dublin from 7-9 Oct this year, I couldn't resist submitting a few of my cloud native observability ideas. They had the entire spectrum of session types, including lightning talks, so I pushed in a few for each category.
The final selection was a few weeks back and for the second time, they seem keen to see one of my lightning talks. Let's see what they found to be the most interesting idea I pushed in for their call for papers.
