Every source GILD analyzed, newest first. Each says who the source is, how it knows, whether it still applies and which findings it counts toward. Open a count to see only its sources.
Source
43 sources in Teams and technical leaders, with product documentation Showing all 78 sources
Positive
Datadog or Arize as the SaaS choice at workPost on X
Says that at the author's workplace, Datadog, Arize or a similar hosted service is the best option for agent observability.
"Same here at my workplace. Datadog, Arize or similar SaaS are the best options there."
Positive
Introducing AgentHub: Booking.com Platform for Modular Travel AI AgentsEngineering blog post, Booking.com ML & DS Blog
Booking.com logs every AgentHub interaction with OpenTelemetry, covering prompts, context, tool calls, and agent transitions. It stores the traces in its internal systems and in Arize, which the team uses for deep debugging and monitoring.
Mixed
Self-hosted Phoenix and Langfuse side by side over OTLPReddit comment, r/mlops
The commenter's team runs self-hosted Phoenix and Langfuse in its projects, publishing every call, piece of feedback, tool call and agent-to-agent call over OTLP gRPC, with custom model pricing on both. Langfuse is better for evals, dataset building and prompt versioning; Phoenix is about as capable, and choosing it is personal preference.
Positive
feat(observability): export traces over OTLP and link them to Phoenix instead of LangfuseGitHub pull request
Moved Bayes Impact's platform from a 673-line Langfuse exporter to plain OTLP, with an OpenTelemetry Collector mapping spans to OpenInference for Phoenix. Plans to keep Langfuse read-only for 30 days, since Phoenix deletes traces after 30 days.
Negative
chore(evals): Delete the Phoenix eval runnerGitHub pull request
Deleted Apify's Phoenix eval runner after Langfuse-based two-tier gates replaced it. The runner had not run in CI since, and the Phoenix client's peer dependency on an old Anthropic SDK conflicted with the Claude Agent SDK.
Mixed
Can the image dependencies for an offline/air-gapped Phoenix deployment be simplified?GitHub discussion
Phoenix's container build pulls four external images and a WASM binary that an air-gapped site must mirror; their team found the PyPI wheel works and asked if that is supported.
Mixed
spike(observability): compare Traceway, Tempo, Langfuse, Phoenix, SigNoz and Grafana Agent ObservabilityGitHub issue
Rates Phoenix as self-hostable with strong datasets, evals, and experiments, but flags its source-available license and fit as an eval specialist beside a general trace store.
Mixed
[kbn-evals] Remove Arize Phoenix executor and @arizeai/phoenix-client dependencyGitHub pull request
Kibana's eval framework launched on Phoenix for datasets and experiments; once an in-Kibana executor stored them in Elasticsearch, the team removed the Phoenix path.
Positive
Building Closed-Loop Evals for a Multimodal Agent at Uber ScaleConference talk with transcript, AI Engineer World's Fair 2026
Uber logs every stage of its food-photo agent as one flat record per case, so technical and non-technical staff can diagnose single cases and roll results up in aggregate. Chopra names Arize as the observability platform the team uses.
Positive
PagerDuty for AI: How the SRE Agent Triages AI IncidentsEngineering blog post, PagerDuty engineering blog
PagerDuty's Insights Agent has several Arize monitors that open a PagerDuty incident when breached. During triage the team's SRE Agent filters the Arize project for the offending traces and summarizes the eval explanations before it proposes prompt changes. The team notes that judge evals can be noisy when few traces are scored.
Mixed
[ENHANCEMENT]: Support attaching images to non-LLM spans (TOOL/CHAIN) without faking LLM message attributesGitHub issue
Their team traces an OCR and vision pipeline in Phoenix, but images render only on LLM spans, so they fake LLM spans to see them.
Mixed
Auto-evals: Braintrust Loop, Arize Alyx and LangSmith on the same 100 tracesIndependent evaluation, Parlance Labs blog
Parlance Labs masked hand labels on 100 production traces and asked each platform's agent to find the failures. Alyx missed more failures than Braintrust Loop, but 91% of its flags were valid and only three were wrong; early runs read only the first 200 characters of each trace.
"The workflow had rough spots. Alyx initially read only the first 200 characters of each trace, and later runs hit compaction and timeout problems. The Arize team resolved each issue quickly once we reported it."
Not counted
Its author already has two counted records on this product. Kept in the record; it takes part in no figure.
Positive
From Traditional ML to AI Agents: How Booking.com Scales AI Observability With Arize AIEngineering blog post, Booking.com ML & DS Blog
Booking.com sends traces from its agents and prediction logs from its ML models into Arize through a central OpenTelemetry collector that redacts PII. An Arize latency monitor caught an agent running without a service tier, and comparing token counts in Arize exposed context bloat in an itinerary agent before it reached production.
Mixed
After three months comparing Galileo, Arize, Langfuse, and LangSmith, the team chose Langfuse. It found Phoenix good for tracing and easy to run locally, but the full Arize platform aimed at larger ML teams.
Positive
Automating and Optimizing Financial Signal Discovery with Multi-Agent SystemsEngineering blog post, NVIDIA Technical Blog
The team traces its long-running signal discovery agents in Phoenix to watch LLM reasoning and token use in real time and to find whether a bottleneck sits in the model's logic.
Counts toward
Negative
chore: remove Arize Phoenix (telemetry / observability) from VSSGitHub pull request
NVIDIA's blueprint team removed Phoenix, an optional tracing exporter, because it added a container and dependencies they did not want to maintain; OpenTelemetry stays for future exporters.
Mixed
BulkInserter opens up to 7 DB sessions per loop iteration, exhausting connection pool under loadGitHub issue
Under sustained ingest on two self-hosted replicas, Phoenix's bulk inserter opened up to 7 database sessions every 100 ms and exhausted the connection pool. The author offered a fix that uses one session per loop.
Mixed
Slow trace and span search performance when searching by spans.attributesGitHub discussion
At about 100,000 LLM interactions a day on Kubernetes and Cloud SQL, filtering traces by metadata such as app or team is slow over a 24-hour window.
Positive
Flag Early, Fix Faster: Real-Time Intervention for Supplier Transfers with WilmaEngineering blog post, Wayfair tech blog
Wayfair's Wilma clears about 65% of supplier-transfer tickets; besides human feedback and offline evals, Arize gives trace-level visibility, rapid debugging, and alerts on metric shifts.
Negative
fix(aihub): Replace Arize Phoenix with open source alternativeGitHub pull request
Proposed replacing Phoenix with Langfuse because Phoenix's Elastic License blocks including it in a SaaS offering. The existing OpenInference instrumentation keeps working with Langfuse, and the team merged the switch in February 2026.
Mixed
A pragmatic guide to LLM evals for devsNewsletter guest post, The Pragmatic Engineer
Shows a NurtureBoss agent trace in Arize Phoenix. Calls generic tools such as Arize a decent start for reviewing data, but they proved cumbersome for the team's context, so it spent a few hours building its own viewer.
Mixed
Evaluating AI Agents with DeepEval and Arize Phoenix: Lessons from Our Integration JourneyEngineering blog post, Codify blog
Codify traces its agents in Phoenix and scores them with DeepEval. Phoenix helps diagnose failures, but past experiment results needed manual database queries, concurrency above 1 errored, and docs were thin or outdated.
Positive
Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardHacker News comment
Evaluated many tools for a small startup in early 2025; Phoenix was the only one that worked out of the box and used OpenTelemetry the right way.
Mixed
Expand RBAC To Limit Access To ProjectsGitHub discussion
Their team sends dev, QA, and production traces to one Phoenix instance and wants each group limited to its own project, which Phoenix's admin and member roles cannot do.
Positive
PagerDuty + Arize: Building End-to-End Observability for AI Agents in ProductionEngineering blog post, PagerDuty engineering blog
PagerDuty traces its agents in Arize, runs golden-dataset experiments as regression tests, scores production traces for relevance and groundedness, and pages on-call when an Arize monitor breaches.
Not counted
It was co-written with Arize's partner solutions director as a joint partner post. Kept in the record; it takes part in no figure.
Mixed
Old logs are getting deleted when the number of log request is highGitHub discussion
Logging thousands of LLM calls from a high-throughput app, their team sees older traces disappear from Phoenix even after tuning batch export settings.
Positive
Add support for Arize Phoenix for LLM observability and evaluationGitHub issue
Their team runs Phoenix alongside Open WebUI and asked for a native Phoenix pipeline, since both speak OpenTelemetry.
Negative
The NonBioS LLM Observability PickCompany blog post, NonBioS
NonBioS looked briefly at Phoenix but found the Phoenix versus Arize naming confusing and the website hard to use, and chose self-hosted Langfuse.
Positive
Optimizing LLMs in Insurance with DSPy: Beyond Manual TuningConference talk with transcript, AI Engineer World's Fair 2024, video published February 2025
The AXA team logged no traces at first and could not see how its LLM calls fit together. Adding open-source Phoenix helped a lot in showing which calls were bundled together and what ran behind the framework's abstractions.
No opinion stated
PromptVersion.format() fails on developer messages for Anthropic and GoogleGitHub issue
Phoenix's prompt client raises a bare NotImplementedError when a prompt holds a developer message and the target is Anthropic or Google, for native prompts and for OpenAI prompts formatted for those providers.
No opinion stated
Phoenix's simple architecture for tracing, other tools for evalsHacker News comment
Has used only Phoenix, calls its architecture extremely simple and its tracing nice, and would use a separate tool for evaluations, datasets and prompts.
"I only used Phoenix. Its architecture is extremely simple. Tracing is nice, I didn't have any complaints. All other features like evaluations, datasets, prompts - I'd use a separate tool for this."
No opinion stated
Phoenix project page slows to seconds per load at 2.4 million root spansGitHub issue
On PostgreSQL 16 with about 2.4 million root spans, schlaepf measured each load of a Phoenix project page at 3.5 seconds or more, whatever time range was selected.
"On PostgreSQL 16 with ~2.4M root spans this costs ~3.5-4s per load regardless of the selected range."
No opinion stated
Experiment results lose their evaluator definition when every attempt throwsGitHub issue
Reports that Phoenix repeats each evaluator's definition inside every result's metadata, so an experiment whose attempts all throw has no result left to carry the definition.
"Today we repeat this definition inside every result's metadata. If every attempt throws before returning, none of those results can supply the definition."
No opinion stated
Arize, Langfuse and Braintrust all intimidating at firstPost on X
Tried Arize, Langfuse, Braintrust and others and found almost all of them intimidating at the start; Langfuse was the easiest to get going.
"I have tried out all the existing tools like Arize, langfuse, braintrust etc and almost all of them are quite intimidating to use in the beginning (langfuse was the easier one to get started)."
"I have tried out all the existing tools like Arize, langfuse, braintrust etc and almost all of them are quite intimidating to use in the beginning (langfuse was the easier one to get started)."
No opinion stated
First Phoenix trace showed a coding agent retrying a failing test 9 timesPost on X
Erik Fiala's first traced session in self-hosted Phoenix showed his Claude Code loop quietly retrying a failing test 9 times before reporting it green.
"…finally put tracing on my claude code loops with phoenix (open source, self-hosted otel) and first session showed the agent quietly retrying a failing test 9 times then reporting it green."
Positive
feat: enable Phoenix tracing in production deploymentsGitHub pull request
Added an opt-in Phoenix overlay to production deployments, with Phoenix on loopback, its own trace volume, prompt and response capture off by default, and no dependency from inference on it.
Negative
fix: disable Phoenix tracing in production, gated behind PHOENIX_ENABLEDGitHub pull request
Turned off Phoenix tracing in production after it contributed to instability three times: unexplained gRPC export attempts and timeouts competed with live chat requests for CPU.
Positive
feat(phoenix): add Arize Phoenix as a second OTLP trace sinkGitHub pull request
Added self-hosted Phoenix beside Langfuse as a second OTLP sink, choosing it over Helicone because Phoenix ingests OTLP, has no license key or feature gating, and ships releases weekly.
No opinion stated
Separating tool-call cost from tool-output cost in PhoenixReddit post, r/AI_Agents
Building cost tracing on Phoenix for a LangChain app, the poster wants each step priced separately: the model call that writes a tool call, the tool run, the tokens its output adds to the next request, and the final answer. The poster's example trace, a sketch of the instrumentation they want rather than a measured run, separates 850 estimated tool-output tokens and 3.49 seconds of tool latency.
Positive
Add backend OpenTelemetry tracing with PhoenixGitHub pull request
Added fail-open OpenTelemetry tracing from the agent backend to Phoenix over the standard OTLP/HTTP exporter, with one root span per chat turn, bounded batch export, sampling, and content redaction.
No opinion stated
Wants reusable Phoenix interface componentsPost on X
Says Phoenix can be forked for a custom viewer, wishes it shipped a reusable component set, and says he is building one.
"You can fork it and do just that, but I agree, something like a re-usable Arize Phoenix component set would be sweet! I have been working on exactly this…"
Positive
feat: self-hosted OTel observability (Phoenix/Langfuse) for multi-agent tracing - not LangSmithGitHub issue
Recommends self-hosted Arize Phoenix for multi-agent tracing in their harness, with zero data egress, after ruling out LangSmith; self-hosted Langfuse is the fallback.
Positive
feat(evals): host Phoenix on Cloud Run and Cloud SQLGitHub pull request
Hosted Phoenix on Cloud Run with Cloud SQL, with authentication on from the first deploy. The author passed on Phoenix Cloud because the SaaS would move eval data out of the project.
Positive
feat(observability): standardise on Phoenix; restore Langfuse v4 as fallbackGitHub pull request
Made self-hosted Phoenix their default over Langfuse v4: one container using about 400 MiB on Postgres against four containers using 1,848 MiB, with prompt versioning, datasets, experiments, and evaluators. Martinez turned on authentication and a 90-day retention, which Phoenix ships off and unbounded.
Counts toward
Mixed
Comment on: A CLI that shows which sub-agent burned your tokens in one runHacker News comment
Built a CLI over OpenInference spans because Phoenix shows cost per span and per project but nothing in between, so explaining one run's cost means reading the trace tree.
Positive
Evaluate Agents Locally with Arize Phoenix (Hands-On Guide)Personal blog post, folarin.dev
Calls Phoenix the easiest way Akinloye knows to get LangSmith-style tracing and evals without sending data to anyone's cloud; an afternoon of setup gives traces and judged scores.
Positive
Add Arize Phoenix integration for LLM tracing and evalsGitHub pull request
Sent AI SDK spans to both the existing collector and Phoenix Cloud, and recorded LLM-as-a-judge scores for claim support, coverage, and noise as Phoenix datasets and experiments.
Mixed
fix: replace arize-phoenix with arize-phoenix-otel to fix OOM (500s on /api/traces)GitHub pull request
Cloud Run containers hit 2,134 MiB against a 2 GiB limit and were killed, because the full arize-phoenix package pulls in the whole server's dependencies. The client-only arize-phoenix-otel package removed 1,846 lockfile lines.
Positive
Replace Langfuse with Phoenix, add LiteLLM proxy, add Snowflake Labs MCPGitHub pull request
Replaced a Langfuse stack that needed ClickHouse, Redis, and MinIO with one Phoenix container on PostgreSQL, and routed LiteLLM and the MCP toolbox to export OpenTelemetry traces to it.
Mixed
Projects with more than 10,000 spans failed to load their header and cost summary. Raising proxy timeouts and tuning the connection pool cut dropped requests from 4 in 5 to 1 in 10, but the errors did not stop.
Mixed
Comment on: Show HN: A MitM proxy to see what your LLM tools are sendingHacker News comment
Wants Claude Code sessions in Arize Phoenix; the best route the commenter found, Arize's own Claude Code tracing setup, feels too heavy.
Mixed
[ENHANCEMENT]: Group-Based Multi-Tenancy for Data IsolationGitHub issue
Phoenix authenticates users and assigns roles, but any viewer sees every project, so one instance cannot serve finance, engineering, and legal teams separately.
Mixed
[BUG]: Transient error StatusCode.RESOURCE_EXHAUSTEDGitHub issue
Exports to a self-hosted Phoenix keep failing with RESOURCE_EXHAUSTED; the author suspects oversized traces and asks what span and trace size limit Phoenix enforces.
Mixed
[ENHANCEMENT]: Apache-2.0 (or similar) relicensing for arize-phoenix-clientGitHub issue
Says the client library's Elastic License 2.0 is too restrictive for open-source projects and asks Arize to relicense it under Apache 2.0, as it did the OTel package.
Positive
Selecting The Right AI Evals ToolIndependent evaluation, hamel.dev
A panel of eval practitioners rated Phoenix well for its notebook-driven evals, trace-to-playground flow, and fully local operation, and found output panes hard to read and run statistics too thin.
Positive
Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardHacker News comment
Says they are a big fan of Arize's OpenInference instrumentation and Phoenix in a thread about OpenTelemetry for LLM observability.
Mixed
Arize integration for .NETReddit post
Found Arize AX tracing easy and useful from Python, then found no Arize SDK for .NET when moving the same observability to a .NET codebase.
Positive
Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardHacker News comment
Says a full LLM observability stack is one Docker Compose file away with OpenTelemetry, Phoenix, and ClickHouse, so there is no excuse to skip it.
Negative
Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardHacker News comment
Found Phoenix clunky and is happier with Langfuse; in a follow-up the commenter cites wrestling with instrumentation and prompt management that was not built out.
No opinion stated
Self-hosted Phoenix as the one observability tool in a lean agent stackReddit comment, r/mlops
Asked which tools machine learning engineers pay for when building agents, lists a model provider, PydanticAI or ADK, and self-hosted Phoenix for observability, and pays for nothing beyond the basics.
Counts toward
Mixed
[BUG]: Prebuilt Evaluators break for Experiments.GitHub issue
Following Phoenix's experiment docs, prebuilt evaluators and decorated custom evaluators showed no results in the Experiments tab; Arize pointed to a newer client API and the issue closed as not planned.
Counts toward, pending a recheck
Mixed
[BUG]: DeadlockDetectedErrorGitHub issue
PostgreSQL deadlocks appear often in a self-hosted Phoenix on OpenShift and trace data is lost; raising client timeouts did not help.
Positive
The RAG Stack We Landed On After 37 FailsConference talk with transcript, AI Engineer World's Fair 2025
Prototypes with LangSmith or Phoenix but runs Phoenix in production because it deploys easily as one Docker container beside the rest of his RAG stack.
Positive
Authorization beyond AuthenticationGitHub issue
Loves the tool and got Keycloak sign-in working, but cannot limit access to users holding specific roles.
Pages from Arize AI, used to check facts for every group.
Documents AX Free at 25,000 spans and 1 GB a month with 15-day retention, and AX Pro at US$50 a month with 50,000 spans, 10 GB, and 30-day retention. AX Enterprise adds custom volume, self-hosting, SSO, audit logs, and HIPAA.
Documents online evaluation tasks that run LLM judges, code evaluators, agent-as-a-judge, or remote evaluators continuously on production traces, with sampling, using an AI provider the team configures.
Documents Signal, which scans a tracing project on a schedule and groups recurring failures into issues. Free allows 10 issues a month and Pro 25. Enterprise has no cap and can also open fix pull requests.
Documents SAML single sign-on and role-based access through organizations, spaces, and custom roles at the space or project level.
Documents OpenInference settings that hide inputs, outputs, messages, images, and embeddings, and span processors that redact PII with regex or Microsoft Presidio before spans leave the application.
Documents installing Arize AX on Kubernetes in Google Cloud, AWS, Azure, IBM Cloud, OpenShift, or Rancher, with an operator and Helm.
Documents moving Phoenix traces, datasets, experiments, and stored eval results into AX with a coding-agent skill, and pointing the existing OpenInference instrumentation at AX.
States that Phoenix is released under the Elastic License 2.0 and is free to self-host with no feature gates.
Documents self-hosting Phoenix with no license fees, usage limits, or feature gates, on Docker, Kubernetes, Helm, and one-click cloud templates, with data that stays in the team's infrastructure.
Documents SQLite as the default store and PostgreSQL 14 or later for production, one tenant per instance, horizontal scaling, and project-scoped access control planned for later in 2026.
States that self-hosted Phoenix sends no trace, evaluation, or dataset data to Arize, collects only web analytics that can be turned off, and can run air-gapped.
Documents indefinite retention by default and project retention policies, by age or trace count, from Phoenix 9.0.
Documents admin, member, and viewer roles in Phoenix and points to Arize AX for SAML, multi-level RBAC, and just-in-time provisioning.
Compares self-hosted, community-supported Phoenix with managed Arize AX, and states that one instrumentation can send the same traces to either.
Source index
Every source GILD read, with the original address and the context used to count it. Open a finding to filter the full cards above. On smaller screens the index lists each source once by name, cohort and date; its full record above carries the address, context and findings.
| Source | Original URL | Author and context | Who | Published | Review date | Applies | Findings |
|---|---|---|---|---|---|---|---|
| PromptVersion.format() fails on developer messages for Anthropic and GoogleID sf-3 | Developer Communities | github.com/ | jaeminbird, self-hosted Phoenix user (issue author)self-described: Local, self-hosted Phoenix with arize-phoenix-client from main | Individual builder | Published Oct 28, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| Phoenix's simple architecture for tracing, other tools for evalsID sf-7 | Developer Communities | news.ycombinator.com/ | nvmdbljstm, Hacker News commenterself-described: Has used only Phoenix for tracing | Individual builder | Published Oct 28, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| Phoenix project page slows to seconds per load at 2.4 million root spansID sf-1 | Developer Communities | github.com/ | schlaepf, Phoenix self-hoster (issue author)self-described: Self-hosted Phoenix on PostgreSQL 16 with about 2.4 million root spans | Individual builder | Published Oct 26, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| Experiment results lose their evaluator definition when every attempt throwsID sf-2 | Developer Communities | github.com/ | juliendemarque-tulip, Phoenix user (issue author)self-described: Phoenix experiments whose runs can fail before returning a result | Individual builder | Published Oct 25, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| Datadog or Arize as the SaaS choice at workID sf-9 | Developer Communities | x.com/ | aiexplorations, builder of Praval agentsself-described: Agent observability at the author's workplace | Product or platform team | Published Oct 22, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Arize, Langfuse and Braintrust all intimidating at firstID sf-8 | Developer Communities | x.com/ | Ganesh Iyer, AI payments builder and creator of the Nura family assistantself-described: Tried the observability tools for his own agents | Individual builder | Published Oct 13, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| First Phoenix trace showed a coding agent retrying a failing test 9 timesID sf-6 | Developer Communities | x.com/ | Erik Fiala, founder building Breakflare and Everchatself-described: Tracing his own Claude Code loops with self-hosted Phoenix | Individual builder | Published Oct 8, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| Introducing AgentHub: Booking.com Platform for Modular Travel AI AgentsID l2-04 | Engineering Blogs & Reviews | booking.ai/ | Moran Beladev, Booking.com (with Hadas Harush and Chana Ross)self-described: AgentHub, Booking.com's platform that gives product teams configurable travel agents with shared monitoring | Organization-wide | Published Oct 2, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Self-hosted Phoenix and Langfuse side by side over OTLPID sf-11 | Developer Communities | www.reddit.com/ | bathon, Reddit commenter on r/mlopsself-described: Team projects with self-hosted models, tracing every call, tool call and agent-to-agent call | Product or platform team | Published Oct 1, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| feat: enable Phoenix tracing in production deploymentsID dc-37 | Developer Communities | github.com/ | Gennaro Baratta (GennaroBaratta), Developer on the FREE projectFREE, self-hosted production deployment with GPU inference | Individual builder | Published Sep 29, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| feat(observability): export traces over OTLP and link them to Phoenix instead of LangfuseID dc-38 | Developer Communities | github.com/ | Jérémie Doucy (jdoucy), Jérémie Doucy, contributor to the Bayes Impact platformself-described: Bayes Impact platform, staging and production | Product or platform team | Published Sep 29, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| chore(evals): Delete the Phoenix eval runnerID dc-36 | Developer Communities | github.com/ | Jiří Spilka (jirispilka), Engineer at Apifyself-described: Apify MCP server evals | Product or platform team | Published Sep 14, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Can the image dependencies for an offline/air-gapped Phoenix deployment be simplified?ID dc-35 | Developer Communities | github.com/ | ToWorld, Developer (discussion author)self-described: Team deploying Phoenix in a fully air-gapped environment | Small product team | Published Sep 9, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| fix: disable Phoenix tracing in production, gated behind PHOENIX_ENABLEDID dc-34 | Developer Communities | github.com/ | Danilo Henrique (danhenriquex), Developerself-described: Production chatbot built on Google ADK | Individual builder | Published Sep 8, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| feat(phoenix): add Arize Phoenix as a second OTLP trace sinkID dc-33 | Developer Communities | github.com/ | Jacob (JacobPEvans-personal), Developer, self-hosted homelabself-described: Self-hosted Proxmox stack with Cribl fanning OTLP traces to Langfuse and Phoenix | Individual builder | Published Sep 3, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Separating tool-call cost from tool-output cost in PhoenixID sf-13 | Developer Communities | www.reddit.com/ | Normal-Blueberry-385, Reddit poster on r/AI_Agentsself-described: Cost and token observability for a Python LangChain application on Phoenix and OpenTelemetry | Individual builder | Published Sep 3, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| Add backend OpenTelemetry tracing with PhoenixID dc-32 | Developer Communities | github.com/ | Rafael Pierre (rafaelpierre), Developerself-described: Sherlock, a Strands agent backend on AWS | Individual builder | Published Sep 1, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Wants reusable Phoenix interface componentsID sf-5 | Developer Communities | x.com/ | John Zabroski, founder of Simmaculate and FluentMigrator maintainerself-described: Building his own eval viewer | Individual builder | Published Aug 31, 2026 | Assessment reviewed Oct 30, 2026 | Current | Listed, no finding position |
| spike(observability): compare Traceway, Tempo, Langfuse, Phoenix, SigNoz and Grafana Agent ObservabilityID dc-31 | Developer Communities | github.com/ | mashkovd, Developer on mctl's platform teammctl agent platform choosing an OTLP backend | Small product team | Published Aug 26, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| feat: self-hosted OTel observability (Phoenix/Langfuse) for multi-agent tracing - not LangSmithID dc-28 | Developer Communities | github.com/ | akaszubski, Developer (issue author)self-described: Personal multi-agent coding harness on Claude Code | Individual builder | Published Aug 6, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| feat(evals): host Phoenix on Cloud Run and Cloud SQLID dc-29 | Developer Communities | github.com/ | Tapan Chugh (chughtapan), Developerself-described: moltzap evals, dashboards that outlive an ephemeral GKE cluster | Individual builder | Published Aug 6, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| feat(observability): standardise on Phoenix; restore Langfuse v4 as fallbackID dc-30 | Developer Communities | github.com/ | Jordi Martinez (jordimo), Jordi Martinez, developerself-described: Own infrastructure, run locally and on an AWS host | Individual builder | Published Aug 6, 2026 | Assessment reviewed Oct 30, 2026 | Current | Overall signalDatasets & Evaluations: PositiveFree, Simple Self-Hosting: PositiveAccess Control & Multi-Team Use: Raised as a concernSource-Available License: Discussed without concernLangfuse is the tool weighed against PhoenixWhen practitioners weigh Arize against another platform, which do they keep?: Chose or kept Arize |
| [kbn-evals] Remove Arize Phoenix executor and @arizeai/phoenix-client dependencyID dc-26 | Developer Communities | github.com/ | arturoliduena, Developer on Elastic's Kibana evaluation frameworkKibana's LLM evaluation framework | Product or platform team | Published Jul 29, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Comment on: A CLI that shows which sub-agent burned your tokens in one runID dc-27 | Developer Communities | news.ycombinator.com/ | rrkher059, Hacker News commenterself-described: Built a CLI over OpenInference spans | Individual builder | Published Jul 29, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Building Closed-Loop Evals for a Multimodal Agent at Uber ScaleID l2-01 | Talks & Videos | ai.engineer/ | Jai Chopra, Sr. Product Manager, Uber (with Soumya Gupta, Sr. Software Engineer)Uber's computer-vision team, running an agent that edits Uber Eats merchants' food photos | Product or platform team | Published Jul 24, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| PagerDuty for AI: How the SRE Agent Triages AI IncidentsID l2-05 | Engineering Blogs & Reviews | www.pagerduty.com/ | PagerDuty Engineering teamself-described: PagerDuty's Insights Agent, a chat assistant for operational questions, watched by Arize monitors | Product or platform team | Published Jul 21, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| [ENHANCEMENT]: Support attaching images to non-LLM spans (TOOL/CHAIN) without faking LLM message attributesID dc-25 | Developer Communities | github.com/ | robbert-gijsels, Developer (issue author)self-described: Team tracing a computer-vision pipeline with OpenTelemetry and OpenInference | Small product team | Published Jul 15, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Evaluate Agents Locally with Arize Phoenix (Hands-On Guide)ID ir-04 | Engineering Blogs & Reviews | folarin.dev/ | Folarin Akinloye, independent developerself-described: Tracing and judging their own agent locally | Individual builder | Published Jul 12, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Auto-evals: Braintrust Loop, Arize Alyx and LangSmith on the same 100 tracesID sf-10 | Engineering Blogs & Reviews | parlance-labs.com/ | Antaripa Saha and Hamel Husain, Parlance Labsself-described: 100 hand-labelled traces from a production apartment-leasing assistant | Small product team | Published Jul 11, 2026 | Assessment reviewed Oct 30, 2026 | Current | Not counted. Its author already has two counted records on this product. |
| From Traditional ML to AI Agents: How Booking.com Scales AI Observability With Arize AIID l2-03 | Engineering Blogs & Reviews | booking.ai/ | Amir Bitaraf, Booking.com (with Shahaf Veber)self-described: Booking.com's shared observability platform for traditional ML models and LLM agents; the authors describe a partnership with Arize | Organization-wide | Published Jul 10, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Add Arize Phoenix integration for LLM tracing and evalsID dc-24 | Developer Communities | github.com/ | Laurent Bouis (lbouis), Developerself-described: raffy-research, report generation with LLM-as-a-judge evals | Individual builder | Published Jun 19, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Spent 3 months evaluating Galileo, Arize, Langfuse and LangSmith for production LLM monitoring. Notes for anyone doing the same.ID dc-23 | Developer Communities | www.reddit.com/ | Total_Listen_4289, Reddit user, r/LLMDevsself-described: Small team shipping agents, evaluating observability for production | Small product team | Published May 30, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Automating and Optimizing Financial Signal Discovery with Multi-Agent SystemsID s2-03 | Engineering Blogs & Reviews | developer.nvidia.com/ | Peihan Huo, Hanyue He, and Ioana Boier of NVIDIA, with Yang Shen of Huatai SecuritiesMulti-agent signal discovery workflow on NeMo Agent Toolkit for quantitative research | Product or platform team | Published May 21, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| chore: remove Arize Phoenix (telemetry / observability) from VSSID dc-22 | Developer Communities | github.com/ | zac-wang-nv, Developer on NVIDIA's Video Search and Summarization blueprintNVIDIA AI Blueprint shipped with Docker Compose and Helm | Product or platform team | Published May 20, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| fix: replace arize-phoenix with arize-phoenix-otel to fix OOM (500s on /api/traces)ID dc-21 | Developer Communities | github.com/ | Venkata Subbarao Gorantla (gvsrusa), Developerself-described: Agent service on Cloud Run sending traces to Phoenix | Individual builder | Published May 9, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| BulkInserter opens up to 7 DB sessions per loop iteration, exhausting connection pool under loadID dc-20 | Developer Communities | github.com/ | David O'Connell (doconnell2020), David O'Connell, GitHub profile lists TelnyxSelf-hosted Phoenix on PostgreSQL with 2 replicas | Product or platform team | Published Mar 25, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Replace Langfuse with Phoenix, add LiteLLM proxy, add Snowflake Labs MCPID dc-19 | Developer Communities | github.com/ | Michael Svendsen (thesven), Michael Svendsen, developerself-described: Own self-hosted agent stack with LibreChat and LiteLLM | Individual builder | Published Mar 4, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| [BUG]: Error fetching GraphQL query ProjectPageHeaderQuery when opening project with >10k spans (costSummary None)ID dc-18 | Developer Communities | github.com/ | Lim Ghim Boon (GhimBoon), Lim Ghim Boon, GitHub profile lists IntelSelf-hosted Phoenix 12.33.1 on PostgreSQL behind nginx | Individual builder | Published Feb 5, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
Slow trace and span search performance when searching by spans.attributesID dc-17 | Developer Communities | github.com/ | oginskis, Developer (discussion author)self-described: Team self-hosting Phoenix on Kubernetes with Cloud SQL PostgreSQL, about 100,000 LLM interactions a day | Small product team | Published Feb 4, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Comment on: Show HN: A MitM proxy to see what your LLM tools are sendingID dc-16 | Developer Communities | news.ycombinator.com/ | vitorbaptistaa, Hacker News commenterself-described: Tracing their own Claude Code sessions | Individual builder | Published Jan 29, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| Flag Early, Fix Faster: Real-Time Intervention for Supplier Transfers with WilmaID ir-03 | Engineering Blogs & Reviews | www.aboutwayfair.com/ | Farshid Bahrami, Wayfair (with Atharva Deo, Roger Bock, Ying Jiang, and Luming Wang)self-described: Wayfair's Wilma, a LangGraph agent that flags supplier transfer tickets for associates | Product or platform team | Published Jan 15, 2026 | Assessment reviewed Oct 30, 2026 | Current | |
| fix(aihub): Replace Arize Phoenix with open source alternativeID dc-15 | Developer Communities | github.com/ | Joel Barmettler (joelbarmettlerUZH), Developer at bbv, bbvch-ai AI Hubbbvch-ai AI Hub, a product the team wants to offer as SaaS | Small product team | Published Dec 22, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| [ENHANCEMENT]: Group-Based Multi-Tenancy for Data IsolationID dc-14 | Developer Communities | github.com/ | metalshanked, Developer (issue author)self-described: Planning one central Phoenix instance for several internal teams | Individual builder | Published Dec 8, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| A pragmatic guide to LLM evals for devsID s2-01 | Engineering Blogs & Reviews | newsletter.pragmaticengineer.com/ | Hamel Husain, former machine learning engineer at Airbnb and GitHub, guest authorself-described: NurtureBoss, an apartment leasing assistant, reviewing agent traces | Small product team | Published Dec 2, 2025 | Assessment reviewed Oct 30, 2026 | Current | |
| [BUG]: Transient error StatusCode.RESOURCE_EXHAUSTEDID dc-13 | Developer Communities | github.com/ | hanweidong, Developer (issue author)self-described: Self-hosted Phoenix receiving OpenInference traces over gRPC | Individual builder | Published Oct 27, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
[ENHANCEMENT]: Apache-2.0 (or similar) relicensing for arize-phoenix-clientID dc-12 | Developer Communities | github.com/ | willkill07, Developer (issue author)self-described: Open-source projects integrating with Phoenix | Individual builder | Published Oct 13, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Evaluating AI Agents with DeepEval and Arize Phoenix: Lessons from Our Integration JourneyID s2-04 | Engineering Blogs & Reviews | codify.ch/ | Valentin Velev, Data Scientist, CodifyCodify AG, Swiss software and AI consultancy, evaluating its own agents | Product or platform team | Published Oct 6, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Selecting The Right AI Evals ToolID s2-02 | Engineering Blogs & Reviews | hamel.dev/ | Hamel Husain, AI evals consultant and course instructorself-described: Three-person panel that watched LangSmith, Braintrust, and Arize Phoenix complete the same eval assignment | Individual builder | Published Oct 1, 2025 | Assessment reviewed Oct 30, 2026 | Current | |
| Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardID dc-11 | Developer Communities | news.ycombinator.com/ | dat_attack, Hacker News commenterself-described: Hacker News thread on OpenTelemetry for LLM observability | Individual builder | Published Sep 29, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardID dc-09 | Developer Communities | news.ycombinator.com/ | jkisiel, Hacker News commenterself-described: Small startup choosing its LLM observability stack | Small product team | Published Sep 28, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Arize integration for .NETID dc-10 | Developer Communities | www.reddit.com/ | Commercial_Artist632, Reddit user, r/LLMDevsself-described: Arize AX tracing, moving from a Python codebase to .NET | Individual builder | Published Sep 28, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardID dc-07 | Developer Communities | news.ycombinator.com/ | CuriouslyC, Hacker News commenterself-described: Hacker News thread on OpenTelemetry for LLM observability | Individual builder | Published Sep 27, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Comment on: LLM Observability in the Wild, Why OpenTelemetry Should Be the StandardID dc-08 | Developer Communities | news.ycombinator.com/ | 7thpower, Hacker News commenterself-described: Hacker News thread on OpenTelemetry for LLM observability | Individual builder | Published Sep 27, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Self-hosted Phoenix as the one observability tool in a lean agent stackID sf-12 | Developer Communities | www.reddit.com/ | ProdigyManlet, machine learning engineer on r/mlopsself-described: Building agents with PydanticAI or Google's ADK, paying only for the basics | Individual builder | Published Sep 20, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Expand RBAC To Limit Access To ProjectsID dc-06 | Developer Communities | github.com/ | ring-pete, Developer (discussion author)self-described: One Phoenix instance serving development, QA, and production projects | Small product team | Published Sep 19, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| [BUG]: Prebuilt Evaluators break for Experiments.ID dc-05 | Developer Communities | github.com/ | taoari, developerself-described: Self-hosted Phoenix 11.29.0, dataset experiments | Individual builder | Published Aug 28, 2025 | Assessment reviewed Oct 30, 2026 | Needs a recheck | |
| PagerDuty + Arize: Building End-to-End Observability for AI Agents in ProductionID ir-02 | Engineering Blogs & Reviews | www.pagerduty.com/ | Everaldo Aguiar, Senior Engineering Manager, Applied AI, PagerDuty (co-written with Antonio Correia and with Arize's Rich Young)PagerDuty Advance agents: Insights, Shift, and SRE agents | Product or platform team | Published Aug 13, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | Not counted. It was co-written with Arize's partner solutions director as a joint partner post. |
| [BUG]: DeadlockDetectedErrorID dc-04 | Developer Communities | github.com/ | luismarquezgft, Developer (issue author)self-described: Self-hosted Phoenix on OpenShift with LangChain instrumentation | Individual builder | Published Jul 31, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Old logs are getting deleted when the number of log request is highID dc-03 | Developer Communities | github.com/ | vignesh-arivazhagan, Developer (discussion author)self-described: Team building a high-throughput LLM application | Small product team | Published Jul 17, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| The RAG Stack We Landed On After 37 FailsID s2-05 | Talks & Videos | ai.engineer/ | Jonathan Fernandes, independent AI engineerself-described: RAG systems for financial clients, deployed with Docker Compose | Individual builder | Published Jun 3, 2025 | Assessment reviewed Oct 30, 2026 | Current | |
| Add support for Arize Phoenix for LLM observability and evaluationID dc-02 | Developer Communities | github.com/ | yurif-freitas, Open WebUI user (issue author)self-described: Team running Phoenix alongside Open WebUI | Small product team | Published May 16, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Authorization beyond AuthenticationID dc-01 | Developer Communities | github.com/ | lucasalvarezlacasa, Developer (issue author)self-described: Self-hosted Phoenix behind Keycloak | Individual builder | Published Mar 5, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| The NonBioS LLM Observability PickID ir-01 | Engineering Blogs & Reviews | www.nonbios.ai/ | NonBioS teamself-described: NonBioS, building an AI software engineer that handles sensitive customer data | Small product team | Published Mar 5, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Optimizing LLMs in Insurance with DSPy: Beyond Manual TuningID l2-02 | Talks & Videos | ai.engineer/ | Jeronim Morina, AI and MLOps Engineer, AXAAXA Germany's data team, building a DSPy pipeline on its internal Secure GPT platform | Product or platform team | Published Feb 16, 2025 | Assessment reviewed Oct 30, 2026 | Still applicable | |
| Arize AX: Pricing and usageID pd-01 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Arize AX: Run online evals on tracesID pd-02 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Arize AX: SignalID pd-03 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Arize AX: SSO & RBACID pd-04 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Arize AX: Mask and redact sensitive dataID pd-05 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Arize AX: Self-hostedID pd-06 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Arize AX: Migrate from Phoenix to Arize AXID pd-07 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: LicenseID pd-08 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: Self-hostingID pd-09 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: ArchitectureID pd-10 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: PrivacyID pd-11 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: Data retentionID pd-12 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: Access control (RBAC)ID pd-13 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
| Phoenix: Arize Phoenix or Arize AXID pd-14 | Product Documentation | arize.com/ | Arize AIOfficial | Not counted (documentation) | No date stated | Documentation checked Oct 12, 2026 | Current | Verification only |
