introduce AutoGen instrumentation.

[fenilfaldu]

📥 Pull Request

📘 Description

• Added AutoGen instrumentation modules to support agent interactions, including agent-specific instrumentors and utilities.
• Implemented new agent types and team structures for enhanced collaboration in AutoGen examples.
• Updated documentation and examples to reflect the new features and usage scenarios, including a GroupChat and Swarm team example.

🧪 Testing Tested Examples

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests.

:loudspeaker: Thoughts on this report? Let us know!

[Dwij1704]

What happened to LangGraph? lol

[Dwij1704]

I re ran it and it works

[fenilfaldu]

So our integration tests are randomly failing on push, different ones each time.

What I suspect: The validate_trace_spans() function (which I believe validates presence of LLM spans) is synchronous, while some of our examples involve async logic and await agent calls. There are chances the spans haven’t fully flushed/exported by the time validation kicks in.This might just be a race condition between span export and validation but this just all in theory for now.

[Dwij1704]

So our integration tests are randomly failing on push, different ones each time.

What I suspect: The validate_trace_spans() function (which I believe validates presence of LLM spans) is synchronous, while some of our examples involve async logic and await agent calls. There are chances the spans haven’t fully flushed/exported by the time validation kicks in.This might just be a race condition between span export and validation but this just all in theory for now.

Few examples are failing due to backend failure, o3 example is busted, @areibman pushed it yesterday as it was working on his machine, will need to check what the actual reason is behind its failure. ag2, web_search and mem0 were already busted, needs fixing as discussed yesterday.

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had any activity in the last 14 days.

If no updates are made within 7 days, this PR will be automatically closed.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11016360	Triggered	Generic Password	2ab32775d78d92e120fe97c9ba10ff39769548e3	app/.github/workflows/test-api.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}