Get back the OpenTelemetry Integration Support to the community version

[aalmazanarbs]

What would you like to be added or enhanced?

We would like to understand the rational behind the removal of the OpenTelemetry integration support from the version 5.8.3 and on. We understand that features that provides enterprise capabilities are suitable to be under the enterprise licensing but, OpenTelemetry support is a broad de-facto standard part of multiple opensource solutions.

Thanks in advance.

Why is this needed?

We need to forward metrics to opentelemetry open source collector.

[seinshah]

Hi EMQX team,

Is there any plan to bring this back? We relied on collecting open telemetry metrics and defined alerts in our pipelines to stay on top of any potential issues that may arise. Removing this feature from the OSS version would break our pipeline.

Also, removing features after initially introducing them introduces serious concerns for future adaptability.

[gujun720]

Hi @aalmazanarbs @seinshah ,

The OpenTelemetry integration is now an enterprise usability feature. You can rely on the EMQX dashboard for monitoring when using the community version.

Regards.

[aalmazanarbs]

Hi @gujun720,

We know that we can check the EMQX dashboard but this is not the aim. Our purpose is to track distributed tracing in our system and EMQX is a component of our system, so if we have 2 applications communicating with each other using EMQX, we want to know that EMQX was there. We are sending EMQX and applications OpenTelemetry to Zipkin.

Regards.

[igkg]

It is not just about monitoring. It is about back-compatibility. For example, we use the pgo component (which uses OpenTelemetry) in our plugin, and the new version of emqx doesn't work with it, even though we don't use OpenTelemetry explicitly.