Background

In both internal and customer discussions, there's a concern regarding the impact on system performance when changin observability stacks. But that discussion needs to be based on data, facts and it shall also be trackeable. For example, it may happen that some technology is not good enough today, but it gets fixed in a couple of months. We should have the ability to revisit these, again, based on data and facts.

Description

This requirement is a placeholder to group benchmarks performed by the distributed tracing team regarding comparisons between OTEL collector and other pieces of the observability stack for collecting, processing and exporting metrics and logs. Distributed tracing is out of this scope because there's not an alternative being considered today.