litellm/tests/e2e/logging
mubashir1osmani 4673754857 test(e2e): run arize_phoenix suite on the otel_v2 pipeline
The logging client registers the suite's Claude deployments at build time and
tests call models by their plain provider-qualified names. Phoenix read-back
uses the same env vars as the proxy's arize_phoenix integration and matches
generation spans by span kind plus a unique prompt marker, since otel_v2 names
spans "chat {model}" and leaves successful spans' status UNSET. The compose
stack passes the phoenix env through and opts into span message content so
prompts and completions land on traces; the shared conftest loads tests/e2e/.env
so bare pytest runs work locally
2026-07-13 18:16:15 -07:00
..
conftest.py test(e2e): add arize_phoenix logging suite with duplicate trace detection 2026-07-13 11:38:37 -07:00
logging_client.py test(e2e): run arize_phoenix suite on the otel_v2 pipeline 2026-07-13 18:16:15 -07:00
test_langfuse_e2e.py test(e2e): run arize_phoenix suite on the otel_v2 pipeline 2026-07-13 18:16:15 -07:00
test_logging_arize_phoenix.py test(e2e): run arize_phoenix suite on the otel_v2 pipeline 2026-07-13 18:16:15 -07:00
test_prometheus_cardinality_e2e.py test(e2e): close coverage gaps across chat/responses, provider features, batches, prometheus, and langfuse eviction (#32165) 2026-07-04 18:56:52 -07:00