Change deprecated OTel jaeger exporter

[oguzhand95]

"go.opentelemetry.io/otel/exporters/jaeger" is deprecated: This module is no longer supported. OpenTelemetry dropped support for Jaeger exporter in July 2023. Jaeger officially accepts and recommends using OTLP. Use [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp] or [go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc] instead

[muratmirgun]

Hey I can take this issue

[emreb]

Please do. Looking forward to receiving the PR.

[muratmirgun]

Guys, I found this in the releases

The go.opentelemetry.io/otel/exporters/jaeger package is deprecated.
OpenTelemetry dropped support for Jaeger exporter in July 2023.
Use go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
or go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc instead.

I will make implementation with "go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp" that's okay with us?

[haines]

We already support otlptracegrpc so I don't think there is anything to be done for this issue, other than we may wish to mark the jaeger exporter as deprecated in our tracing configuration so that we can remove it in a future release.

[muratmirgun]

Yes, that is correct. Now you can use it with the otlp client on the Jeager side. We can remove the Jeager option and write this information to Docs. I can open PR for the remove Jeager client side. Or we can additionally add HTTP as an option to grpc

[haines]

I think we should start by documenting the Jaeger exporter as deprecated first, then remove it in a future release, so that anybody who is currently using it has some warning before it disappears.

Let's change the comment on the config section to be prefixed with [Deprecated] and include a note that the OTLP exporter should be used instead because Jaeger now supports OTLP.

cerbos/internal/observability/tracing/conf.go

Line 29 in f134903

// Jaeger configures the Jaeger exporter.

That'll show up in the full configuration docs at https://docs.cerbos.dev/cerbos/latest/configuration/#_full_configuration

Then, let's also update the docs with a similar note about using the OTLP exporter instead.

cerbos/docs/modules/configuration/pages/tracing.adoc

Line 7 in f134903

The system to export the trace data must be specified using the `exporter` setting. Currently link:https://www.jaegertracing.io[Jaeger] and link:https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md[OTLP collectors] are supported. If using Jaeger, traces can be sent to either a Jaeger Agent (compact Thrift format) or a Jaeger Collector (Thrift format).

Let's also move the OTLP section above the Jaeger one so it has more prominence.

That'll show up at https://docs.cerbos.dev/cerbos/latest/configuration/tracing

I think it would be reasonable to support HTTP as well as gRPC. We could add a Protocol field to the config that would default to "grpc" but could also be set to "http/protobuf" (per the docs they also have an "http/json" protocol, but we won't support that because their Go SDK doesn't support that).

https://github.com/cerbos/cerbos/blob/main/internal/observability/tracing/conf.go#L50-L53

Hope that helps you get started @muratmirgun! Thanks for contributing 🙇

[muratmirgun]

Thanks for the info. I am working on it 🚀