Skip to content

Agent Monitoring Continuous Evaluation for Custom Agents Failing with error "No trace data found" #47812

Description

@hante-sonova
  • Package Name: Agent Monitoring Continuous Evaluation
  • Package Version:
  • Operating System:
  • Python Version:

Describe the bug
We have setup continuous monitoring via the UI for our custom agent, however evaluation run fails with this error even though traces exist:

There was an error with this evaluation run.No trace data found where customDimensions.gen_ai.input.messages or customDimensions.gen_ai.output.messages contain data. Please check the agent running status for agent 'ifd-mono' during time range: from 2026-07-02T05:50:08+00:00 to 2026-07-02T06:50:08+00:00

Image Image Image

To Reproduce
Set up monitoring for your custom agents

  1. Onboard your custom agent to Foundry using the instructions in Register and manage custom agents.
  2. Instrument your agent to comply with the semantic conventions for generative AI solutions in the OpenTelemetry standard.
  3. Configure your agent to send telemetry to the same Application Insights instance as your Foundry project to enable continuous evaluation features.
  4. In Foundry Control Plane, go to the Asset page and select your agent.
  5. Select the Monitor tab to view your metrics and charts.
  6. Set up continuous evaluations using the methods outlined in Configure settings.

Note: We only implemented the configure settings via the UI and didn't create the python implementation as we understood it achieves the same thing?

Expected behavior
A clear and concise description of what you expected to happen.
Evalution result should appear in the Evaluation page successfully

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
See user_log attached

user_logs (12).txt

Metadata

Metadata

Assignees

Labels

AI ProjectsClientThis issue points to a problem in the data-plane of the library.Service AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions