[BUG] Promptflow tracing is not compatible with code-based Azure Web Apps about promptflow HOT 3 CLOSED

Attach another issue on same topic for more context: #3391

Logging traces to Azure Cosmos DB requires credential, and its current implementation only supports Azure CLI. So if Azure Web App does not support Azure CLI, according to Ryan's comment in the Q&A, that should be current limitation.

To support this, prompt flow needs to support retrieving credential from something else like environment variables. I added feature tag (and remove bug tag) on this issue, and we can track this using this issue.

BTW, for the error message that complains "pf command not found", it requires you to correctly configure your environment in Azure Web App.

from promptflow.

Hi @tyler-suard-parker , could you please share how you deploy a flow to web APP?
Currently, prompt flow serving supports collect trace to Azure application insights.
You could use pf build to build a docker image from a flow and then deploy to Azure APP service. For more details, please refer to this article.
After deploy, you can set environment variables of your application insights connection string in the APP service, and then you can collect the trace to the app insights.

from promptflow.

@zhengfeiwang @likebupt I was able to get tracing to work using a container web app, but it still will not work using a code-based web app. Choosing to make the user sign in using az login is, in my opinion, a poor design choice. It isn't necessary (Azure can use opentelemetry to send telemetry from a web app to azure metrics without using az login, see here: https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable?tabs=python) and it adds a ton of frustration. I had to containerize my app code, create a new web app, and change our whole deployment pipeline just to use tracing.

from promptflow.