[Dineshsuriya D (droideronline)]

Motivation & Context

Issue #9896 reported that configure_otel_providers attaches an OTel LoggingHandler to the agent_framework logger, so an application that also has its own OTel LoggingHandler on the root logger exports every agent_framework record twice. Per maintainer direction on the issue, runtime behavior stays unchanged and the function's docstring is clarified instead.

Description & Review Guide

• What are the major changes? Added a Note to the configure_otel_providers docstring: it is a convenience setup that attaches a handler to the agent_framework logger only, does not inspect or coordinate with other logging handlers, and applications combining it with their own root handler should use manual OpenTelemetry setup, with a pointer to python/samples/02-agents/observability/advanced_manual_setup_console_output.py. Also corrected an inline comment that said "root logger" where the code attaches to the agent_framework logger.
• What is the impact of these changes? Documentation and a comment only. No runtime change.
• What do you want reviewers to focus on? The wording of the new docstring note.

Related Issue

Fixes #9896

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: issue analysis and the docstring wording.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.