Observability 🔭 at KubeCon CloudNativeCon EU 2024 Paris

Greetings from KubeCon + CloudNativeCon Europe! It was a wild and awesome ride last week! [Ken](https://www.linkedin.com/in/ken-hamric-016b1420/) and I had a blast at both the Co-Located Observability Day on Tuesday, as well as during the main conference! I have a lot to share. Here’s a recap of how the observability community has grown in Europe since last year.

## KubeCon + CloudNativeCon Venue

KubeCon + CloudNativeCon Europe 2024 was in Paris the week of March 18th. I thought it would be interesting to recap some of the events from the Tracetest team’s perspective with an eye towards Observability.


First, the venue [Paris Expo Porte de Versailles](https://maps.app.goo.gl/gWXq6EaZzMnWfsMZ6?g_st=ic), was beautiful. Our team had a booth on the main floor, but also attended the co-located Observability Day event prior to the main conference.

The Observability Day got two rooms this year! Finally! Here’s what the main room looked like at 8:30 before it got packed to the brim when the talks started. Absolutely massive!


## Observability Day and OpenTelemetry

Let me start off by discussing Observability Day. The agenda was packed with informative sessions and discussions that shed light on the latest trends and advancements in observability.

The CNCF finally provided a second room to have more sessions and accommodate the number of interested people!

### Opening session by OpenTelemetry community committee members

[Austin Parker](https://www.linkedin.com/in/austinlparker/), Honeycomb, [started off the co-located event](https://colocatedeventseu2024.sched.com/event/1YGT9/observability-day-welcome-project-updates-eduardo-silva-fluentbit-austin-parker-honeycombio). He covered OpenTelemetry project updates and future goals.


Most notable were updates to:

- Stability
- Events & RUM
- Continuous profiling

Since last Observability Day 2023 in Chicago, 4 more languages have been marked stable!


Events will be optimized for real-user monitoring!


Profiling will be added this year!


But the biggest bombshell is that OpenTelemetry has applied for graduation in the CNCF.


[Eduardo Silva](https://www.linkedin.com/in/edsiper/), Chronosphere, then took the stage to talk about updates happening in the world of FluentBit.


He covered latest updates and the roadmap for 2024.

[Pavol Loffay](https://www.linkedin.com/in/pavolloffay/) (Red Hat) and [Jonah Kowall](https://www.linkedin.com/in/jkowall/) (Aiven) covered exciting updates to Jaeger.


The roadmap looks awesome!


As do the v2 goals!


This was a great segue into the more technical presentations of the day.

We did catch all the sessions at Observability Day, but I want to share some of my favorites with you.

### Hey OpenTelemetry, where’s my error!?

[Dude, Where’s My Error?: How OpenTelemetry Records Errors, and Why It Does It Like That](https://colocatedeventseu2024.sched.com/#) — The session presented by [Reese Lee, New Relic](https://www.linkedin.com/in/reese-lee/) & [Adriana Villela, ServiceNow](https://www.linkedin.com/in/adrianavillela/).

They emphasized the importance of tracking errors and understanding system functionality for user satisfaction. They used a demo to showcase OTel's error logging, metadata-enhanced troubleshooting, and the difference between errors and exceptions. The session explained error visualization across different backends and the effect of different span kinds on error reporting.


### How to think about overhead?

[How to Think About Instrumentation Overhead](https://colocatedeventseu2024.sched.com/#) — [Jason Plumb (Splunk)](https://www.linkedin.com/in/jasonplumb/) did an amazing talk on instrumentation overhead in an observability context. Novice observability practitioners who were previously overly obsessed with performance had approached instrumentation with skepticism due to concerns about latency degradation or resource consumption.


The causes of overhead were covered, illustrating why it is difficult to measure and predict. Jason also showcased practical techniques for understanding overhead in one's environment and strategies for coping with it were presented.

### FluentBit vs. OpenTelemetry Collector

[Telemetry Showdown: Fluent Bit Vs. OpenTelemetry Collector - a Comprehensive Benchmark Analysis](https://colocatedeventseu2024.sched.com/#) —  [Henrik Rexed](https://www.linkedin.com/in/hrexed/), Dynatrace.

In a push to standardize observability practices, the cloud-native community has embraced OpenTelemetry, offering a unified framework for metrics, logs, and traces. In the past log processing relied on agents like Fluentd, evolving into FluentBit. With FluentBit's recent expansion to support additional signals and the rise of OpenTelemetry Collector, a question arises: "Which is the superior choice for performance?"


Henrik explained the performance differences, ease of use, compatibility, and more!

### Improving Serverless monitoring at Google

[Monitoring Serverless Workloads with OpenTelemetry and Prometheus](https://colocatedeventseu2024.sched.com/event/1YFhh/monitoring-serverless-workloads-with-opentelemetry-and-prometheus-ridwan-sharif-google) - [Ridwan Sharif](https://www.linkedin.com/in/ridwanmsharif/), Google.

In this presentation Ridwan explained the challenge with observability and serverless platforms. To enable OpenTelemetry tracing and Prometheus-based metrics in Google's Cloud Run they had to implement new updates to sidecars in Cloud Run.


This enabled flushing push-based OpenTelemetry traces before containers were killed. But also scraping with Prometheus. This presentation explains how these improvements to Cloud Run enabled the use of open-source observability tooling to improve serverless observability.

### What's a good OpenTelemetry mindset?

[Shift Into an Observability Mindset with OpenTelemetry](https://colocatedeventseu2024.sched.com/event/1YFjB/shift-into-an-observability-mindset-with-opentelemetry-daniel-gomez-blanco-skyscanner) - [Daniel Gomez Blanco](https://www.linkedin.com/in/danielgblanco86/), Skyscanner.


Daniel covered an amazing topic. Embracing observability in your organization.

To do so, you must shift your mindset to rethink monitoring and debugging practices. This means moving to OpenTelemetry and communicating the value of OpenTelemetry as the ideal tool for the job both today and moving forward. Daniel also covered adoption best practices as well. Can't wait to get the recording and re-watch this amazing talk.

### How to build dynamic OpenTelemetry Collector configs?

[OpAMP in Action: User Configurable Observability Pipelines](https://colocatedeventseu2024.sched.com/event/1YFk6/opamp-in-action-user-configurable-observability-pipelines-srikanth-chekuri-signoz) - [Srikanth Chekuri](https://www.linkedin.com/in/tinyidly/), SigNoz.


Observability pipelines using OpenTelemetry Collector can't be configured dynamically. This means you need to restart the collector when the config is changed. With OpAMP you can bypass this to build dynamic user configurable observability pipelines!

## Observability Vendors at KubeCon

Moving on, let's explore the diverse range of observability vendors present at KubeCon in Paris this year. I counted 29 vendors who set up booths, each offering unique solutions and perspectives.

- [Tracetest](https://tracetest.io/)
- [OpenTelemetry](https://opentelemetry.io/)
- [Honeycomb](https://honeycomb.io/)
- [Grafana](https://grafana.com/)
- [Datadog](https://www.datadoghq.com/)
- [OpenSearch](https://opensearch.org/)
- [Tyk](https://tyk.io/)
- [Prometheus](https://prometheus.io/)
- [Dynatrace](https://www.dynatrace.com/)
- [New Relic](https://newrelic.com/)
- [Splunk](https://www.splunk.com/)
- [Elastic](https://www.elastic.co/)
- [Edge Delta](https://edgedelta.com/)
- [Chronosphere](https://chronosphere.io/)
- [Calyptia](https://Calyptia.com)
- [Victoria Metrics](https://victoriametrics.com/)
- [Logz](https://logz.io/)
- [Fluentbit](https://fluentbit.io/)
- [Lumigo](https://lumigo.io/)
- [Coralogix](https://coralogix.com/)
- [Axiom](https://axiom.co/)
- [StackState](https://www.stackstate.com/)
- [Sentry](https://sentry.io/welcome/)
- [Dash0](https://www.dash0.com/)
- [Highlight](https://www.highlight.io/)
- [ManageEngine](https://www.manageengine.com/)
- [Kloudfuse](https://www.kloudfuse.com/)
- [Axoflow](https://axoflow.com/)
- [Groundcover](https://www.groundcover.com/)

As promised, I have compiled a collection of photos to give you a glimpse into the vibrant atmosphere and impressive setups.

[Check out the video on YouTube, here.](https://www.youtube.com/watch?v=g58GB_YVbM8)

## Interviewing OpenTelemetry Maintainers, Approvers, and Contributors

I had the chance to talk to OpenTelemetry community members about their experience and work in the community. The interviews include [Juliano Costa](https://www.linkedin.com/in/julianocosta89/) (OpenTelemetry Demo maintainer), [Kayla Reopelle](https://www.linkedin.com/in/kaylareopelle/) (OpenTelemetry Ruby Approver), and [Adriana Villela](https://www.linkedin.com/in/adrianavillela/) (OpenTelemetry Contributor).

[View the video with OpenTelemetry Demo Maintainer Juliano Costa, here.](https://www.youtube.com/watch?v=vgBKuSMa5J0)

Stay tuned for a complete case study with the OpenTelemetry maintainers!

## Fostering a Sense of Community

In the world of observability, it's super cool to see how vendors, even while competing, come together like old friends. It’s awesome to witness these bonds and collabs, giving the whole scene a cozy, tight-knit vibe.

Need proof? Check out how folks from ServiceNow and New Relic teamed up for sessions, not to mention how Google engineers are committed to open-source observability!

At Tracetest, we’re neutral like Switzerland within the OpenTelemetry ecosystem, emphasizing on trace-based testing. Our approach is focused on bridging the existing gaps in the development process, by offering two advantages. Firstly, we provide a trace for every test run, enhancing the observability in testing. Secondly, we enable integrations with testing frameworks such as Cypress, Playwright, k6, and Artillery, allowing developers to get a peek into the black box. It’s about making testing less of a headache and more enjoyable because you can finally see what’s going on!

## Where do we go from now?

Now once we're all back from KubeCon in Paris, let’s continue the discussion and try contributing even more to the OpenTelemetry project. The OpenTelemetry project has filed for graduation in the CNCF.

Our team has been active in the last year, with numerous PRs, both code contributions and content for the OpenTelemetry blog. I am hoping we can ramp up even more and help the developer community embrace OpenTelemetry, making it easier than ever to get started.

## What do you think?

I’ve shared my thoughts and experiences from KubeCon. Let me hear your ideas as well! What topics would you like to see covered? Feel free to reach out and share your suggestions!

Do you want us to contribute to something specific in the OpenTelemetry project?
Do you need a specific feature in Tracetest to help you work with OpenTelemetry?
There are no bad ideas!

I’m eager to hear your thoughts. Feel free to reach out to me any way you prefer! I am active on LinkedIn daily and happy to answer questions or just chat about OTel.

- [LinkedIn](https://www.linkedin.com/in/adnanrahic/)
- [Slack](https://dub.sh/tracetest-community)
- [Contact Form](https://tracetest.io/contact)

## See you at KubeCon North America in Salt Lake City!

To wrap it up, KubeCon was a super exciting experience. The observability vendors showed off their skills, and the awesome sense of community was all about working together and contributing to OpenTelemetry.

If you enjoyed this post, share it with your friends!

Feel free to connect with us on [social media](https://www.linkedin.com/company/tracetest), join our [Slack community](https://dub.sh/tracetest-community), and give us a [⭐ on GitHub](https://github.com/kubeshop/tracetest).

‍