Questions on Securing Phoenix Web App and Custom Trace Attributes
Hello team, we just started using Phoenix to trace our Typescript Azure OpenAI calls. The code is quite easy to use, and we love it so far. However in the web app we have noticed a few things and we are not sure if we're missing something or it just isn't supported yet:
Is there a way to lock the Phoenix web app (Docker container) with username/password or some kind of access control?
Currently we tried limiting access by IP, but that is not feasible because Azure requires static IP even for the apps that will send the traces to the Phoenix app
Is there a way to show attributes which are not listed in the main table for Traces/Spans?
For example we set a custom attribute called input.agent, that we would like to see in the main table and also sort/filter by it
Is it possible to group by some specific attribute?
We are storing an id to connect it with our other logs in the DB
We would like to group conversations by this id, so that we can see flow of the spans. Is this possible?
