Where does Foundry tracing send data for debugging?
Why C is the answer
Azure Monitor Application Insights
Tracing is built on OpenTelemetry and integrates with Application Insights.
In detail
- Foundry tracing sends data to Azure Monitor Application Insights.
- Connect tracing before you need it.
Use case
An illustrative scenario, not a real incident.
A developer debugs a slow answer by opening its trace in Azure Monitor Application Insights, and sees which step took longest.
See it in different ways
flowchart LR A["App or agent"] --> B["OpenTelemetry traces"] B --> C["Application Insights"] A --> D["Evaluators"] D --> E["Quality and safety scores"]
sequenceDiagram participant A as Agent or app participant O as OpenTelemetry participant M as Application Insights A->>O: Spans for each step O->>M: Exports the trace M-->>A: Debug and monitor
flowchart LR S0["Foundry app"] --> S1["Tracing"] --> S2["Application Insights"] --> S3["Debug"]
Key point: Foundry traces go to Application Insights.
Why the other options are wrong
- A. A table in the project's storage account
- A table is not the destination.
- B. The model provider's public status page
- A status page holds no traces.
- D. Local log files on each developer's machine
- Local files are not where traces go.