Feed
Pro
Search

Author

Write
Drafts

Bug0 - The AI-native e2e QA regression testing Passmark - The open-source AI framework for regression testing Hackathons Changelog Brand Hashnode gql skill - let your AI agent publish to your Hashnode blog The Foreword by Hashnode - official blog from the Hashnode team @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap
Sign in

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Observability in Microsoft Agent Framework through Open Telemetry in Azure Application Insights, KQL and Aspire on Docker" | Hashnode

FeedDiscussion

Sachin Nandanwar

Jun 22

Observability in Microsoft Agent Framework through Open Telemetry in Azure Application Insights, KQL and Aspire on Docker

In a typical Agent AI and Workflow setups when something goes wrong major questions start piling up: Which agent handled the request? Which tool was invoked? How long did each step take? Where did

azureguru.net8 min read

#ai #microsoft-agent-framework #observability #opentelemetry #opentelemetry-collector #ai-agent

Responses(2)

Suny Choudhary

Building AI Security for LLMs | CEO @ LangProtect

Agents without observability are just distributed bugs with better branding.

If you can’t trace the tool calls, handoffs, latency, and failures, you don’t really have an agent platform. You have a black box.

Jun 23

Sachin Nandanwar

Jun 27

Thank you for your comment.

Absolutely !!! Couldn't have said it more better . Agents are unpredictable .Observability isn't an optional implementation.. it's the foundation for debugging, optimization, and governance.

Through this article I tried to highlight the best tools at your disposal to implement observability in MAF . Soon I will be posting a new article how to leverage observability metrics and use them to build insightful dashboards in Grafana.