diff --git a/website/blog/2024-07-25-AgentOps/img/flow.png b/website/blog/2024-07-25-AgentOps/img/flow.png index e778719fdf9e..75adca023ec0 100644 Binary files a/website/blog/2024-07-25-AgentOps/img/flow.png and b/website/blog/2024-07-25-AgentOps/img/flow.png differ diff --git a/website/blog/2024-07-25-AgentOps/index.mdx b/website/blog/2024-07-25-AgentOps/index.mdx index ffeb47b967cd..3505c23065c8 100644 --- a/website/blog/2024-07-25-AgentOps/index.mdx +++ b/website/blog/2024-07-25-AgentOps/index.mdx @@ -1,5 +1,5 @@ # AgentOps, the Best Tool for AutoGen Agent Observability -![agents](img/badge.jpeg) +AgentOps and AutoGen ## TL;DR * AutoGen® offers detailed multi-agent observability with AgentOps. @@ -16,11 +16,13 @@ As agents evolve into even more powerful and complex tools, you should view them Agent observability, in its most basic form, allows you to monitor, troubleshoot, and clarify the actions of your agent during its operation. The ability to observe every detail of your agent's activity, right down to a timestamp, enables you to trace its actions precisely, identify areas for improvement, and understand the reasons behind any failures-— a key aspect of effective debugging. Beyond enhancing diagnostic precision, this level of observability is integral for your system's reliability. Think of it as the ability to identify and address issues before they spiral out of control. Observability isn't just about keeping things running smoothly and maximizing uptime; it's about strengthening your agent-based solutions. +AgentOps and AutoGen + ## Why AgentOps? AutoGen has simplified the process of building agents, yet we recognized the need for an easy-to-use, native tool for observability. We've previously discussed AgentOps, and now we're excited to partner with AgentOps as our official agent observability tool. Integrating AgentOps with AutoGen simplifies your workflow and boosts your agents' performance through clear observability, ensuring they operate optimally. For more details, check out our [AgentOps documentation](https://microsoft.github.io/autogen/docs/notebooks/agentchat_agentops/). -![agents](img/waterfall.jpeg) +Agent Session Replay Enterprises and enthusiasts trust AutoGen as the leader in building agents. With our partnership with AgentOps, developers can now natively debug agents for efficiency and ensure compliance, providing a comprehensive audit trail for all of your agents' activities. AgentOps allows you to monitor LLM calls, costs, latency, agent failures, multi-agent interactions, tool usage, session-wide statistics, and more all from one dashboard. @@ -42,7 +44,7 @@ agentops.init(os.environ["AGENTOPS_API_KEY"]) AgentOps includes all the functionality you need to ensure your agents are suitable for real-world, scalable solutions. -![agents](img/dashboard.jpeg) +AgentOps overview dashboard * **Analytics Dashboard:** The AgentOps Analytics Dashboard allows you to configure and assign agents and automatically track what actions each agent is taking simultaneously. When used with AutoGen, AgentOps is automatically configured for multi-agent compatibility, allowing users to track multiple agents across runs easily. Instead of a terminal-level screen, AgentOps provides a superior user experience with its intuitive interface. * **Tracking LLM Costs:** Cost tracking is natively set up within AgentOps and provides a rolling total. This allows developers to see and track their run costs and accurately predict future costs. @@ -56,7 +58,7 @@ AutoGen users also have access to the following features in AgentOps: * **Custom Tests:** Run your agents against domain-specific tests. * **Time Travel Debugging:** Save snapshots of session states to rewind and replay agent runs from chosen checkpoints. * **Compliance and Security:** Create audit logs and detect potential threats, such as profanity and leaks of Personally Identifiable Information. -* **Prompt Injection Detection: **Identify potential code injection and secret leaks. +* **Prompt Injection Detection:** Identify potential code injection and secret leaks. ## Conclusion