Skip to content

Clarify Arize integration positioning - #570

Open
arizedatngo wants to merge 1 commit into
deepset-ai:mainfrom
arizedatngo:arize-positioning-refresh
Open

Clarify Arize integration positioning#570
arizedatngo wants to merge 1 commit into
deepset-ai:mainfrom
arizedatngo:arize-positioning-refresh

Conversation

@arizedatngo

@arizedatngo arizedatngo commented Aug 18, 2026

Copy link
Copy Markdown

Summary

  • Clarifies the Arize AX path and the Phoenix path across the Haystack integration pages
  • Keeps the existing Haystack tracing examples intact
  • Adds short context for readers moving from trace collection into evaluation workflows

Why

The pages already show how to trace Haystack pipelines. This update makes it clearer that AX is the full-featured option for production, managed cloud, or enterprise self-hosted deployments, while Phoenix fits open-source local and self-hosted workflows.

Testing

  • Docs-only change; not run.

@arizedatngo
arizedatngo requested a review from a team as a code owner August 18, 2026 20:04
@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown

@arizedatngo is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

@arizedatngo
arizedatngo force-pushed the arize-positioning-refresh branch from 6aa6803 to f1ea4e3 Compare August 18, 2026 20:07
@arizedatngo arizedatngo changed the title Refresh Arize integration positioning Clarify Arize integration positioning Aug 18, 2026
@arizedatngo
arizedatngo force-pushed the arize-positioning-refresh branch from f1ea4e3 to 3b83d15 Compare August 18, 2026 20:57
@arizedatngo
arizedatngo force-pushed the arize-positioning-refresh branch from 3b83d15 to bc9f1a3 Compare August 19, 2026 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant