Python: Use executor_id and edge_group_id as span names for meaningful observability traces

[moonbox3]

Motivation and Context

Changes span names from hardcoded constants (executor.process, edge_group.process) to use meaningful identifiers (executor_id, edge_group_id), making observability traces readable when multiple executors/edge groups are present in a workflow.

Changes

• create_processing_span: Uses executor_id as span name instead of OtelAttr.EXECUTOR_PROCESS_SPAN
• create_edge_group_processing_span: Uses edge_group_id (or edge_group_type as fallback) as span name instead of OtelAttr.EDGE_GROUP_PROCESS_SPAN
• Updated tests to filter spans by attributes rather than hardcoded names

Not a breaking change. Span names are not part of the public API contract. All span attributes (executor.id, executor.type, edge_group.type, etc.) remain unchanged, so existing trace consumers continue to work correctly with more meaningful span names.

Description

• Fixes Python: Use more meaningful names in observability traces #2467
• Adjust tests based on new behavior

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[markwallace-microsoft]

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
packages/core/agent_framework
observability.py	610	101	83%	238, 264–266, 268, 270–274, 282–283, 288–289, 294–299, 322–324, 326–327, 333, 417, 427, 449, 455, 474–476, 484–486, 509–511, 521–523, 656, 658, 745–749, 752–756, 765–768, 778–781, 783, 1050, 1128–1130, 1200–1202, 1360, 1368, 1372, 1376, 1382, 1384, 1386, 1394, 1404, 1432–1433, 1446–1449, 1468–1470, 1472–1475, 1477–1478, 1482, 1485, 1543, 1559, 1563, 1697, 1699
TOTAL	15886	2416	84%

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
2282	130 💤	0 ❌	0 🔥	59.380s ⏱️

[Copilot]

Pull request overview

This PR improves observability by changing span names from hardcoded constants to meaningful identifiers. Instead of using generic names like "executor.process" and "edge_group.process", the spans now use the actual executor_id and edge_group_id, making traces more readable when multiple executors or edge groups are involved.

Key changes:

• Executor processing spans now use executor_id as the span name
• Edge group processing spans now use edge_group_id (with fallback to edge_group_type) as the span name
• Tests updated to filter spans by attributes rather than hardcoded names

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 10 comments.

File	Description
python/packages/core/agent_framework/observability.py	Modified create_processing_span to use executor_id as span name and create_edge_group_processing_span to use edge_group_id (or edge_group_type as fallback)
python/packages/core/tests/workflow/test_workflow_observability.py	Updated tests to filter spans by attributes and added verification that span names match executor_id
python/packages/core/tests/workflow/test_edge.py	Updated edge group tests to filter spans by attributes instead of hardcoded span names

---

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.