Description:

Right now, our examples and docs suggest running arize phoenix without authentication as it is just a quick start:

• https://aigateway.envoyproxy.io/docs/capabilities/observability/tracing
  • from https://github.com/envoyproxy/ai-gateway/blob/main/site/docs/capabilities/observability/tracing.md#install-phoenix-for-llm-observability
• https://github.com/envoyproxy/ai-gateway/blob/main/cmd/aigw/docker-compose-otel.yaml#L30

These docs say to use normal otel config for full scope:

• https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/

However, docs don't give an example of additional config, notably auth config. I think it is just setting these ENV variables according to phoenix docs, adding a couple to remind that this is tracing-only.

OTEL_EXPORTER_OTLP_ENDPOINT=http://your_phoenix:6006
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer YOUR_API_KEY
OTEL_RESOURCE_ATTRIBUTES=project.name=YOUR_PHOENIX_PROJECT_NAME
# Phoenix does not support OTLP metrics or logs
OTEL_METRICS_EXPORTER=none
OTEL_LOGS_EXPORTER=none

Possibly having a file somewhere .env.otel.phoenix could help on a common question and link back to it in both places (k8s and docker docs)? Regardless, it should be tested with our examples prior to documenting, though I wouldn't recommend making our examples start phoenix as authenticated as it adds login steps that are annoying for a demo.

cc @mikeldking