Hi everyone,
I am encountering two distinct blockers while trying to set up evaluations for an agent in Azure AI Foundry (utilizing an agent connected to a custom MCP server and an Azure AI Search index).
Issue 1: "Failed to save continuous evaluation settings" for Tool Evaluators
When navigating to my agent under Continuous Evaluations (Production/Continuous Monitoring), I can successfully add and save behavioral evaluators (like Coherence, Customer Satisfaction, and Intent Resolution).
However, whenever I attempt to add any of the following tool-based metrics:
- Tool Call Accuracy Evaluator
- Tool Input Accuracy Evaluator
- Tool Output Utilization Evaluator
The portal UI instantly throws the error: Failed to save continuous evaluation settings. Please try again.
- Context: My agent relies on an Azure AI Search index and a remote custom MCP server endpoint. Why does the continuous evaluation configuration fail to save specifically when these tool evaluators are selected? Is there a hidden schema or dataset dependency required to register them in production monitoring?
Issue 2: "No runs" in Foundry Portal & Missing Logs in App Insights / LAW
For the baseline evaluators that did successfully save (Coherence, Customer Satisfaction), the Foundry Portal dashboard shows "No runs" across all tabs.
To troubleshoot, I checked the underlying workspace-based Application Insights instance and the linked Log Analytics Workspace (LAW), but no evaluation traces or metrics are appearing there either.
- Questions:
- Do continuous evaluations require a minimum baseline threshold of production traffic or chat interactions before the evaluation pipeline executes and populates the "Runs" tab?
- Is there a specific background service, latency period, or diagnostic logging setting required to force the continuous evaluation engine to start piping metrics into App Insights/LAW?
- I am concurrently working on uploading a generated custom dataset for a batch evaluation. Is continuous evaluation completely separate from dataset-driven evaluation runs, and if so, how do I kickstart the tracking for it?
Any guidance or troubleshooting steps on resolving the tool evaluator UI crash and locating the missing evaluation telemetry would be greatly appreciated!
Hi everyone,
I am encountering two distinct blockers while trying to set up evaluations for an agent in Azure AI Foundry (utilizing an agent connected to a custom MCP server and an Azure AI Search index).
Issue 1: "Failed to save continuous evaluation settings" for Tool Evaluators
When navigating to my agent under Continuous Evaluations (Production/Continuous Monitoring), I can successfully add and save behavioral evaluators (like Coherence, Customer Satisfaction, and Intent Resolution).
However, whenever I attempt to add any of the following tool-based metrics:
- Tool Call Accuracy Evaluator
- Tool Input Accuracy Evaluator
- Tool Output Utilization Evaluator
The portal UI instantly throws the error: Failed to save continuous evaluation settings. Please try again.
- Context: My agent relies on an Azure AI Search index and a remote custom MCP server endpoint. Why does the continuous evaluation configuration fail to save specifically when these tool evaluators are selected? Is there a hidden schema or dataset dependency required to register them in production monitoring?
Issue 2: "No runs" in Foundry Portal & Missing Logs in App Insights / LAW
For the baseline evaluators that did successfully save (Coherence, Customer Satisfaction), the Foundry Portal dashboard shows "No runs" across all tabs.
To troubleshoot, I checked the underlying workspace-based Application Insights instance and the linked Log Analytics Workspace (LAW), but no evaluation traces or metrics are appearing there either.
- Questions:
- Do continuous evaluations require a minimum baseline threshold of production traffic or chat interactions before the evaluation pipeline executes and populates the "Runs" tab?
- Is there a specific background service, latency period, or diagnostic logging setting required to force the continuous evaluation engine to start piping metrics into App Insights/LAW?
- I am concurrently working on uploading a generated custom dataset for a batch evaluation. Is continuous evaluation completely separate from dataset-driven evaluation runs, and if so, how do I kickstart the tracking for it?
Any guidance or troubleshooting steps on resolving the tool evaluator UI crash and locating the missing evaluation telemetry would be greatly appreciated!