microsoft / microsoft/agent-framework
Add telemetry support for condition input and output in edge group conditions
Open
Nobody has claimed this yet.
.NET
epic
observability
workflows
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
Description
Currently, telemetry in the Microsoft Agent Framework does not capture condition input and output for edge group conditions.
This makes it hard to debug agent routing — especially when loops or multiple routes are evaluated based on conditions.
Proposed Solution
Add telemetry to log:
- Condition Input: values passed into the condition
- Condition Output: the evaluation result (
true/falseor computed result)
Example:
{
"event": "ConditionEvaluated",
"conditionInput": { "customerType": "premium" },
"conditionOutput": true,
"selectedEdge": "PremiumAgentRoute"
}
Benefit
Improves observability and debugging by showing why a specific route or agent was selected.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.