renovate-runner VS opentelemetry-tracing

Use Renovate runner for GitLab.

Renovate offers instructions to install the product for GitLab. As I had to understand how Renovate works and how to install it, I had to consult quite a few sites.

This is the recommended way to run Renovate on GitLab: https://gitlab.com/renovate-bot/renovate-runner

I flew from Geneva the day before my talk and crashed into my hotel bed. Of course, I woke up very early in the morning and decided to check the demo of a talk planned for the end of the tour. It didn't work, so I tried to remove the stopped containers. Tired as I was, I deleted all my Docker images, including the ones I'd need a few hours later for my talk on OpenTelemetry!

Last year, I wrote a post on Open Telemetry Tracing to understand more about the subject. I also created a demo around it, which featured the following components:

I decided to give it a try. I'll use the root commit of my OpenTelemetry tracing demo. Let's execute the proposed command:

The OpenTelemetry Collector sits at the center of the OpenTelemetry architecture but is unrelated to the W3C Trace Context. In my tracing demo, I use Jaeger instead of the Collector. Yet, it's ubiquitous, as in every OpenTelemetry-related post. I wanted to explore it further.

One of the components of my OpenTelemetry demo is a Rust application built with the Axum web framework. In its description, axum mentions:

It's always a good idea to check that the design behaves as expected. We can use OpenTelemetry for this. For more information on how to set up OpenTelemetry in such an architecture, please refer to End-to-end tracing with OpenTelemetry.