Files
agent-framework/dotnet/samples/02-agents/AgentOpenTelemetry
T
westey 8b191de936 Merge and move scripts (#4308)
* .NET: Add Microsoft Fabric sample #3674 (#4230)

Co-authored-by: Chris <66376200+crickman@users.noreply.github.com>

* Python: Phase 2: Embedding clients for Ollama, Bedrock, and Azure AI Inference (#4207)

* Phase 2: Embedding clients for Ollama, Bedrock, and Azure AI Inference

Add embedding client implementations to existing provider packages:

- OllamaEmbeddingClient: Text embeddings via Ollama's embed API
- BedrockEmbeddingClient: Text embeddings via Amazon Titan on Bedrock
- AzureAIInferenceEmbeddingClient: Text and image embeddings via Azure AI
  Inference, supporting Content | str input with separate model IDs for
  text (AZURE_AI_INFERENCE_EMBEDDING_MODEL_ID) and image
  (AZURE_AI_INFERENCE_IMAGE_EMBEDDING_MODEL_ID) endpoints

Additional changes:
- Rename EmbeddingCoT -> EmbeddingT, EmbeddingOptionsCoT -> EmbeddingOptionsT
- Add otel_provider_name passthrough to all embedding clients
- Register integration pytest marker in all packages
- Add lazy-loading namespace exports for Ollama and Bedrock embeddings
- Add image embedding sample using Cohere-embed-v3-english
- Add azure-ai-inference dependency to azure-ai package

Part of #1188

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix mypy duplicate name and ruff lint issues

- Rename second 'vector' variable to 'img_vector' in image embedding loop
- Combine nested with statements in tests
- Remove unused result assignments in tests

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* updates from feedback

* Fix CI failures in embedding usage handling

- Fix Azure AI embedding mypy issues by normalizing vectors to list[float],
  safely accumulating optional usage token fields, and filtering None entries
  before constructing GeneratedEmbeddings
- Avoid Bandit false positive by initializing usage details as an empty dict
- Update OpenAI embedding tests to assert canonical usage keys
  (input_token_count/total_token_count)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* [Purview] Mark responses as responses and fix epoch bug for python long overflow (#4225)

* .NET: Support InvokeMcpTool for declarative workflows (#4204)

* Initial implementation of InvokeMcpTool in declarative workflow

* Cleaned up sample implementation

* Updated sample comments.

* Added missing executor routing attribute

* Fix PR comments.

* Updated based on PR comments.

* Updated based on PR comments.

* Removed unnecessary using statement.

* Update Python package versions to rc2 (#4258)

- Bump core and azure-ai to 1.0.0rc2
- Bump preview packages to 1.0.0b260225
- Update dependencies to >=1.0.0rc2
- Add CHANGELOG entries for changes since rc1
- Update uv.lock

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* .NET: Fixing issue where OpenTelemetry span is never exported in .NET in-process workflow execution (#4196)

* 1. Add reproduction test for issue #4155: workflow.run Activity never stopped in streaming OffThread path

The WorkflowRunActivity_IsStopped_Streaming_OffThread test demonstrates that
the workflow.run OpenTelemetry Activity created in StreamingRunEventStream.RunLoopAsync
is started but never stopped when using the OffThread/Default streaming execution.
The background run loop keeps running after event consumption completes, so the
using Activity? declaration never disposes until explicit StopAsync() is called.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2. Fix workflow.run Activity never stopped in streaming OffThread execution (#4155)

The workflow.run OpenTelemetry Activity in StreamingRunEventStream.RunLoopAsync
was scoped to the method lifetime via 'using'. Since the run loop only exits on
cancellation, the Activity was never stopped/exported until explicit disposal.

Fix: Remove 'using' and explicitly dispose the Activity when the workflow reaches
Idle status (all supersteps complete). A safety-net disposal in the finally block
handles cancellation and error paths.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add root-level workflow.session activity spanning run loop lifetime\n\nImplements two-level telemetry hierarchy per PR feedback from lokitoth:\n- workflow.session: spans the entire run loop / stream lifetime\n- workflow_invoke: per input-to-halt cycle, nested within the session\n\nThis ensures the session activity stays open across multiple turns,\nwhile individual run activities are created and disposed per cycle.\n\nAlso fixes linkedSource CancellationTokenSource disposal leak in\nStreamingRunEventStream (added using declaration)."

* Address Copilot review: fix Activity/CTS disposal, rename activity, add error tag\n\n1. LockstepRunEventStream: Remove 'using' from Activity in async iterator\n   and manually dispose in finally block (fixes #4155 pattern). Also dispose\n   linkedSource CTS in finally to prevent leak.\n2. Tags.cs: Add ErrorMessage (\"error.message\") tag for runtime errors,\n   distinct from BuildErrorMessage (\"build.error.message\").\n3. ActivityNames: Rename WorkflowRun from \"workflow_invoke\" to \"workflow.run\"\n   for cross-language consistency.\n4. WorkflowTelemetryContext: Fix XML doc to say \"outer/parent span\" instead\n   of \"root-level span\".\n5. ObservabilityTests: Assert WorkflowSession absence when DisableWorkflowRun\n   is true.\n6. WorkflowRunActivityStopTests: Fix streaming test race by disposing\n   StreamingRun before asserting activities are stopped.\n7. StreamingRunEventStream/LockstepRunEventStream: Use Tags.ErrorMessage\n   instead of Tags.BuildErrorMessage for runtime error events."

* Review fixes: revert workflow_invoke rename, use 'using' for linkedSource, move SessionStarted earlier\n\n- Revert ActivityNames.WorkflowRun back to \"workflow_invoke\" (OTEL semantic convention contract)\n- Use 'using' declaration for linkedSource CTS in LockstepRunEventStream (no timing sensitivity)\n- Move SessionStarted event before WaitForInputAsync in StreamingRunEventStream to match Lockstep behavior"

* Improve naming and comments in WorkflowRunActivityStopTests"

* Prevent session Activity.Current leak in lockstep mode, add nesting test

Save and restore Activity.Current in LockstepRunEventStream.Start() so the
session activity doesn't leak into caller code via AsyncLocal. Re-establish
Activity.Current = sessionActivity before creating the run activity in
TakeEventStreamAsync to preserve parent-child nesting.

Add test verifying app activities after RunAsync are not parented under the
session, and that the workflow_invoke activity nests under the session."

* Fix stale XML doc: WorkflowRun -> WorkflowInvoke in ObservabilityTests

---------

Co-authored-by: alliscode <bentho@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Python / .NET Samples - Restructure and Improve Samples (Feature Branc… (#4092)

* Python: .NET Samples - Restructure and Improve Samples (Feature Branch) (#4091)

* Moved by agent (#4094)

* Fix readme links

* .NET Samples - Create `04-hosting` learning path step (#4098)

* Agent move

* Agent reorderd

* Remove A2A section from README 

Removed A2A section from the Getting Started README.

* Agent fixed links

* Fix broken sample links in durable-agents README (#4101)

* Initial plan

* Fix broken internal links in documentation

Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

* Revert template link changes; keep only durable-agents README fix

Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

* .NET Samples - Create `03-workflows` learning path step (#4102)

* Fix solution project path

* Python: Fix broken markdown links to repo resources (outside /docs) (#4105)

* Initial plan

* Fix broken markdown links to repo resources

Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

* Update README to rename .NET Workflows Samples section

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

* .NET Samples - Create `02-agents` learning path step (#4107)

* .NET: Fix broken relative link in GroupChatToolApproval README (#4108)

* Initial plan

* Fix broken link in GroupChatToolApproval README

Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

* Update labeler configuration for workflow samples

* .NET - Reorder Agents samples to start from Step01 instead of Step04 (#4110)

* Fix solution

* Resolve new sample paths

* Move new AgentSkills and AgentWithMemory_Step04 samples

* Fix link

* Fix readme path

* fix: update stale dotnet/samples/Durable path reference in AGENTS.md

Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>

* Moved new sample

* Update solution

* Resolve merge (new sample)

* Sync to new sample - FoundryAgents_Step21_BingCustomSearch

* Updated README

* .NET Samples - Configuration Naming Update (#4149)

* .NET: Restore AzureFunctions index parity with ConsoleApps under DurableAgents samples (#4221)

* Clean-up `05_host_your_agent`

* Config setting consistency

* Refine samples

* AGENTS.md

* Move new samples

* Re-order samples

* Move new project and fixup solution

* Fixup model config

* Fix up new UT project

---------

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>

* Python: Fix Bedrock embedding test stub missing meta attribute (#4287)

* Fix Bedrock embedding test stub missing meta attribute

* Increase test coverage so gate passes

* Python: (ag-ui): fix approval payloads being re-processed on subsequent conversation turns (#4232)

* Fix ag-ui tool call issue

* Safe json fix

* Python: Update workflow orchestration samples to use AzureOpenAIResponsesClient (#4285)

* Update workflow orchestration samples to use AzureOpenAIResponsesClient

* Fix broken link

* Move scripts to scripts folder

---------

Co-authored-by: Roger Barreto <19890735+rogerbarreto@users.noreply.github.com>
Co-authored-by: Chris <66376200+crickman@users.noreply.github.com>
Co-authored-by: Eduard van Valkenburg <eavanvalkenburg@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Rishabh Chawla <rishabhchawla1995@gmail.com>
Co-authored-by: Peter Ibekwe <109177538+peibekwe@users.noreply.github.com>
Co-authored-by: Dmytro Struk <13853051+dmytrostruk@users.noreply.github.com>
Co-authored-by: Ben Thomas <ben.thomas@microsoft.com>
Co-authored-by: alliscode <bentho@microsoft.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Evan Mattson <35585003+moonbox3@users.noreply.github.com>
8b191de936 Β· 2026-02-26 10:49:07 +00:00
History
..
2026-02-26 10:49:07 +00:00
2026-02-26 10:49:07 +00:00
2026-02-26 10:49:07 +00:00

OpenTelemetry Aspire Demo with Azure OpenAI

This demo showcases the integration of OpenTelemetry with the Microsoft Agent Framework using Azure OpenAI and .NET Aspire Dashboard for telemetry visualization.

Overview

The demo consists of three main components:

  1. Aspire Dashboard - Provides a web-based interface to visualize OpenTelemetry data
  2. Console Application - An interactive console application that demonstrates agent interactions with proper OpenTelemetry instrumentation
  3. [Optional] Application Insights - When the agent is deployed to a production environment, Application Insights can be used to monitor the agent performance.

Architecture

graph TD
    A["Console App<br/>(Interactive)"] --> B["Agent Framework<br/>with OpenTel<br/>Instrumentation"]
    B --> C["Azure OpenAI<br/>Service"]
    A --> D["Aspire Dashboard<br/>(OpenTelemetry Visualization)"]
    B --> D

Prerequisites

  • .NET 10 SDK or later
  • Azure OpenAI service endpoint and deployment configured
  • Azure CLI installed and authenticated (for Azure credential authentication)
  • Docker installed (for running Aspire Dashboard)
  • [Optional] Application Insights and Grafana

Configuration

Azure OpenAI Setup

Set the following environment variables:

$env:AZURE_OPENAI_ENDPOINT="https://your-resource.openai.azure.com/"
$env:AZURE_OPENAI_DEPLOYMENT_NAME="gpt-4o-mini"  # Optional, defaults to gpt-4o-mini

Note: This demo uses Azure CLI credentials for authentication. Make sure you're logged in with az login and have access to the Azure OpenAI resource.

[Optional] Application Insights Setup

Set the following environment variables:

$env:APPLICATIONINSIGHTS_CONNECTION_STRING="InstrumentationKey=XXXX;IngestionEndpoint=https://XXXX.applicationinsights.azure.com/;LiveEndpoint=https://XXXXX.livediagnostics.monitor.azure.com/;ApplicationId=XXXXX"

Running the Demo

Quick Start (Using Script)

The easiest way to run the demo is using the provided PowerShell script:

.\start-demo.ps1

This script will automatically:

  • βœ… Check prerequisites (Docker, Azure OpenAI configuration)
  • πŸ”¨ Build the console application
  • 🐳 Start the Aspire Dashboard via Docker (with anonymous access)
  • ⏳ Wait for dashboard to be ready (polls port until listening)
  • 🌐 Open your browser with the dashboard
  • πŸ“Š Configure telemetry endpoints (http://localhost:4317)
  • 🎯 Start the interactive console application

Manual Setup (Step by Step)

If you prefer to run the components manually:

Step 1: Start the Aspire Dashboard via Docker

docker run -d --name aspire-dashboard -p 4318:18888 -p 4317:18889 -e DOTNET_DASHBOARD_UNSECURED_ALLOW_ANONYMOUS=true mcr.microsoft.com/dotnet/aspire-dashboard:latest

Step 2: Access the Dashboard

Open your browser to: http://localhost:4318

Step 3: Run the Console Application

cd dotnet/demos/AgentOpenTelemetry
$env:OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4317"
dotnet run

Interacting with the Console Application

You should see a welcome message like:

=== OpenTelemetry Aspire Demo ===
This demo shows OpenTelemetry integration with the Agent Framework.
You can view the telemetry data in the Aspire Dashboard.
Type your message and press Enter. Type 'exit' or empty message to quit.

You:
  1. Type your message and press Enter to interact with the AI agent
  2. The agent will respond, and you can continue the conversation
  3. Type exit to stop the application

Note: Make sure the Aspire Dashboard is running before starting the console application, as the telemetry data will be sent to the dashboard.

Step 4: Test the Integration

  1. Start the Aspire Dashboard (if not already running)
  2. Run the Console Application in a separate terminal
  3. Send a test message like "Hello, how are you?"
  4. Check the Aspire Dashboard - you should see:
    • New traces appearing in the Traces tab
    • Each trace showing the complete agent interaction flow
    • Metrics in the Metrics tab showing token usage and duration
    • Logs in the Structured Logs tab with detailed information

Viewing Telemetry Data in Aspire Dashboard

Traces

  1. In the Aspire Dashboard, navigate to the Traces tab
  2. You'll see traces for each agent interaction
  3. Each trace contains:
    • An outer span for the entire agent interaction
    • Inner spans from the Agent Framework's OpenTelemetry instrumentation
    • Spans from HTTP calls to Azure OpenAI

Metrics

  1. Navigate to the Metrics tab
  2. View metrics related to:
    • Agent execution duration
    • Token usage (input/output tokens)
    • Request counts

Logs

  1. Navigate to the Structured Logs tab
  2. Filter by the console application to see detailed logs
  3. Logs include information about user inputs, agent responses, and any errors

[Optional] View Application Insights data in Grafana

Besides the Aspire Dashboard and the Application Insights native UI, you can also use Grafana to visualize the telemetry data in Application Insights. There are two tailored dashboards for you to get started quickly:

Agent Overview dashboard

Open dashboard in Azure portal: https://aka.ms/amg/dash/af-agent Agent Overview dashboard

Workflow Overview dashboard

Open dashboard in Azure portal: https://aka.ms/amg/dash/af-workflow Workflow Overview dashboard

Key Features Demonstrated

OpenTelemetry Integration

  • Automatic instrumentation of Agent Framework operations
  • Custom spans for user interactions
  • Proper span lifecycle management (create β†’ execute β†’ close)
  • Telemetry correlation across the entire request flow

Agent Framework Features

  • ChatClientAgent with Azure OpenAI integration
  • OpenTelemetry wrapper using .WithOpenTelemetry()
  • Conversation threading for multi-turn conversations
  • Error handling with telemetry correlation

Aspire Dashboard Features

  • Real-time telemetry visualization
  • Distributed tracing across services
  • Metrics and logging integration
  • Resource management and monitoring

Available Script

The demo includes a PowerShell script to make running the demo easy:

start-demo.ps1

Complete demo startup script that handles everything automatically.

Usage:

.\start-demo.ps1           # Start the complete demo

Features:

  • Automatic configuration detection - Checks for Azure OpenAI configuration
  • Project building - Automatically builds projects before running
  • Error handling - Provides clear error messages if something goes wrong
  • Multi-window support - Opens dashboard in separate window for better experience
  • Browser auto-launch - Automatically opens the Aspire Dashboard in your browser
  • Docker integration - Uses Docker to run the Aspire Dashboard

Docker Endpoints:

  • Aspire Dashboard: http://localhost:4318
  • OTLP Telemetry: http://localhost:4317

Troubleshooting

Port Conflicts

If you encounter port binding errors, try:

  1. Stop any existing Docker containers using the same ports (docker stop aspire-dashboard)
  2. Or kill any processes using the conflicting ports

Authentication Issues

  • Ensure your Azure OpenAI endpoint is correctly configured
  • Check that the environment variables are set in the correct terminal session
  • Verify you're logged in with Azure CLI (az login) and have access to the Azure OpenAI resource
  • Ensure the Azure OpenAI deployment name matches your actual deployment

Build Issues

  • Ensure you're using .NET 10.0 SDK
  • Run dotnet restore if you encounter package restore issues
  • Check that all project references are correctly resolved

Project Structure

AgentOpenTelemetry/
β”œβ”€β”€ AgentOpenTelemetry.csproj             # Project file with dependencies
β”œβ”€β”€ Program.cs                            # Main application with Azure OpenAI agent integration
β”œβ”€β”€ start-demo.ps1                        # PowerShell script to start the demo
└── README.md                             # This file

Next Steps

  • Experiment with different prompts to see various telemetry patterns
  • Explore the Aspire Dashboard's filtering and search capabilities
  • Try modifying the OpenTelemetry configuration to add custom metrics or spans
  • Integrate additional services to see distributed tracing in action