Add Arize Phoenix tracing instructions to the observability docs page #7812
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi DSPy team - I was working through a tutorial on prompt optimization using DSPy for Arize Phoenix, and noticed the docs page on observability just showed MLFlow. I, somewhat selfishly, figured it could be good to have other observability options on there, similar to what other coming tools do (e.g. litellm).
Phoenix also will trace the optimization process when compiling a teleprompter, which I thought could be helpful on top of what MLFlow shows.
Made this PR to include Arize Phoenix as an option, and figured others could follow suit.
Hope you don't mind! Lmk of any desired changes or questions