Chaitanya

RunLLM yes a code example is appreciated

Hi Mikyo I noticed that you have added a feature that sets the admin key separately using an environment variable PHOENIX_ADMIN_SECRET . Will this serve my initial request?

Hi Mikyo Thanks for your response. I am deploying phoenix in ECS fargate along with my chatbot services. These chatbot services send traces to the phoenix services. Right now upon successful deployment of the phoenix, the other chatbot services will start. This is completely automated in the code pipeline. Now I need to add a manual intervention after phoenix is deployed, need to change the admin default password, generate a system API key, and store it in one of the secrets and pass it to downstream applications as input or environment variable etc. I want to avoid this manual intervention. Hope it is clear...

So I removed the path-patterns in the listener rule configurations and the environment variable for host root path. After that I can see the UI and API are both working. It will be better to have an example for deploying the phoenix in any cloud platform with various settings for paths. Thanks Roger .

I found the file. There is an error "Unexpected token <"

Yeah I am using the latest version only. I am using the ALB in AWS. How can I debug the error?

Roger Y. do you want me to try with the debug image here?

Also there is a health check I have added for the ECS. It will ping the /healthz endpoint periodically. Actually it should ping /phoenix/v1/healthz but as per below log, its different. INFO: 10.41.248.21:63560 - "GET /phoenix/v1/phoenix/v1/healthz HTTP/1.1" 200 OK