Mubashir Osmani d0db267f40 test(e2e): add datadog log-delivery e2e scenarios ... Drive real traffic through the proxy and read the events back out of the Datadog Logs Search API to prove delivery instead of trusting the proxy. The DatadogClient reads DD_API_KEY, DD_SITE and DD_APP_KEY from the environment and polls the search API for a per-run marker stamped into each request Three scenarios cover the contract: a batch of gpt-5.5 chat completions shipped with no drops, the /v1/responses path on a claude-haiku-4-5 deployment exercising the Responses-to-Anthropic translation, and a failed request that must land as an error event. The e2e compose config enables the datadog (and prometheus) callback so the delivery path is actually exercised, and the suite skips unless all three credentials are set		2026-07-07 22:32:41 -04:00
..
conftest.py	test(e2e): add datadog log-delivery e2e scenarios	2026-07-07 22:32:41 -04:00
logging_client.py	test(e2e): add datadog log-delivery e2e scenarios	2026-07-07 22:32:41 -04:00
test_datadog_e2e.py	test(e2e): add datadog log-delivery e2e scenarios	2026-07-07 22:32:41 -04: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