quarkus.otel.exporter.otlp.enabled property not documented in guides/all-config

[Ricardo Peironcely]

Hello community.

I've discovered that quarkus.otel.exporter.otlp.enabled property is not documented in all-config guide but it is referred in opentelemetry guide

It is the same for the 3.8 and 3.12 versions.

Is this something intentional about this property? 
If not, what is the correct way to include this property in all-config reference page

Best regards

Rick Peironcely

[Georgios Andrianakis]

cc @Bruno Baptista 

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAJd9y_Yz0svH%2BEHGX_yVRXS%3D0mbMfWc9%3DscR33_th7XiNgvGGQ%40mail.gmail.com.

--

Georgios Andrianakis

Independent Contractor

[Bruno Baptista]

Nice catch!
That property is actually deprecated and should be removed both from the code and the documentation. 

The property still works and the behaviour be removed.

Cheers

Bruno

[Ricardo Peironcely]

Then you’re creating a dilema in me.

How to remove the output export, but let the instrumentation there generating traces internally?

Un saludo / Best regards / С уважением

Ricardo Peironcely

Enviado desde mi móvil, disculpas por la brevedad.
This mail was sent from mobile, sorry for being brief
Написано на мобильном, приношу извинения за краткость.

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/d15b5696-8cf8-477a-be13-6ef7ab002e09n%40googlegroups.com.

[Bruno Baptista]

Hi Ricardo, 

You can set the exporter to none, therefore you will keep OpenTelemetry working under the hood but no data will be sent out.

Please use this property:

quarkus.otel.traces.exporter=none

Will update that part of the documentation. Other people might have the same question.
Regards

Bruno Baptista