Description:

When running the Envoy AI Gateway in host/standalone mode with Docker Compose (otel‑tui profile), OTLP logs never reach otel‑tui even though traces and metrics do. The gateway is configured to export access logs via OTLP gRPC to the otel‑tui collector, but the log pipeline is silently dropped because the backend hostname for logs uses a single‑label name (otel-tui).

In host/standalone mode, the backend hostname validation rejects single‑label hosts (except localhost), so the access log backend fails validation and Envoy Gateway omits the access_log configuration entirely. This breaks docker‑based setups that use Compose service names for OTLP log sinks; logs appear only when switching to console exporter or using a dotted hostname like host.docker.internal.

Relevant Links

#6503
#7427