foundry-observability

Wire shared App Insights telemetry across Bicep, hosted agents, and ACA workloads.

5|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-observability
Source: https://github.com/aiappsgbb/awesome-gbb/tree/main/skills/foundry-observability
Command: npx skills add https://github.com/aiappsgbb/awesome-gbb --skill foundry-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires azure-monitor-opentelemetry, and includes references (resource) components.

What problem does it solve?

This Skill fixes a silent telemetry gap where Foundry pilots deploy successfully but App Insights receives no traces, logs, or metrics due to missing or miswired observability connections across Bicep, hosted agents, and ACA workloads.

Core Features & Use Cases

  • End-to-end observability wiring: Provisions a single Log Analytics workspace and workspace-bound App Insights, then ensures every workload (MCP servers, bot service, workspace UI, ACA jobs, and cron-triggered containers) uses the same App Insights connection string.
  • Hosted-agent connection and RBAC setup: Creates the required account-level Foundry App Insights connection and applies the Monitoring Metrics Publisher RBAC to the platform-managed agent identities.
  • Operational diagnostics ready to use: Ships KQL queries to verify that any traces are arriving, to break down MCP tool calls, to debug silent cron failures, and to smoke-test first trace ingestion.
  • Silent-failure guardrails: Includes guidance and workarounds for real-world cases where platform auto-injection fails or returns credentials:null, requiring defensively guarded telemetry initialization.

Quick Start

Deploy the skill’s Bicep substrate and run the postprovision hook so the Foundry account gets an account-level App Insights connection and all hosted and ACA components start emitting telemetry.

Frequently Asked Questions about foundry-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my Azure AI Foundry agents producing no App Insights traces after a successful deployment?

Missing Azure AI Foundry telemetry often occurs when Bicep substrate, hosted-agent runtime, and ACA workloads lack a shared observability signal and properly wired App Insights connection strings. This Skill restores that missing end-to-end wiring.

How do I enable OpenTelemetry traces for Azure AI Foundry MCP servers and ACA workloads?

To enable OpenTelemetry traces, provision a workspace-bound App Insights instance, create an account-level Foundry connection, apply Monitoring Metrics Publisher RBAC, and run guarded telemetry initialization across all ACA workloads and MCP servers.

Do I need Monitoring Metrics Publisher RBAC for Azure AI Foundry hosted-agent telemetry?

Yes, applying the Monitoring Metrics Publisher RBAC to platform-managed agent identities is required to authorize telemetry emission from Azure AI Foundry hosted agents to the bound App Insights workspace.

What's the best way to verify Azure AI Foundry telemetry is reaching App Insights?

Running KQL smoke and diagnostic queries against your Log Analytics workspace is the best way to verify trace ingestion, break down MCP tool calls, and debug silent cron failures in Azure AI Foundry components.

How do I handle Azure AI Foundry platform auto-injection failures returning credentials null?

Handle credentials null auto-injection failures by implementing defensively guarded OpenTelemetry initialization in your hosted-agent runtime, ensuring telemetry gracefully degrades without crashing the Azure AI Foundry workload.