Support OTEL over HTTP for Access Logs

[arkodg]

          @zirain any plans on doing otel over http?

writing a grpc service just to get the access log looks like overkill to me...

Originally posted by @pkit in #701 (comment)

[zirain]

In most of the cases, otel-collector is the best choice as a backend/transit.

[ShyunnY]

Maybe I can try this working!

[pkit]

In most of the cases, otel-collector is the best choice as a backend/transit.

Do you mean I need to fork the collector, create custom backend, compile, build, deploy, etc.?

[zirain]

otel-collector support both http and grpc, see the configuration here, you can use it as intermediary agent send to other exporters(e.g. another otel backend but http protocol).

[pkit]

Yeah. Ok. Thanks.

[ShyunnY]

When I looked through the documentation, it seems that the configuration in OpenTelemetryAccessLogConfig.common_config does not support us to choose HTTP protocol for export. ref

[zirain]

You can extend it to support HTTP, just as OpenTelemetry tracer do.

[ShyunnY]

您可以扩展它以支持 HTTP，就像 OpenTelemetry 跟踪器一样。

I started working on this and I don't quite understand it. Do we need to enhance and extend this in Envoy?

[zirain]

您可以扩展它以支持 HTTP，就像 OpenTelemetry 跟踪器一样。

I started working on this and I don't quite understand it. Do we need to enhance and extend this in Envoy?

bingo!

[ShyunnY]

您可以扩展它以支持 HTTP，就像 OpenTelemetry 跟踪器一样。

I started working on this and I don't quite understand it. Do we need to enhance and extend this in Envoy?

bingo!

This seems to be a challenge for me, because I am not familiar with cpp and find it difficult to see this activity.