Issue with opentelemetry endpoint that contains a path about imgproxy HOT 2 OPEN

Hey @Darkle!

The IMGPROXY_OPEN_TELEMETRY_ENDPOINT format is host:port. I guess, we need to revise the OTel configuration to add support for custom endpoint paths

from imgproxy.

I revised the OpenTelemetry config in the latest build to use standard env vars when possible (have been going to do so for a long time): https://docs.imgproxy.net/latest/monitoring/open_telemetry.

Take note that imgproxy doesn't support sending logs to OpenTelemetry.

However, if you want to send request traces to Seq, you can use the latest build and set the following env vars:

• IMGPROXY_OPEN_TELEMETRY_ENABLE=1
• OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
• OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:5341/ingest/otlp" (/v1/traces will be added automatically)

Seq doesn't support collecting OTel metrics, so IMGPROXY_OPEN_TELEMETRY_ENABLE_METRICS will not work with it.

I'm not sure if the X-Seq-ApiKey header is mandatory for Seq, but if it is, set OTEL_EXPORTER_OTLP_HEADERS="X-Seq-ApiKey=your_api_key"

from imgproxy.