OpenTelemetry traces: why deprecating span events is a terrible idea
Earlier this year, the OpenTelemetry team announced the deprecation of span events. I'll explain in this article why I think it's a bad idea.
Je suis Mathieu, ingénieur expert en développement, architecture logicielle, SRE et platform engineering.
Certains articles sont uniquement en français ou en anglais — Some articles are French or English only : Français English
Earlier this year, the OpenTelemetry team announced the deprecation of span events. I'll explain in this article why I think it's a bad idea.
A few days ago I read on X this tweet from Charity Majors about the fear of deploying on Friday and agreed with her. I’ve had this "deploy on Friday" discussion several times over the years, and even proposed a talk about this topic at some French conferences a while ago (I didn’t pass the CFP :D).
I released recently Cabourotte Cabourotte v0.16.0, I added several features since my previous article (which is I think an interesting read about my motivations behind the project) which I will explain in this article, as well as the roadmap for next year.
I released last week Cabourotte 0.12.0. This release brings a couple of new features that I will detail in this article. I will also discuss why I built Cabourotte and what’s next.
When using Ansible, it’s important to define naming conventions and to apply them for all your roles and playbooks. Here are mine.
Let’s take for example HAProxy. This wonderful piece of software can be configured with hundreds of options. How to write an Ansible role to handle this, AND share this role accross multiple projects/teams/companies ?
How tu use the (by) stream in Riemann ?