Chapter 3 of 6
Confirm these prerequisites:
- Session 04 produced one governed Foundry agent in an approved nonproduction project.
- Session 09 selected the evaluator set and thresholds for that same agent.
- Session 11 named the Log Analytics workspace, Application Insights resource, action owner, and incident route.
- Session 12 or the approved deployment path can run Bicep what-if and deployment at the exact resource group that contains the Foundry account.
- The operator has Monitoring Contributor on the approved resource group.
- The project managed identity can receive Foundry User through the customer's access process.
- The operating owner has reviewed baseline traffic and approved the initial thresholds.
Keep tenant IDs, subscription IDs, resource IDs, project endpoints, prompts, responses, tokens, connection strings, and customer data out of this repository. Store resolved values in the approved private configuration path.
Implementation files#
| Type | File | Consumer |
|---|---|---|
| Deployment | artifacts/monitoring/foundry-platform-monitoring.bicep | The Azure monitoring deployment pipeline |
| Deployment | artifacts/monitoring/foundry-platform-monitoring.bicepparam | The Azure monitoring deployment pipeline |
| Record | artifacts/evaluation/continuous-evaluation-decision.json | The AI quality owner, Foundry operator, and module preflight scripts |
| Runtime | artifacts/evaluation/continuous-evaluation-rule.py | The Foundry evaluation operator |
| Runtime | artifacts/evaluation/requirements.txt | The Foundry evaluation operator and Python build process |
| Runtime | artifacts/queries/foundry-token-and-throttling.kql | The Azure Monitor operations owner |