As a new user I find it a bit strange that you have to push a trace to phoenix in order to create a new project (e.g. we would do that in a github actions when provisioning the app). Would be cleaner to have a projects API to perform CRUD operations (+ a create project functionality in the UI). May I create a request for that too? Mikyo By the way this link is dead... Should be this one I guess?
Currently, Phoenix requires traces to be pushed in order to create a new project, as projects are automatically created when traces arrive. This is confirmed by a Slack conversation where it was mentioned that projects show up after traces are sent. There isn't a separate API for project CRUD operations at the moment.You can certainly create a feature request for a projects API to perform CRUD operations. This would be a valuable enhancement for users who want more control over project management without relying on trace data.Regarding the link, the correct documentation link for tracing in Phoenix is here.Would you like more detail on any specific part?Sources: - Slack conversation - here
๐กย Hint: Mention RunLLM in the thread for followups.
Yeah I think that makes sense. I think the reason why we've had it this way for so long is that it's sorta acts as re-affirmation that you have setup tracing correctly if the project gets scaffolded via traces rather than via the UI. E.g. if you create a project but you setup tracing wrong, you inevitably end up with traces landing in the wrong project. However making the simple CRUD operations and management of projects via the UI makes a lot of sense. I'm down to add it ๐ . We'll be adding more functionality like retention policies on projects so making the project onboarding experience be UI / API driven makes a lot of sense with regards to the direction we will be going. Appreciate the feedback! Keep it coming. Feel free to file issues if you wanna follow along with our progress.
