diff --git a/docs/ai/index.mdx b/docs/ai/index.mdx index ae54a06c2191b9..f3cfec913828bb 100644 --- a/docs/ai/index.mdx +++ b/docs/ai/index.mdx @@ -10,7 +10,7 @@ keywords: - MCP - Model Context Protocol - agent plugin - - AI monitoring + - AI observability - vibe coding - Claude - Cursor @@ -45,9 +45,9 @@ keywords: className="w-full md:w-[calc(50%-12px)]" /> diff --git a/docs/ai/monitoring/agents/getting-started.mdx b/docs/ai/monitoring/agents/getting-started.mdx deleted file mode 100644 index 2f1c90765248fc..00000000000000 --- a/docs/ai/monitoring/agents/getting-started.mdx +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Set Up -sidebar_order: 0 -description: "Learn how to set up Sentry AI Agent Monitoring" -keywords: - - AI agent setup - - agent monitoring setup - - OpenAI integration - - Anthropic integration - - LangChain integration - - Python AI - - Node.js AI - - React AI - - JavaScript AI - - React Native AI - - Next.js AI - - .NET AI - - dotnet AI ---- - -Sentry AI Agent Monitoring helps you track and debug AI agent applications using our supported SDKs and integrations. Monitor your complete agent workflows from user interaction to final response, including tool calls, model interactions, and custom logic. - -To use [Conversations](/ai/monitoring/conversations/), set a conversation ID for each chat. Sentry uses the `gen_ai.conversation.id` attribute to group related AI spans, and some SDK integrations set it automatically. - -To start sending AI agent data to Sentry, make sure you've created a Sentry project for your AI-enabled repository and follow one of the guides below: - -- [Python](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module) -- [Laravel](/platforms/php/guides/laravel/ai-monitoring/) -- [Node.js](/platforms/javascript/guides/node/ai-agent-monitoring/) -- [Browser (JavaScript)](/platforms/javascript/ai-agent-monitoring-browser/) -- [React](/platforms/javascript/guides/react/ai-agent-monitoring-browser/) -- [React Native](/platforms/react-native/ai-agent-monitoring/) -- [Next.js](/platforms/javascript/guides/nextjs/ai-agent-monitoring/) -- [.NET](/platforms/dotnet/tracing/instrumentation/ai-agents-module/) -- [Ruby](/platforms/ruby/tracing/instrumentation/custom-instrumentation/ai-agents-module/) - -After setting up, [name your agents](/ai/monitoring/agents/naming/) so they appear as identifiable entries in the AI Agents dashboard. - - - -You can also instrument AI agents manually by following our [manual instrumentation guides](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module). - - diff --git a/docs/ai/monitoring/agents/index.mdx b/docs/ai/monitoring/agents/index.mdx deleted file mode 100644 index 4636800e5ea966..00000000000000 --- a/docs/ai/monitoring/agents/index.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: AI Agents -sidebar_order: 10 -description: >- - Learn how to use Sentry's AI Agent monitoring tools to trace and debug your AI - agent workflows, including agent runs, tool calls, and model interactions. -keywords: - - AI agents - - LLM monitoring - - agent monitoring - - tool calls - - OpenAI - - Anthropic - - LangChain - - token usage - - agent tracing -og_image: /og-images/ai-monitoring-agents.png ---- - -Sentry's AI Agent monitoring tools help you understand what's going on with your AI agent workflows. They automatically collect information about agent runs, tool calls, model interactions, and errors across your entire AI pipeline—from user interaction to final response. - -## Example AI Agent Monitoring Use Cases - -- Your AI agent is failing silently during tool execution, and you want to trace the complete agent flow to identify where it's breaking. -- Users report that your AI agent is returning unexpected or malformed responses, and you need to debug the full context of prompts, model calls, and outputs. -- Your AI agent workflows are experiencing performance issues, and you want to identify which steps (model calls, tool usage, or custom logic) are causing bottlenecks. - -## Get Started - -To use AI Agent Monitoring, you must have an existing Sentry account and project set up. If you don't have one, [create an account here](https://sentry.io/signup/). - -![AI Agents Monitoring Overview](./img/overview.png) - -Learn how to [set up Sentry for AI Agents](/ai/monitoring/agents/getting-started/) and [name your agents](/ai/monitoring/agents/naming/) so they're identifiable in the dashboard. diff --git a/docs/ai/monitoring/agents/costs.mdx b/docs/ai/observability/agents/costs.mdx similarity index 92% rename from docs/ai/monitoring/agents/costs.mdx rename to docs/ai/observability/agents/costs.mdx index 99e11614333a8c..71c6a34af706af 100644 --- a/docs/ai/monitoring/agents/costs.mdx +++ b/docs/ai/observability/agents/costs.mdx @@ -4,7 +4,7 @@ sidebar_order: 15 description: Learn how Sentry calculates AI model costs, where pricing data comes from, and what's not covered. --- -The **Model Cost** widget in the [AI Agents Dashboard](/ai/monitoring/agents/dashboards/) Models tab shows estimated costs for your LLM usage. This page explains how those costs are calculated. +The **Model Cost** widget in the [AI Agents Dashboard](/ai/observability/agents/dashboards/) Models tab shows estimated costs for your LLM usage. This page explains how those costs are calculated. ## Data Sources @@ -67,5 +67,5 @@ Cost estimates only account for **token-based pricing**. The following are **not If you're using manual instrumentation and your costs look unexpected (for example, negative costs), the most common cause is incorrectly set token attributes. See the "Token Usage and Cost Gotchas" section on the manual instrumentation page for your platform: - [Python](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module/#token-usage-and-cost-gotchas) -- [JavaScript](/platforms/javascript/guides/node/ai-agent-monitoring/#token-usage-and-cost-gotchas) +- [JavaScript](/platforms/javascript/guides/node/agent-tracing/#token-usage-and-cost-gotchas) - [Ruby](/platforms/ruby/tracing/instrumentation/custom-instrumentation/ai-agents-module/#token-usage-and-cost-gotchas) diff --git a/docs/ai/monitoring/agents/dashboards.mdx b/docs/ai/observability/agents/dashboards.mdx similarity index 81% rename from docs/ai/monitoring/agents/dashboards.mdx rename to docs/ai/observability/agents/dashboards.mdx index 6a602e8338ccfe..dec122a0240383 100644 --- a/docs/ai/monitoring/agents/dashboards.mdx +++ b/docs/ai/observability/agents/dashboards.mdx @@ -12,9 +12,9 @@ keywords: og_image: /og-images/ai-monitoring-agents-dashboard.png --- -The AI Agents [Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=agents&sort=mostPopular) provide a comprehensive view of your AI workflows, including executions, model costs and token usage, tool calls, and recent errors. Once you've [configured the Sentry SDK](/ai/monitoring/agents/getting-started/) for your AI agent project, telemetry data is collected and displayed in the dashboard to support analysis of system behavior and performance. +The AI Agents [Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=agents&sort=mostPopular) provide a comprehensive view of your AI workflows, including executions, model costs and token usage, tool calls, and recent errors. Once you've [configured the Sentry SDK](/ai/observability/agents/getting-started/) for your AI agent project, telemetry data is collected and displayed in the dashboard to support analysis of system behavior and performance. -AI Agent monitoring have three dashboards: +Agent tracing have three dashboards: - [Overview](#overview) - [Models](#models) diff --git a/docs/ai/observability/agents/getting-started.mdx b/docs/ai/observability/agents/getting-started.mdx new file mode 100644 index 00000000000000..3abf02cf805789 --- /dev/null +++ b/docs/ai/observability/agents/getting-started.mdx @@ -0,0 +1,43 @@ +--- +title: Set Up +sidebar_order: 0 +description: "Learn how to set up Sentry Agent Tracing" +keywords: + - AI agent setup + - agent tracing setup + - OpenAI integration + - Anthropic integration + - LangChain integration + - Python AI + - Node.js AI + - React AI + - JavaScript AI + - React Native AI + - Next.js AI + - .NET AI + - dotnet AI +--- + +Sentry Agent Tracing helps you track and debug AI agent applications using our supported SDKs and integrations. Monitor your complete agent workflows from user interaction to final response, including tool calls, model interactions, and custom logic. + +To use [Conversations](/ai/observability/conversations/), set a conversation ID for each chat. Sentry uses the `gen_ai.conversation.id` attribute to group related AI spans, and some SDK integrations set it automatically. + +To start sending AI agent data to Sentry, make sure you've created a Sentry project for your AI-enabled repository and follow one of the guides below: + +- [Python](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module) +- [Laravel](/platforms/php/guides/laravel/agent-tracing/) +- [Node.js](/platforms/javascript/guides/node/agent-tracing/) +- [Browser (JavaScript)](/platforms/javascript/agent-tracing-browser/) +- [React](/platforms/javascript/guides/react/agent-tracing-browser/) +- [React Native](/platforms/react-native/agent-tracing/) +- [Next.js](/platforms/javascript/guides/nextjs/agent-tracing/) +- [.NET](/platforms/dotnet/tracing/instrumentation/ai-agents-module/) +- [Ruby](/platforms/ruby/tracing/instrumentation/custom-instrumentation/ai-agents-module/) + +After setting up, [name your agents](/ai/observability/agents/naming/) so they appear as identifiable entries in the AI Agents dashboard. + + + +You can also instrument AI agents manually by following our [manual instrumentation guides](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module). + + diff --git a/docs/ai/monitoring/agents/img/advanced-scrubbing-rule.png b/docs/ai/observability/agents/img/advanced-scrubbing-rule.png similarity index 100% rename from docs/ai/monitoring/agents/img/advanced-scrubbing-rule.png rename to docs/ai/observability/agents/img/advanced-scrubbing-rule.png diff --git a/docs/ai/monitoring/agents/img/overview.png b/docs/ai/observability/agents/img/overview.png similarity index 100% rename from docs/ai/monitoring/agents/img/overview.png rename to docs/ai/observability/agents/img/overview.png diff --git a/docs/ai/observability/agents/index.mdx b/docs/ai/observability/agents/index.mdx new file mode 100644 index 00000000000000..7ca427be75a4fa --- /dev/null +++ b/docs/ai/observability/agents/index.mdx @@ -0,0 +1,34 @@ +--- +title: AI Agents +sidebar_order: 10 +description: >- + Learn how to use Sentry's Agent tracing tools to trace and debug your AI + agent workflows, including agent runs, tool calls, and model interactions. +keywords: + - AI agents + - LLM monitoring + - agent tracing + - tool calls + - OpenAI + - Anthropic + - LangChain + - token usage + - agent tracing +og_image: /og-images/ai-monitoring-agents.png +--- + +Sentry's Agent tracing tools help you understand what's going on with your AI agent workflows. They automatically collect information about agent runs, tool calls, model interactions, and errors across your entire AI pipeline—from user interaction to final response. + +## Example Agent Tracing Use Cases + +- Your AI agent is failing silently during tool execution, and you want to trace the complete agent flow to identify where it's breaking. +- Users report that your AI agent is returning unexpected or malformed responses, and you need to debug the full context of prompts, model calls, and outputs. +- Your AI agent workflows are experiencing performance issues, and you want to identify which steps (model calls, tool usage, or custom logic) are causing bottlenecks. + +## Get Started + +To use Agent Tracing, you must have an existing Sentry account and project set up. If you don't have one, [create an account here](https://sentry.io/signup/). + +![Agents Tracing Overview](./img/overview.png) + +Learn how to [set up Sentry for AI Agents](/ai/observability/agents/getting-started/) and [name your agents](/ai/observability/agents/naming/) so they're identifiable in the dashboard. diff --git a/docs/ai/monitoring/agents/naming.mdx b/docs/ai/observability/agents/naming.mdx similarity index 92% rename from docs/ai/monitoring/agents/naming.mdx rename to docs/ai/observability/agents/naming.mdx index 4726cda76aa073..8b6771741f41a6 100644 --- a/docs/ai/monitoring/agents/naming.mdx +++ b/docs/ai/observability/agents/naming.mdx @@ -6,11 +6,11 @@ keywords: - AI agents - agent name - gen_ai.agent.name - - agent monitoring + - agent tracing - agent identification --- -Sentry uses the `gen_ai.agent.name` span attribute to identify agents in the [AI Agents Dashboard](/ai/monitoring/agents/dashboards/). Without a name, you won't be able to filter for a specific agent, group results by agent, or set up alerts for individual agents. +Sentry uses the `gen_ai.agent.name` span attribute to identify agents in the [AI Agents Dashboard](/ai/observability/agents/dashboards/). Without a name, you won't be able to filter for a specific agent, group results by agent, or set up alerts for individual agents. ## Quick Reference @@ -219,7 +219,7 @@ const agent = new Agent({ }); ``` - + Mastra integration docs @@ -285,10 +285,10 @@ await Sentry.startSpan( ); ``` -See [JavaScript manual instrumentation](/platforms/javascript/guides/node/ai-agent-monitoring/#invoke-agent-span) for full span attributes. +See [JavaScript manual instrumentation](/platforms/javascript/guides/node/agent-tracing/#invoke-agent-span) for full span attributes. ## Next Steps -- [AI Agents Dashboard](/ai/monitoring/agents/dashboards/) — view and filter agents by name -- [Data Privacy](/ai/monitoring/agents/privacy/) — control what data is sent to Sentry -- [Model Costs](/ai/monitoring/agents/costs/) — track token usage and estimated costs +- [AI Agents Dashboard](/ai/observability/agents/dashboards/) — view and filter agents by name +- [Data Privacy](/ai/observability/agents/privacy/) — control what data is sent to Sentry +- [Model Costs](/ai/observability/agents/costs/) — track token usage and estimated costs diff --git a/docs/ai/monitoring/agents/privacy.mdx b/docs/ai/observability/agents/privacy.mdx similarity index 98% rename from docs/ai/monitoring/agents/privacy.mdx rename to docs/ai/observability/agents/privacy.mdx index 532ea9b2854505..a652f13ec9e888 100644 --- a/docs/ai/monitoring/agents/privacy.mdx +++ b/docs/ai/observability/agents/privacy.mdx @@ -3,7 +3,7 @@ title: Data Privacy sidebar_order: 20 description: >- Learn how to control data collection and protect sensitive information in AI - agent monitoring. + agent tracing. keywords: - AI privacy - PII diff --git a/docs/ai/monitoring/agents/sampling.mdx b/docs/ai/observability/agents/sampling.mdx similarity index 96% rename from docs/ai/monitoring/agents/sampling.mdx rename to docs/ai/observability/agents/sampling.mdx index fab702af67a589..e0f9e14546caaa 100644 --- a/docs/ai/monitoring/agents/sampling.mdx +++ b/docs/ai/observability/agents/sampling.mdx @@ -191,6 +191,6 @@ sentry_sdk.logger.info( ## Next Steps -- [Getting Started](/ai/monitoring/agents/getting-started/) -- [Model Costs](/ai/monitoring/agents/costs/) -- [AI Agents Dashboard](/ai/monitoring/agents/dashboards/) +- [Getting Started](/ai/observability/agents/getting-started/) +- [Model Costs](/ai/observability/agents/costs/) +- [AI Agents Dashboard](/ai/observability/agents/dashboards/) diff --git a/docs/ai/monitoring/conversations/img/conversations-detail.png b/docs/ai/observability/conversations/img/conversations-detail.png similarity index 100% rename from docs/ai/monitoring/conversations/img/conversations-detail.png rename to docs/ai/observability/conversations/img/conversations-detail.png diff --git a/docs/ai/monitoring/conversations/img/conversations-list.png b/docs/ai/observability/conversations/img/conversations-list.png similarity index 100% rename from docs/ai/monitoring/conversations/img/conversations-list.png rename to docs/ai/observability/conversations/img/conversations-list.png diff --git a/docs/ai/monitoring/conversations/index.mdx b/docs/ai/observability/conversations/index.mdx similarity index 90% rename from docs/ai/monitoring/conversations/index.mdx rename to docs/ai/observability/conversations/index.mdx index 40bd0276e1b870..eb03564ac20e84 100644 --- a/docs/ai/monitoring/conversations/index.mdx +++ b/docs/ai/observability/conversations/index.mdx @@ -28,9 +28,9 @@ You can find it in **Explore > Conversations** in the Sentry sidebar. ## Prerequisites -Conversations are built on top of [AI Agent Monitoring](/ai/monitoring/agents/). Before you can use them, you need: +Conversations are built on top of [Agent Tracing](/ai/observability/agents/). Before you can use them, you need: -1. **Tracing enabled** with the Sentry SDK configured for your AI agent project. Follow the [Agent Monitoring getting started guide](/ai/monitoring/agents/getting-started/) if you haven't already. +1. **Tracing enabled** with the Sentry SDK configured for your AI agent project. Follow the [Agent Tracing getting started guide](/ai/observability/agents/getting-started/) if you haven't already. 2. **A conversation ID on your spans.** Sentry groups spans into conversations using the `gen_ai.conversation.id` attribute. You can set this manually, or some SDK integrations infer it automatically. @@ -38,11 +38,11 @@ Conversations are built on top of [AI Agent Monitoring](/ai/monitoring/agents/). A conversation is a collection of spans that share the same `gen_ai.conversation.id`. This is typically the ID of the chat session in your application (for example, the session ID you store in your database). -Some SDK integrations (such as OpenAI Agents SDK for Python and OpenAI SDK for Node) automatically infer the conversation ID. For all other integrations, you need to set it manually. See your platform's AI agent monitoring guide for setup instructions: +Some SDK integrations (such as OpenAI Agents SDK for Python and OpenAI SDK for Node) automatically infer the conversation ID. For all other integrations, you need to set it manually. See your platform's Agent tracing guide for setup instructions: -- [JavaScript/Node](/platforms/javascript/guides/node/ai-agent-monitoring/#tracking-conversations) +- [JavaScript/Node](/platforms/javascript/guides/node/agent-tracing/#tracking-conversations) - [Python](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module/#tracking-conversations) -- [Laravel](/platforms/php/guides/laravel/ai-monitoring/#conversations) +- [Laravel](/platforms/php/guides/laravel/agent-tracing/#conversations) ### Choosing a Conversation ID diff --git a/docs/ai/monitoring/index.mdx b/docs/ai/observability/index.mdx similarity index 85% rename from docs/ai/monitoring/index.mdx rename to docs/ai/observability/index.mdx index c6c1fefced2a8b..679d25bf7cc0b3 100644 --- a/docs/ai/monitoring/index.mdx +++ b/docs/ai/observability/index.mdx @@ -1,11 +1,11 @@ --- -title: AI Monitoring +title: AI Observability sidebar_order: 30 description: "Monitor your AI agents and MCP servers in production with Sentry. Track LLM calls, token usage, tool executions, and agent handoffs." keywords: - - AI monitoring + - AI observability - LLM monitoring - - agent monitoring + - agent tracing - MCP monitoring - token usage - AI observability @@ -16,21 +16,21 @@ Sentry provides comprehensive monitoring for your AI implementations. Whether yo Sentry AI Agent Monitoring, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry Agent Tracing, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data will be fully connected to your other Sentry data like logs, errors, and traces. -As a prerequisite to setting up AI Agent Monitoring with .NET, you'll need to first set up tracing. Once this is done, you can use the `Sentry.Extensions.AI` package to automatically instrument AI agents created with `Microsoft.Extensions.AI`. +As a prerequisite to setting up Agent Tracing with .NET, you'll need to first set up tracing. Once this is done, you can use the `Sentry.Extensions.AI` package to automatically instrument AI agents created with `Microsoft.Extensions.AI`. ## Installation @@ -33,7 +33,7 @@ The `Sentry.Extensions.AI` package provides automatic instrumentation for AI age ### Basic Setup -AI Agent monitoring is marked as experimental. You may encounter unexpected behaviour from this SDK. +Agent tracing is marked as experimental. You may encounter unexpected behaviour from this SDK. To instrument your AI agent, simply call `IChatClient.AddSentry()` before building your chat client. If your AI agent uses tools (function calling), you can instrument them using the `AddSentryToolInstrumentation()` extension method on `ChatOptions`: @@ -106,7 +106,7 @@ Name of the AI Agent. This name will be used to identify the agent in the Sentry ## ASP.NET Core Integration -For ASP.NET Core applications, you can integrate Sentry AI Agent monitoring as follows: +For ASP.NET Core applications, you can integrate Sentry Agent tracing as follows: ```csharp var builder = WebApplication.CreateBuilder(args); diff --git a/docs/platforms/javascript/common/ai-agent-monitoring-browser/index.mdx b/docs/platforms/javascript/common/agent-tracing-browser/index.mdx similarity index 65% rename from docs/platforms/javascript/common/ai-agent-monitoring-browser/index.mdx rename to docs/platforms/javascript/common/agent-tracing-browser/index.mdx index 717d07b96496a9..0927c1e9229953 100644 --- a/docs/platforms/javascript/common/ai-agent-monitoring-browser/index.mdx +++ b/docs/platforms/javascript/common/agent-tracing-browser/index.mdx @@ -1,6 +1,6 @@ --- -title: Browser AI Monitoring -sidebar_title: AI Agent Monitoring +title: Browser AI Tracing +sidebar_title: Agent Tracing sidebar_order: 7 description: "Learn how to manually instrument AI agents in browser applications." sidebar_section: features @@ -44,11 +44,11 @@ notSupported: - javascript.capacitor --- -With Sentry AI Agent Monitoring, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry Agent Tracing, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data will be fully connected to your other Sentry data like logs, errors, and traces. ## Prerequisites -Before setting up AI Agent Monitoring, ensure you have tracing enabled in your Sentry configuration. +Before setting up Agent Tracing, ensure you have tracing enabled in your Sentry configuration. @@ -56,4 +56,4 @@ Before setting up AI Agent Monitoring, ensure you have + diff --git a/docs/platforms/javascript/common/ai-agent-monitoring/index.mdx b/docs/platforms/javascript/common/agent-tracing/index.mdx similarity index 93% rename from docs/platforms/javascript/common/ai-agent-monitoring/index.mdx rename to docs/platforms/javascript/common/agent-tracing/index.mdx index 5fc65d54d1b746..4a9f3f7728b3c8 100644 --- a/docs/platforms/javascript/common/ai-agent-monitoring/index.mdx +++ b/docs/platforms/javascript/common/agent-tracing/index.mdx @@ -1,6 +1,6 @@ --- -title: Set Up AI Agent Monitoring -sidebar_title: AI Agent Monitoring +title: Set Up Agent Tracing +sidebar_title: Agent Tracing sidebar_order: 7 description: "Monitor AI agents with token usage, latency, tool execution, and error tracking." sidebar_section: features @@ -30,13 +30,13 @@ supported: - javascript.nitro --- -With Sentry AI Agent Monitoring, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry Agent Tracing, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data will be fully connected to your other Sentry data like logs, errors, and traces. ## Prerequisites -Before setting up AI Agent Monitoring, ensure you have tracing enabled in your Sentry configuration. +Before setting up Agent Tracing, ensure you have tracing enabled in your Sentry configuration. ## Automatic Instrumentation @@ -120,7 +120,7 @@ Sentry.init({ ### Streaming Gen AI Spans -`gen_ai` spans are sent as standalone envelope items instead of being bundled in the transaction by default (since SDK version `10.61.0`). This prevents AI spans with large inputs and outputs from hitting transaction payload size limits and being dropped, and is required for Conversations to work. +`gen_ai` spans are sent as standalone envelope items instead of being bundled in the transaction by default (since SDK version `10.61.0`). This prevents AI spans with large inputs and outputs from hitting transaction payload size limits and being dropped, and is required for Conversations to work. To send `gen_ai` spans as part of the transaction instead, set `streamGenAiSpans` to `false`. Self-hosted Sentry users should set this to `false`, as standalone `gen_ai` spans may not be ingested by their Sentry instance. @@ -192,7 +192,7 @@ Sentry.setConversationId(null); ## Identifying Users in Conversations -The [Conversations](/ai/monitoring/conversations/) view includes a **User** column. To populate it, call `setUser` once per request or session, before any AI calls: +The [Conversations](/ai/observability/conversations/) view includes a **User** column. To populate it, call `setUser` once per request or session, before any AI calls: ```javascript import * as Sentry from "___SDK_PACKAGE___"; @@ -297,7 +297,7 @@ await Sentry.startSpan( -For a complete guide on naming agents across all supported frameworks, see [Naming Your Agents](/ai/monitoring/agents/naming/). +For a complete guide on naming agents across all supported frameworks, see [Naming Your Agents](/ai/observability/agents/naming/). @@ -456,7 +456,7 @@ async function callLLMStreaming(model, messages) { If you're using an AI framework with a Sentry exporter, you can send traces to Sentry: -- Mastra Sentry Exporter +- Mastra Sentry Exporter ## MCP Server Monitoring diff --git a/docs/platforms/javascript/common/ai-agent-monitoring/mastra.mdx b/docs/platforms/javascript/common/agent-tracing/mastra.mdx similarity index 100% rename from docs/platforms/javascript/common/ai-agent-monitoring/mastra.mdx rename to docs/platforms/javascript/common/agent-tracing/mastra.mdx diff --git a/docs/platforms/javascript/common/configuration/apis.mdx b/docs/platforms/javascript/common/configuration/apis.mdx index d34f84e0f3e1a2..4bcba3d06c4174 100644 --- a/docs/platforms/javascript/common/configuration/apis.mdx +++ b/docs/platforms/javascript/common/configuration/apis.mdx @@ -903,7 +903,7 @@ Sentry.setConversationId(null); -See AI Agent Monitoring for more information on tracking AI conversations. +See Agent Tracing for more information on tracking AI conversations. diff --git a/docs/platforms/javascript/common/configuration/integrations/anthropic.mdx b/docs/platforms/javascript/common/configuration/integrations/anthropic.mdx index 050749691ddc1c..01654acd4fabdc 100644 --- a/docs/platforms/javascript/common/configuration/integrations/anthropic.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/anthropic.mdx @@ -125,7 +125,7 @@ Defaults to `true` if `dataCollection.genAI.outputs` is `true` (which is the def ```javascript Sentry.init({ dsn: "____PUBLIC_DSN____", - // Tracing must be enabled for agent monitoring to work + // Tracing must be enabled for agent tracing to work tracesSampleRate: 1.0, integrations: [ Sentry.anthropicAIIntegration({ diff --git a/docs/platforms/javascript/common/configuration/integrations/google-genai.mdx b/docs/platforms/javascript/common/configuration/integrations/google-genai.mdx index bf1999998807a6..1e0dc646c59b08 100644 --- a/docs/platforms/javascript/common/configuration/integrations/google-genai.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/google-genai.mdx @@ -121,7 +121,7 @@ Using the `googleGenAIIntegration` integration for **automatic instrumentation** ```javascript Sentry.init({ dsn: "____PUBLIC_DSN____", - // Tracing must be enabled for agent monitoring to work + // Tracing must be enabled for agent tracing to work tracesSampleRate: 1.0, integrations: [ Sentry.googleGenAIIntegration({ diff --git a/docs/platforms/javascript/common/configuration/integrations/langchain.mdx b/docs/platforms/javascript/common/configuration/integrations/langchain.mdx index 49fbb2dd54d4d5..c3815b476be7f2 100644 --- a/docs/platforms/javascript/common/configuration/integrations/langchain.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/langchain.mdx @@ -125,7 +125,7 @@ Using the `langChainIntegration` integration for **automatic instrumentation**: ```javascript Sentry.init({ dsn: "____PUBLIC_DSN____", - // Tracing must be enabled for agent monitoring to work + // Tracing must be enabled for agent tracing to work tracesSampleRate: 1.0, integrations: [ Sentry.langChainIntegration({ diff --git a/docs/platforms/javascript/common/configuration/integrations/langgraph.mdx b/docs/platforms/javascript/common/configuration/integrations/langgraph.mdx index a069558e64f048..19c42ea57b0eb8 100644 --- a/docs/platforms/javascript/common/configuration/integrations/langgraph.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/langgraph.mdx @@ -147,7 +147,7 @@ Using the `langGraphIntegration` integration for **automatic instrumentation**: ```javascript Sentry.init({ dsn: "____PUBLIC_DSN____", - // Tracing must be enabled for agent monitoring to work + // Tracing must be enabled for agent tracing to work tracesSampleRate: 1.0, integrations: [ Sentry.langGraphIntegration({ diff --git a/docs/platforms/javascript/common/configuration/integrations/openai.mdx b/docs/platforms/javascript/common/configuration/integrations/openai.mdx index 032521ee2853ec..e32019c0bb161a 100644 --- a/docs/platforms/javascript/common/configuration/integrations/openai.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/openai.mdx @@ -125,7 +125,7 @@ Using the `openAIIntegration` integration for **automatic instrumentation**: ```javascript Sentry.init({ dsn: "____PUBLIC_DSN____", - // Tracing must be enabled for agent monitoring to work + // Tracing must be enabled for agent tracing to work tracesSampleRate: 1.0, integrations: [ Sentry.openAIIntegration({ diff --git a/docs/platforms/javascript/common/tracing/instrumentation/mcp-module.mdx b/docs/platforms/javascript/common/tracing/instrumentation/mcp-module.mdx index 508f78c19d152d..010a32c5497087 100644 --- a/docs/platforms/javascript/common/tracing/instrumentation/mcp-module.mdx +++ b/docs/platforms/javascript/common/tracing/instrumentation/mcp-module.mdx @@ -26,7 +26,7 @@ supported: - javascript.tanstackstart-react --- -With Sentry's [MCP monitoring](/ai/monitoring/mcp/), you can track and debug MCP servers with full-stack context. You'll be able to monitor tool executions, prompt retrievals, resource access, and error rates. MCP monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry's [MCP monitoring](/ai/observability/mcp/), you can track and debug MCP servers with full-stack context. You'll be able to monitor tool executions, prompt retrievals, resource access, and error rates. MCP monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. As a prerequisite to setting up MCP monitoring with JavaScript, you'll need to first set up tracing. Once this is done, the JavaScript SDK will automatically instrument MCP servers created with supported libraries. If that doesn't fit your use case, you can use custom instrumentation described below. @@ -34,7 +34,7 @@ As a prerequisite to setting up MCP monitoring with JavaScript, you'll need to f The JavaScript SDK supports automatic instrumentation for MCP servers. We recommend adding the MCP integration to your Sentry configuration to automatically capture spans for MCP operations. -- [MCP (Model Context Protocol)](/ai/monitoring/mcp/getting-started/) +- [MCP (Model Context Protocol)](/ai/observability/mcp/getting-started/) ## Manual Instrumentation diff --git a/docs/platforms/javascript/guides/nextjs/index.mdx b/docs/platforms/javascript/guides/nextjs/index.mdx index ee4cea898ee1b7..f6797e3b824959 100644 --- a/docs/platforms/javascript/guides/nextjs/index.mdx +++ b/docs/platforms/javascript/guides/nextjs/index.mdx @@ -350,7 +350,7 @@ You've successfully integrated Sentry into your Next.js application! Here's what - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - [Logs Integrations](/platforms/javascript/guides/nextjs/logs/#integrations) - Connect popular logging libraries like Pino, Winston, and Bunyan - [Distributed Tracing](/platforms/javascript/guides/nextjs/tracing/distributed-tracing/) - Trace requests across services and microservices -- [AI Agent Monitoring](/platforms/javascript/guides/nextjs/ai-agent-monitoring/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more +- [Agent Tracing](/platforms/javascript/guides/nextjs/agent-tracing/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more - [Connect GitHub + Seer](/integrations/source-code-mgmt/github/#installing-github) - Enable AI-powered [root cause analysis](/product/ai-in-sentry/seer/) by connecting your GitHub repository - [Configuration Options](/platforms/javascript/guides/nextjs/configuration/) - Explore extended SDK configuration options diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx index 69fdbf11164c4e..0e604cd7b5785c 100644 --- a/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx +++ b/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx @@ -608,7 +608,7 @@ You've successfully integrated Sentry into your Next.js application! Here's what - [Logs Integrations](/platforms/javascript/guides/nextjs/logs/#integrations) - Connect popular logging libraries like Pino, Winston, and Bunyan - [Distributed Tracing](/platforms/javascript/guides/nextjs/tracing/distributed-tracing/) - Trace requests across services and microservices -- [AI Agent Monitoring](/platforms/javascript/guides/nextjs/ai-agent-monitoring/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more +- [Agent Tracing](/platforms/javascript/guides/nextjs/agent-tracing/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more - [Connect GitHub + Seer](/integrations/source-code-mgmt/github/#installing-github) - Enable AI-powered [root cause analysis](/product/ai-in-sentry/seer/) by connecting your GitHub repository - [Configuration Options](/platforms/javascript/guides/nextjs/configuration/) - Explore extended SDK configuration options diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx index 0ecf0c5a244963..e2d95a03f87140 100644 --- a/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx +++ b/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx @@ -488,7 +488,7 @@ If your application uses both the App Router and Pages Router: - [Logs Integrations](/platforms/javascript/guides/nextjs/logs/#integrations) - Connect popular logging libraries like Pino, Winston, and Bunyan - [Distributed Tracing](/platforms/javascript/guides/nextjs/tracing/distributed-tracing/) - Trace requests across services and microservices -- [AI Agent Monitoring](/platforms/javascript/guides/nextjs/ai-agent-monitoring/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more +- [Agent Tracing](/platforms/javascript/guides/nextjs/agent-tracing/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more - [Connect GitHub + Seer](/integrations/source-code-mgmt/github/#installing-github) - Enable AI-powered [root cause analysis](/product/ai-in-sentry/seer/) - [Configuration Options](/platforms/javascript/guides/nextjs/configuration/) - Explore extended SDK configuration diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/webpack-setup.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/webpack-setup.mdx index f643f30c37bc1d..ce1a7a146c255b 100644 --- a/docs/platforms/javascript/guides/nextjs/manual-setup/webpack-setup.mdx +++ b/docs/platforms/javascript/guides/nextjs/manual-setup/webpack-setup.mdx @@ -399,6 +399,6 @@ export default withSentryConfig(nextConfig, { - [Logs Integrations](/platforms/javascript/guides/nextjs/logs/#integrations) - Connect popular logging libraries like Pino, Winston, and Bunyan - [Distributed Tracing](/platforms/javascript/guides/nextjs/tracing/distributed-tracing/) - Trace requests across services and microservices -- [AI Agent Monitoring](/platforms/javascript/guides/nextjs/ai-agent-monitoring/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more +- [Agent Tracing](/platforms/javascript/guides/nextjs/agent-tracing/) - Monitor AI agents built with Vercel AI SDK, LangChain, and more - [Connect GitHub + Seer](/integrations/source-code-mgmt/github/#installing-github) - Enable AI-powered [root cause analysis](/product/ai-in-sentry/seer/) - [Configuration Options](/platforms/javascript/guides/nextjs/configuration/) - Explore extended SDK configuration diff --git a/docs/platforms/php/guides/laravel/ai-monitoring/index.mdx b/docs/platforms/php/guides/laravel/agent-tracing/index.mdx similarity index 88% rename from docs/platforms/php/guides/laravel/ai-monitoring/index.mdx rename to docs/platforms/php/guides/laravel/agent-tracing/index.mdx index 71c8155111d52c..c1decbaf5ec280 100644 --- a/docs/platforms/php/guides/laravel/ai-monitoring/index.mdx +++ b/docs/platforms/php/guides/laravel/agent-tracing/index.mdx @@ -1,6 +1,6 @@ --- -title: Set Up AI Agent Monitoring -sidebar_title: AI Agent Monitoring +title: Set Up Agent Tracing +sidebar_title: Agent Tracing sidebar_order: 5 sidebar_section: features description: "Monitor Laravel AI agents with token usage, latency, tool execution, and error tracking." @@ -13,7 +13,7 @@ This feature is currently in Beta. Beta features are still in progress and may h -With Sentry AI Agent Monitoring, you can monitor and debug your Laravel AI agents with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data is connected to your other Sentry data like logs, errors, and traces. +With Sentry Agent Tracing, you can monitor and debug your Laravel AI agents with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data is connected to your other Sentry data like logs, errors, and traces. @@ -27,7 +27,7 @@ With Sentry AI Agent MonitoringAI Agent Monitoring. The more specific `gen_ai_*` options let you disable individual AI span types while keeping the rest of AI monitoring enabled. +The `gen_ai` option is the master switch for Agent Tracing. The more specific `gen_ai_*` options let you disable individual AI span types while keeping the rest of AI tracing enabled. diff --git a/docs/platforms/php/guides/laravel/data-management/data-collected.mdx b/docs/platforms/php/guides/laravel/data-management/data-collected.mdx index f465e41c3fe98f..2cedc4b317e640 100644 --- a/docs/platforms/php/guides/laravel/data-management/data-collected.mdx +++ b/docs/platforms/php/guides/laravel/data-management/data-collected.mdx @@ -55,7 +55,7 @@ If you want to prevent bodies from being sent to Sentry altogether, set `max_req ## Laravel AI -When AI Agent Monitoring is active, Sentry collects metadata about AI agent activity. This can include agent names, provider names, model names, token usage, streaming state, finish reasons, conversation IDs, tool names, tool descriptions, and tool schemas. +When Agent Tracing is active, Sentry collects metadata about AI agent activity. This can include agent names, provider names, model names, token usage, streaming state, finish reasons, conversation IDs, tool names, tool descriptions, and tool schemas. By default, Sentry doesn't send LLM or tool inputs and outputs. To capture this data for debugging, set the send_default_pii option to `true`. diff --git a/docs/platforms/php/guides/laravel/integrations/laravel-ai.mdx b/docs/platforms/php/guides/laravel/integrations/laravel-ai.mdx index 526407a8d92c4c..57ce2fba87ba56 100644 --- a/docs/platforms/php/guides/laravel/integrations/laravel-ai.mdx +++ b/docs/platforms/php/guides/laravel/integrations/laravel-ai.mdx @@ -9,7 +9,7 @@ This feature is currently in Beta. Beta features are still in progress and may h -The Laravel AI integration connects Sentry with the [Laravel AI](https://laravel.com/docs/13.x/ai-sdk) package. It powers AI Agent Monitoring for Laravel applications. +The Laravel AI integration connects Sentry with the [Laravel AI](https://laravel.com/docs/13.x/ai-sdk) package. It powers Agent Tracing for Laravel applications. ## Requirements @@ -31,4 +31,4 @@ When tracing is active and `laravel/ai` is installed, Sentry automatically captu - Model and provider metadata - Conversation IDs from Laravel AI's [remembering conversations](https://laravel.com/docs/13.x/ai-sdk#remembering-conversations) feature -For setup, provider support, privacy controls, and verification, see Set Up AI Agent Monitoring. +For setup, provider support, privacy controls, and verification, see Set Up Agent Tracing. diff --git a/docs/platforms/php/guides/laravel/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/php/guides/laravel/tracing/instrumentation/automatic-instrumentation.mdx index ee1438b413728d..bef5eb3f2c6636 100644 --- a/docs/platforms/php/guides/laravel/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/php/guides/laravel/tracing/instrumentation/automatic-instrumentation.mdx @@ -19,7 +19,7 @@ Automatic instrumentation is also available with the following packages: - [Lighthouse](https://lighthouse-php.com/) GraphQL operations - [Laravel Folio](https://laravel.com/docs/11.x/folio) page based routes - [Laravel Livewire](https://livewire.laravel.com/) components -- [Laravel AI](https://laravel.com/docs/13.x/ai-sdk) agent invocations, LLM requests, tool executions, and embeddings (see AI Agent Monitoring) +- [Laravel AI](https://laravel.com/docs/13.x/ai-sdk) agent invocations, LLM requests, tool executions, and embeddings (see Agent Tracing) The Laravel SDK is also capable of creating spans for filesystem access operations. You can enable this feature by wrapping the configuration for all disks diff --git a/docs/platforms/python/integrations/anthropic/index.mdx b/docs/platforms/python/integrations/anthropic/index.mdx index ef5ef9067927c2..047d05cd6cfa56 100644 --- a/docs/platforms/python/integrations/anthropic/index.mdx +++ b/docs/platforms/python/integrations/anthropic/index.mdx @@ -5,9 +5,9 @@ description: "Learn about using Sentry for Anthropic." This integration connects Sentry with the [Anthropic Python SDK](https://github.com/anthropics/anthropic-sdk-python). -Once you've installed this SDK, you can use the Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. +Once you've installed this SDK, you can use the Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). ## Install @@ -54,7 +54,7 @@ def my_llm_stuff(): After running this script, the resulting data should show up in the `AI Spans` tab on the `Explore > Traces > Trace` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/monitoring/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/google-genai/index.mdx b/docs/platforms/python/integrations/google-genai/index.mdx index 509edefe6cf184..011a7592cad652 100644 --- a/docs/platforms/python/integrations/google-genai/index.mdx +++ b/docs/platforms/python/integrations/google-genai/index.mdx @@ -5,9 +5,9 @@ description: "Learn about using Sentry for Google Gen AI." This integration connects Sentry with the [Google Gen AI Python SDK](https://github.com/googleapis/python-genai). -Once you've installed this SDK, you can use the Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. +Once you've installed this SDK, you can use the Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). ## Install @@ -67,7 +67,7 @@ def my_llm_stuff(): After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/monitoring/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/huggingface_hub/index.mdx b/docs/platforms/python/integrations/huggingface_hub/index.mdx index 030b1b637e430e..6f34bcde59bcad 100644 --- a/docs/platforms/python/integrations/huggingface_hub/index.mdx +++ b/docs/platforms/python/integrations/huggingface_hub/index.mdx @@ -5,7 +5,7 @@ description: "Learn about using Sentry for Hugging Face Hub." This integration connects Sentry with [Hugging Face Hub](https://github.com/huggingface/huggingface_hub) in Python. -Once you've installed this SDK, you can use Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). ## Install @@ -87,7 +87,7 @@ if __name__ == "__main__": ``` -After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/ai/monitoring/agents). +After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/langchain/index.mdx b/docs/platforms/python/integrations/langchain/index.mdx index bbf3cb44af4538..13a0e2464f0a6d 100644 --- a/docs/platforms/python/integrations/langchain/index.mdx +++ b/docs/platforms/python/integrations/langchain/index.mdx @@ -5,7 +5,7 @@ description: "Learn about using Sentry for LangChain." This integration connects Sentry with [LangChain](https://github.com/langchain-ai/langchain) in Python. -Once you've installed this SDK, you can use Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). ## Install @@ -149,7 +149,7 @@ with sentry_sdk.start_transaction(name="langchain-anthropic"): print(result) ``` -After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/ai/monitoring/agents). +After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/langgraph/index.mdx b/docs/platforms/python/integrations/langgraph/index.mdx index b21156d66947f3..3051ed71293c9c 100644 --- a/docs/platforms/python/integrations/langgraph/index.mdx +++ b/docs/platforms/python/integrations/langgraph/index.mdx @@ -5,7 +5,7 @@ description: "Learn about using Sentry for LangGraph." This integration connects Sentry with [LangGraph](https://github.com/langchain-ai/langgraph) in Python. -Once you've installed this SDK, you can use Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). ## Install @@ -82,7 +82,7 @@ with sentry_sdk.start_transaction(name="langgraph-openai"): print(result) ``` -After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/ai/monitoring/agents). +After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/litellm/index.mdx b/docs/platforms/python/integrations/litellm/index.mdx index b455e07369c1c5..ee2dfec8559d25 100644 --- a/docs/platforms/python/integrations/litellm/index.mdx +++ b/docs/platforms/python/integrations/litellm/index.mdx @@ -5,9 +5,9 @@ description: "Learn about using Sentry for LiteLLM." This integration connects Sentry with the [LiteLLM Python SDK](https://github.com/BerriAI/litellm). -Once you've installed this SDK, you can use the Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. +Once you've installed this SDK, you can use the Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). ## Install @@ -71,7 +71,7 @@ print(response.choices[0].message.content) After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/monitoring/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/openai-agents/index.mdx b/docs/platforms/python/integrations/openai-agents/index.mdx index 48005a0de05eaf..89a24ddad8b47f 100644 --- a/docs/platforms/python/integrations/openai-agents/index.mdx +++ b/docs/platforms/python/integrations/openai-agents/index.mdx @@ -16,7 +16,7 @@ The integration has been confirmed to work with OpenAI Agents version 0.0.19. Once you've installed this SDK, you can use the [AI Agents Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=agents&sort=mostPopular) to understand what's going on with your AI agents. -Sentry AI Agents monitoring will automatically collect information about agents, tools, prompts, tokens, and models. +Sentry AI Agents tracing will automatically collect information about agents, tools, prompts, tokens, and models. ## Install diff --git a/docs/platforms/python/integrations/openai/index.mdx b/docs/platforms/python/integrations/openai/index.mdx index 0e4681f7ca7396..a5a3beba374db0 100644 --- a/docs/platforms/python/integrations/openai/index.mdx +++ b/docs/platforms/python/integrations/openai/index.mdx @@ -5,13 +5,13 @@ description: "Learn about using Sentry for OpenAI." This integration connects Sentry with the [OpenAI Python SDK](https://github.com/openai/openai-python). -Once you've installed this SDK, you can use Sentry AI Agents Monitoring, a Sentry dashboard that helps you understand what's going on with your AI requests. +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Monitoring will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/monitoring/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/ai/observability/agents). -AI frameworks are moving fast, and so are our integrations. To get the most out of our AI Agents Monitoring dashboard, use Python SDK version 2.41.0 or later. +AI frameworks are moving fast, and so are our integrations. To get the most out of our Agents Tracing dashboard, use Python SDK version 2.41.0 or later. @@ -63,7 +63,7 @@ def my_llm_stuff(): After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/monitoring/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/ai/observability/agents). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx index c5528fefe9daff..3f91b50d8d1052 100644 --- a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx +++ b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx @@ -4,11 +4,11 @@ sidebar_order: 500 description: "Learn how to manually instrument your code to use Sentry's Agents module." --- -With Sentry AI Agent Monitoring, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry Agent Tracing, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data will be fully connected to your other Sentry data like logs, errors, and traces. -As a prerequisite to setting up AI Agent Monitoring with Python, you'll need to first set up tracing. Once this is done, the Python SDK will automatically instrument AI agents created with supported libraries. If that doesn't fit your use case, you can use custom instrumentation described below. +As a prerequisite to setting up Agent Tracing with Python, you'll need to first set up tracing. Once this is done, the Python SDK will automatically instrument AI agents created with supported libraries. If that doesn't fit your use case, you can use custom instrumentation described below. ## Automatic Instrumentation @@ -80,7 +80,7 @@ with sentry_sdk.start_span(op="gen_ai.chat", name="chat o3-mini") as span: #### Thinking / reasoning messages -Models with extended thinking (such as Anthropic's `thinking` blocks, Gemini's `thought`, or DeepSeek's `reasoning_content`) produce internal reasoning that isn't part of the user-visible reply. Represent this content as a `reasoning` part inside the assistant message, alongside the user-facing `text` part. Sentry surfaces reasoning parts separately and filters them out of the user-facing Conversations view, so don't fold thinking into a `text` part. +Models with extended thinking (such as Anthropic's `thinking` blocks, Gemini's `thought`, or DeepSeek's `reasoning_content`) produce internal reasoning that isn't part of the user-visible reply. Represent this content as a `reasoning` part inside the assistant message, alongside the user-facing `text` part. Sentry surfaces reasoning parts separately and filters them out of the user-facing Conversations view, so don't fold thinking into a `text` part. ```python import json @@ -123,7 +123,7 @@ This span represents the execution of an AI agent, capturing the full lifecycle -For a complete guide on naming agents across all supported frameworks, see [Naming Your Agents](/ai/monitoring/agents/naming/). +For a complete guide on naming agents across all supported frameworks, see [Naming Your Agents](/ai/observability/agents/naming/). @@ -177,7 +177,7 @@ with sentry_sdk.start_span(op="gen_ai.execute_tool", name="execute_tool get_weat Tracking Conversations has **beta** stability. Configuration options and behavior may change. -For AI applications that involve multi-turn conversations, you can use `sentry_sdk.ai.set_conversation_id()` to associate all AI spans from the same conversation. This enables you to track and analyze complete conversation flows within Sentry. +For AI applications that involve multi-turn conversations, you can use `sentry_sdk.ai.set_conversation_id()` to associate all AI spans from the same conversation. This enables you to track and analyze complete conversation flows within Sentry. The conversation ID is set as the `gen_ai.conversation.id` attribute on all AI-related spans in the current scope. To remove the conversation ID, use the `remove_conversation_id()` method on the `Scope`. @@ -208,7 +208,7 @@ response = openai.responses.create( ## Identifying Users in Conversations -The [Conversations](/ai/monitoring/conversations/) view includes a **User** column. To populate it, call `sentry_sdk.set_user` once per request or session, before any AI calls: +The [Conversations](/ai/observability/conversations/) view includes a **User** column. To populate it, call `sentry_sdk.set_user` once per request or session, before any AI calls: ```python import sentry_sdk diff --git a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/mcp-module.mdx b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/mcp-module.mdx index 74b8af8cac9412..35ba0c533dc7b6 100644 --- a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/mcp-module.mdx +++ b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/mcp-module.mdx @@ -4,7 +4,7 @@ sidebar_order: 600 description: "Learn how to manually instrument your code to use Sentry's MCP monitoring." --- -With Sentry's [MCP monitoring](/ai/monitoring/mcp/), you can track and debug MCP servers with full-stack context. You'll be able to monitor tool executions, prompt retrievals, resource access, and error rates. MCP monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry's [MCP monitoring](/ai/observability/mcp/), you can track and debug MCP servers with full-stack context. You'll be able to monitor tool executions, prompt retrievals, resource access, and error rates. MCP monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. As a prerequisite to setting up MCP monitoring with Python, you'll need to first set up tracing. Once this is done, the Python SDK will automatically instrument MCP servers created with supported libraries. If that doesn't fit your use case, you can use custom instrumentation described below. @@ -12,7 +12,7 @@ As a prerequisite to setting up MCP monitoring with Python, you'll need to first The Python SDK supports automatic instrumentation for MCP servers. We recommend adding the MCP integration to your Sentry configuration to automatically capture spans for MCP operations. -- [MCP (Model Context Protocol)](/ai/monitoring/mcp/getting-started/) +- [MCP (Model Context Protocol)](/ai/observability/mcp/getting-started/) ## Manual Instrumentation diff --git a/docs/platforms/react-native/common/agent-tracing/index.mdx b/docs/platforms/react-native/common/agent-tracing/index.mdx new file mode 100644 index 00000000000000..3973e4fc063a20 --- /dev/null +++ b/docs/platforms/react-native/common/agent-tracing/index.mdx @@ -0,0 +1,21 @@ +--- +title: Agent Tracing +sidebar_order: 7 +description: "Learn how to manually instrument AI agents in React Native applications." +sidebar_section: features +new: true +--- + +With Sentry Agent Tracing, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data will be fully connected to your other Sentry data like logs, errors, and traces. + +## Prerequisites + +Before setting up Agent Tracing, ensure you have tracing enabled in your Sentry configuration. + + + +**React Native applications require manual instrumentation.** The automatic (OpenTelemetry-based) AI integrations shipped with `@sentry/node` rely on Node.js require-hooks that aren't available on Hermes or JavaScriptCore, so they can't be used from React Native. Use the manual client wrappers described below instead. + + + + diff --git a/docs/platforms/react-native/common/ai-agent-monitoring/index.mdx b/docs/platforms/react-native/common/ai-agent-monitoring/index.mdx deleted file mode 100644 index d3542a5952d901..00000000000000 --- a/docs/platforms/react-native/common/ai-agent-monitoring/index.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: AI Agent Monitoring -sidebar_order: 7 -description: "Learn how to manually instrument AI agents in React Native applications." -sidebar_section: features -new: true ---- - -With Sentry AI Agent Monitoring, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. - -## Prerequisites - -Before setting up AI Agent Monitoring, ensure you have tracing enabled in your Sentry configuration. - - - -**React Native applications require manual instrumentation.** The automatic (OpenTelemetry-based) AI integrations shipped with `@sentry/node` rely on Node.js require-hooks that aren't available on Hermes or JavaScriptCore, so they can't be used from React Native. Use the manual client wrappers described below instead. - - - - diff --git a/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx b/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx index 0e851c9c73a8b7..33f321a43b724d 100644 --- a/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx +++ b/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/ai-agents-module.mdx @@ -4,9 +4,9 @@ sidebar_order: 500 description: "Learn how to manually instrument your code to use Sentry's Agents module." --- -With Sentry AI Agent Monitoring, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. AI Agent Monitoring data will be fully connected to your other Sentry data like logs, errors, and traces. +With Sentry Agent Tracing, you can monitor and debug your AI systems with full-stack context. You'll be able to track key insights like token usage, latency, tool usage, and error rates. Agent Tracing data will be fully connected to your other Sentry data like logs, errors, and traces. -As a prerequisite to setting up AI Agent Monitoring with Ruby, you'll need to first set up tracing. Once this is done, you can use the custom instrumentation described below to capture AI agent spans. +As a prerequisite to setting up Agent Tracing with Ruby, you'll need to first set up tracing. Once this is done, you can use the custom instrumentation described below to capture AI agent spans. ## Manual Instrumentation diff --git a/docs/product/dashboards/sentry-dashboards/ai/agents.mdx b/docs/product/dashboards/sentry-dashboards/ai/agents.mdx index b6df5d17403e69..3509d9b0ae3097 100644 --- a/docs/product/dashboards/sentry-dashboards/ai/agents.mdx +++ b/docs/product/dashboards/sentry-dashboards/ai/agents.mdx @@ -12,7 +12,7 @@ keywords: og_image: /og-images/ai-monitoring-agents-dashboard.png --- -AI Agents Dashboards, found in [Sentry Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=agents&sort=mostPopular) provide a comprehensive view of your AI workflows, including executions, model costs and token usage, tool calls, and recent errors. Once you've [configured the Sentry SDK](/ai/monitoring/agents/getting-started/) for your AI agent project, telemetry data is collected and displayed in the dashboard to support analysis of system behavior and performance. +AI Agents Dashboards, found in [Sentry Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=agents&sort=mostPopular) provide a comprehensive view of your AI workflows, including executions, model costs and token usage, tool calls, and recent errors. Once you've [configured the Sentry SDK](/ai/observability/agents/getting-started/) for your AI agent project, telemetry data is collected and displayed in the dashboard to support analysis of system behavior and performance. AI Agent monitoring have three dashboards: diff --git a/docs/product/dashboards/sentry-dashboards/ai/index.mdx b/docs/product/dashboards/sentry-dashboards/ai/index.mdx index f06f68f82ab8b5..032dfc3edec99b 100644 --- a/docs/product/dashboards/sentry-dashboards/ai/index.mdx +++ b/docs/product/dashboards/sentry-dashboards/ai/index.mdx @@ -6,7 +6,7 @@ description: "Use Sentry Dashboards to monitor AI agents and MCP performance." Sentry Dashboards include dedicated views for AI monitoring. Use them to track agent executions, token usage, tool calls, and MCP (Model Context Protocol) traffic. -- **[AI Agents Dashboards](/product/dashboards/sentry-dashboards/ai/agents/)** — View AI agent workflows, model costs, token usage, and tool calls. See [Set up AI Agent Monitoring](/ai/monitoring/agents/getting-started/) to get started. -- **[MCP Dashboards](/product/dashboards/sentry-dashboards/ai/mcp/)** — Monitor MCP server usage and performance. See [Set up MCP](/ai/monitoring/mcp/getting-started/) to get started. +- **[AI Agents Dashboards](/product/dashboards/sentry-dashboards/ai/agents/)** — View AI agent workflows, model costs, token usage, and tool calls. See [Set up Agent Tracing](/ai/observability/agents/getting-started/) to get started. +- **[MCP Dashboards](/product/dashboards/sentry-dashboards/ai/mcp/)** — Monitor MCP server usage and performance. See [Set up MCP](/ai/observability/mcp/getting-started/) to get started. -For data privacy and security, see [AI Agents Data Privacy](/ai/monitoring/agents/privacy/). +For data privacy and security, see [AI Agents Data Privacy](/ai/observability/agents/privacy/). diff --git a/docs/product/dashboards/sentry-dashboards/ai/mcp.mdx b/docs/product/dashboards/sentry-dashboards/ai/mcp.mdx index 886d5a20bb26fb..ea511697de87b1 100644 --- a/docs/product/dashboards/sentry-dashboards/ai/mcp.mdx +++ b/docs/product/dashboards/sentry-dashboards/ai/mcp.mdx @@ -11,7 +11,7 @@ keywords: og_image: /og-images/ai-monitoring-mcp-dashboard.png --- -MCP Dashboards, found in [Sentry Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=mcp&sort=mostPopular), provide a comprehensive view of your MCP server activities, including requests, tool executions, resource access, and prompt usage. Once you've [configured the Sentry SDK](/ai/monitoring/mcp/getting-started/) for your MCP project, telemetry data is collected and displayed in the dashboard to support analysis of system behavior and performance. +MCP Dashboards, found in [Sentry Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/?filter=onlyPrebuilt&query=mcp&sort=mostPopular), provide a comprehensive view of your MCP server activities, including requests, tool executions, resource access, and prompt usage. Once you've [configured the Sentry SDK](/ai/observability/mcp/getting-started/) for your MCP project, telemetry data is collected and displayed in the dashboard to support analysis of system behavior and performance. MCP monitoring has four dashboards: diff --git a/docs/product/index.mdx b/docs/product/index.mdx index 6e3e56bb816a18..8519fb52cd3229 100644 --- a/docs/product/index.mdx +++ b/docs/product/index.mdx @@ -59,8 +59,8 @@ See the moment a release starts to degrade. Track crash-free sessions, version a ### [AI in Sentry (Seer)](/product/ai-in-sentry/) [Seer](/product/ai-in-sentry/seer/) turns your telemetry into answers. It explains why your code failed (not just where), generates merge-ready fixes with [Autofix](/product/ai-in-sentry/seer/autofix/), and catches regressions before they merge with [AI Code Review](/product/ai-in-sentry/seer/code-review/). -### [AI Agents Monitoring](/ai/monitoring/agents/) -If you're building AI-powered features, Sentry traces LLM calls, agent tool executions, and token usage alongside the rest of your application telemetry. [Learn more →](/ai/monitoring/) +### [Agents Tracing](/ai/observability/agents/) +If you're building AI-powered features, Sentry traces LLM calls, agent tool executions, and token usage alongside the rest of your application telemetry. [Learn more →](/ai/observability/) ### [Monitors and Alerts](/product/monitors-and-alerts/) Define what matters — then get notified when it breaks. Set up [cron monitors](/product/monitors-and-alerts/monitors/crons/) for scheduled jobs, [uptime monitoring](/product/monitors-and-alerts/monitors/uptime-monitoring/) for endpoints, and [alerts](/product/monitors-and-alerts/alerts/) that route to Slack, PagerDuty, or your issue tracker. @@ -70,7 +70,7 @@ Define what matters — then get notified when it breaks. Set up [cron monitors] ### [Build Distribution](/product/build-distribution/) Securely distribute app builds to your internal teams and beta testers. Upload builds from CI to streamline your distribution workflow, manage access control, and track installation analytics. -### [AI Monitoring](/ai/monitoring/) +### [AI Observability](/ai/observability/) Whether you're building AI agents or MCP servers, Sentry automatically captures performance metrics, errors, and traces across your entire AI pipeline. ## Getting Started diff --git a/docs/product/sentry-basics/performance-monitoring.mdx b/docs/product/sentry-basics/performance-monitoring.mdx index 21fab29d8469aa..426775ead3eb4a 100644 --- a/docs/product/sentry-basics/performance-monitoring.mdx +++ b/docs/product/sentry-basics/performance-monitoring.mdx @@ -21,7 +21,7 @@ After turning on tracing, you'll automatically see [Sentry Dashboards](/product/ - [**Frontend**](/product/dashboards/sentry-dashboards/frontend/) — Core Web Vitals, transaction duration, error rates - [**Backend**](/product/dashboards/sentry-dashboards/backend/) — database queries, API calls, caches, queues, crons - [**Mobile**](/product/dashboards/sentry-dashboards/mobile/) — cold/warm app starts, TTID & TTFD, screen load times -- [**AI**](/ai/monitoring/agents/) — LLM call latency, token usage, tool execution performance +- [**AI**](/ai/observability/agents/) — LLM call latency, token usage, tool execution performance
diff --git a/includes/ai-agent-monitoring/manual-instrumentation.mdx b/includes/agent-tracing/manual-instrumentation.mdx similarity index 100% rename from includes/ai-agent-monitoring/manual-instrumentation.mdx rename to includes/agent-tracing/manual-instrumentation.mdx diff --git a/includes/ai-dashboards/detailed-trace-view.mdx b/includes/ai-dashboards/detailed-trace-view.mdx index 6c61c26e9ce8dd..e62f92d8ee95cd 100644 --- a/includes/ai-dashboards/detailed-trace-view.mdx +++ b/includes/ai-dashboards/detailed-trace-view.mdx @@ -1,6 +1,6 @@ The full trace view shows the complete agent workflow with full context: -![AI Agents Monitoring Detailed Trace View =900x](./img/agent-detailed-trace-view.png) +![Agents Tracing Detailed Trace View =900x](./img/agent-detailed-trace-view.png) This detailed view reveals: diff --git a/includes/ai-dashboards/models.mdx b/includes/ai-dashboards/models.mdx index 840335f56bae6f..32eb2fabfb49ba 100644 --- a/includes/ai-dashboards/models.mdx +++ b/includes/ai-dashboards/models.mdx @@ -1,5 +1,5 @@ The Models dashboard displays Model Cost, Tokens Used, and Token Types widgets, as well as all used models with durations and token usage: -![AI Agents Monitoring Models =900x](./img/agent-models-dash.png) +![Agents Tracing Models =900x](./img/agent-models-dash.png) -The Model Cost widget shows estimated costs based on token usage and model pricing. For details on how costs are calculated, where pricing data comes from, and what's not covered, see [Model Costs](/ai/monitoring/agents/costs/). +The Model Cost widget shows estimated costs based on token usage and model pricing. For details on how costs are calculated, where pricing data comes from, and what's not covered, see [Model Costs](/ai/observability/agents/costs/). diff --git a/includes/ai-dashboards/overview.mdx b/includes/ai-dashboards/overview.mdx index 887d0b449676a0..08f95606dd758c 100644 --- a/includes/ai-dashboards/overview.mdx +++ b/includes/ai-dashboards/overview.mdx @@ -1,6 +1,6 @@ The Overview dashboard provides a high-level view of your AI agent activity: -![AI Agents Monitoring Overview =900x](./img/agent-overview-dash.png) +![Agents Tracing Overview =900x](./img/agent-overview-dash.png) The dashboard displays the following key widgets: @@ -11,7 +11,7 @@ The dashboard displays the following key widgets: - **Tokens Used**: Token usage by top models - **Tool Calls**: Tool call volume and trends -Agents are grouped by name. If your agents show up as unnamed, see [Naming Your Agents](/ai/monitoring/agents/naming/). +Agents are grouped by name. If your agents show up as unnamed, see [Naming Your Agents](/ai/observability/agents/naming/). Click into any model listed under widgets to get to the Models dashboard. Click into any tool listed under widgets to get to the Tools dashboard. diff --git a/includes/ai-dashboards/tools.mdx b/includes/ai-dashboards/tools.mdx index 22ee2d5036458d..2447f0224957cb 100644 --- a/includes/ai-dashboards/tools.mdx +++ b/includes/ai-dashboards/tools.mdx @@ -1,3 +1,3 @@ The Tools dashboard displays Tool Calls and Tool Errors widgets, as well as all used tools with durations and errors: -![AI Agents Monitoring Tools =900x](./img/agent-tools-dash.png) +![Agents Tracing Tools =900x](./img/agent-tools-dash.png) diff --git a/includes/docs-changelog.mdx b/includes/docs-changelog.mdx index 979ac06504c18f..ee67a3a0ad5669 100644 --- a/includes/docs-changelog.mdx +++ b/includes/docs-changelog.mdx @@ -20,20 +20,20 @@ ### [docs(ai): Update AI dashboards with shared includes and new AI Spans view](https://github.com/getsentry/sentry-docs/pull/17183) **Added:** -- [AI Agents Dashboards](/ai/monitoring/agents/dashboards/) +- [AI Agents Dashboards](/ai/observability/agents/dashboards/) **Modified:** -- [Model Costs](/ai/monitoring/agents/costs/) -- [AI Agents](/ai/monitoring/agents/) +- [Model Costs](/ai/observability/agents/costs/) +- [AI Agents](/ai/observability/agents/) - [Instrument AI Agents](/platforms/dotnet/tracing/instrumentation/ai-agents-module/) -- [Browser AI Monitoring](/platforms/javascript/ai-agent-monitoring-browser/) -- [Set Up AI Agent Monitoring](/platforms/javascript/guides/node/ai-agent-monitoring/) +- [Browser AI Tracing](/platforms/javascript/agent-tracing-browser/) +- [Set Up Agent Tracing](/platforms/javascript/guides/node/agent-tracing/) - [Instrument AI Agents](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module/) - [Instrument AI Agents](/platforms/ruby/tracing/instrumentation/custom-instrumentation/ai-agents-module/) - [AI Agents Dashboards](/product/dashboards/sentry-dashboards/ai/agents/) **Removed:** -- [/ai/monitoring/agents/dashboard/](/ai/monitoring/agents/dashboards/) +- [/ai/observability/agents/dashboard/](/ai/observability/agents/dashboards/) --- @@ -75,12 +75,12 @@ ### [docs(ai): Add naming your agents page](https://github.com/getsentry/sentry-docs/pull/17133) **Added:** -- [Naming Your Agents](/ai/monitoring/agents/naming/) +- [Naming Your Agents](/ai/observability/agents/naming/) **Modified:** -- [Set Up](/ai/monitoring/agents/getting-started/) -- [AI Agents](/ai/monitoring/agents/) -- [Set Up AI Agent Monitoring](/platforms/javascript/guides/node/ai-agent-monitoring/) +- [Set Up](/ai/observability/agents/getting-started/) +- [AI Agents](/ai/observability/agents/) +- [Set Up Agent Tracing](/platforms/javascript/guides/node/agent-tracing/) - [Instrument AI Agents](/platforms/python/tracing/instrumentation/custom-instrumentation/ai-agents-module/) --- diff --git a/includes/tracing/ai-agents-module/token-cost-gotchas.mdx b/includes/tracing/ai-agents-module/token-cost-gotchas.mdx index ed01a410b9dfc3..5cdb151bee85ce 100644 --- a/includes/tracing/ai-agents-module/token-cost-gotchas.mdx +++ b/includes/tracing/ai-agents-module/token-cost-gotchas.mdx @@ -1,6 +1,6 @@ ## Token Usage and Cost Gotchas -When manually setting token attributes, be aware of how Sentry uses them to [calculate model costs](/ai/monitoring/agents/costs/). +When manually setting token attributes, be aware of how Sentry uses them to [calculate model costs](/ai/observability/agents/costs/). **Cached and reasoning tokens are subsets, not separate counts.** `gen_ai.usage.input_tokens` is the **total** input token count that already includes any cached tokens. Similarly, `gen_ai.usage.output_tokens` already includes reasoning tokens. Sentry subtracts the cached/reasoning counts from the totals to compute the "raw" portion, so reporting them incorrectly can produce wrong or negative costs. diff --git a/middleware.ts b/middleware.ts index fc00a973fb14f8..6e0369c6426a22 100644 --- a/middleware.ts +++ b/middleware.ts @@ -3384,59 +3384,112 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ }, { from: '/product/ai-monitoring/', - to: '/ai/monitoring/agents/', + to: '/ai/observability/agents/', }, { from: '/product/insights/llm-monitoring/', - to: '/ai/monitoring/agents/', + to: '/ai/observability/agents/', }, { from: '/product/insights/llm-monitoring/getting-started/', - to: '/ai/monitoring/agents/getting-started/', + to: '/ai/observability/agents/getting-started/', }, { from: '/product/insights/llm-monitoring/getting-started/the-dashboard/', - to: '/ai/monitoring/agents/dashboards/', + to: '/ai/observability/agents/dashboards/', }, { from: '/product/insights/ai/', - to: '/ai/monitoring/', + to: '/ai/observability/', }, { from: '/product/insights/ai/agents/', - to: '/ai/monitoring/agents/', + to: '/ai/observability/agents/', }, { from: '/product/insights/ai/agents/privacy/', - to: '/ai/monitoring/agents/privacy/', + to: '/ai/observability/agents/privacy/', }, { from: '/product/insights/ai/agents/dashboard/', - to: '/ai/monitoring/agents/dashboards/', + to: '/ai/observability/agents/dashboards/', }, { - from: '/ai/monitoring/agents/dashboard/', - to: '/ai/monitoring/agents/dashboards/', + from: '/ai/observability/agents/dashboard/', + to: '/ai/observability/agents/dashboards/', }, { from: '/product/insights/ai/agents/costs/', - to: '/ai/monitoring/agents/costs/', + to: '/ai/observability/agents/costs/', }, { from: '/product/insights/ai/agents/getting-started/', - to: '/ai/monitoring/agents/getting-started/', + to: '/ai/observability/agents/getting-started/', }, { from: '/product/insights/ai/mcp/', - to: '/ai/monitoring/mcp/', + to: '/ai/observability/mcp/', }, { from: '/product/insights/ai/mcp/getting-started/', - to: '/ai/monitoring/mcp/getting-started/', + to: '/ai/observability/mcp/getting-started/', }, { from: '/product/insights/ai/mcp/dashboard/', - to: '/ai/monitoring/mcp/dashboard/', + to: '/ai/observability/mcp/dashboard/', + }, + // AI Monitoring → AI Observability rename redirects + { + from: '/ai/monitoring/', + to: '/ai/observability/', + }, + { + from: '/ai/monitoring/agents/', + to: '/ai/observability/agents/', + }, + { + from: '/ai/monitoring/agents/getting-started/', + to: '/ai/observability/agents/getting-started/', + }, + { + from: '/ai/monitoring/agents/dashboards/', + to: '/ai/observability/agents/dashboards/', + }, + { + from: '/ai/monitoring/agents/dashboard/', + to: '/ai/observability/agents/dashboards/', + }, + { + from: '/ai/monitoring/agents/naming/', + to: '/ai/observability/agents/naming/', + }, + { + from: '/ai/monitoring/agents/privacy/', + to: '/ai/observability/agents/privacy/', + }, + { + from: '/ai/monitoring/agents/costs/', + to: '/ai/observability/agents/costs/', + }, + { + from: '/ai/monitoring/agents/sampling/', + to: '/ai/observability/agents/sampling/', + }, + { + from: '/ai/monitoring/conversations/', + to: '/ai/observability/conversations/', + }, + { + from: '/ai/monitoring/mcp/', + to: '/ai/observability/mcp/', + }, + { + from: '/ai/monitoring/mcp/getting-started/', + to: '/ai/observability/mcp/getting-started/', + }, + { + from: '/ai/monitoring/mcp/dashboard/', + to: '/ai/observability/mcp/dashboard/', }, { from: '/product/sentry-mcp/', diff --git a/platform-includes/getting-started-node/javascript.mdx b/platform-includes/getting-started-node/javascript.mdx index 95d2aad1f817d6..3be10e71b7ee1e 100644 --- a/platform-includes/getting-started-node/javascript.mdx +++ b/platform-includes/getting-started-node/javascript.mdx @@ -52,7 +52,7 @@ To import and initialize Sentry, create a file named `instrument.(js|mjs)` in th -Import `instrument.js` before any other modules to ensure Sentry initializes early. If you initialize later, auto-instrumentation and modules like database monitoring, agent monitoring, tracing may not work. +Import `instrument.js` before any other modules to ensure Sentry initializes early. If you initialize later, auto-instrumentation and modules like database monitoring, agent tracing, tracing may not work. diff --git a/redirects.js b/redirects.js index 9b335fdf18adaf..5b385a1fa696f8 100644 --- a/redirects.js +++ b/redirects.js @@ -1881,14 +1881,14 @@ const userDocsRedirects = [ source: '/ai/sentry-cli/', destination: 'https://cli.sentry.dev', }, - // Redirects for Insights → Sentry Dashboards migration + // Redirects for Insights → Sentry Dashboards migration { source: '/product/insights/llm-monitoring/:path*', - destination: '/ai/monitoring/:path*', + destination: '/ai/observability/:path*', }, { source: '/product/insights/agents/:path*', - destination: '/ai/monitoring/agents/:path*', + destination: '/ai/observability/agents/:path*', }, { source: '/product/insights/retention-priorities/', @@ -1896,11 +1896,11 @@ const userDocsRedirects = [ }, { source: '/product/insights/mcp/', - destination: '/ai/monitoring/mcp/', + destination: '/ai/observability/mcp/', }, { source: '/product/insights/ai/:path*', - destination: '/ai/monitoring/:path*', + destination: '/ai/observability/:path*', }, { source: '/product/insights/requests/', @@ -1959,30 +1959,129 @@ const userDocsRedirects = [ source: '/product/insights/:path*', destination: '/product/dashboards/sentry-dashboards/', }, - // AI Agent Monitoring moved to top-level feature + // Agent Tracing moved to top-level feature { source: '/platforms/javascript/tracing/instrumentation/ai-agents-module/:path*', - destination: '/platforms/javascript/ai-agent-monitoring/:path*', + destination: '/platforms/javascript/agent-tracing/:path*', }, { source: '/platforms/javascript/guides/:guide/tracing/instrumentation/ai-agents-module/:path*', - destination: '/platforms/javascript/guides/:guide/ai-agent-monitoring/:path*', + destination: '/platforms/javascript/guides/:guide/agent-tracing/:path*', }, { source: '/platforms/javascript/tracing/instrumentation/ai-agents-module-browser/:path*', - destination: '/platforms/javascript/ai-agent-monitoring-browser/:path*', + destination: '/platforms/javascript/agent-tracing-browser/:path*', }, { source: '/platforms/javascript/guides/:guide/tracing/instrumentation/ai-agents-module-browser/:path*', - destination: '/platforms/javascript/guides/:guide/ai-agent-monitoring-browser/', + destination: '/platforms/javascript/guides/:guide/agent-tracing-browser/', }, - // Browser JS doesn't have server-side AI Agent Monitoring, redirect to browser version + // Browser JS doesn't have server-side Agent Tracing, redirect to browser version + { + source: '/platforms/javascript/agent-tracing/', + destination: '/platforms/javascript/agent-tracing-browser/', + }, + // AI Monitoring → AI Observability rename redirects + { + source: '/ai/monitoring/:path*', + destination: '/ai/observability/:path*', + }, + { + source: '/ai/monitoring/', + destination: '/ai/observability/', + }, + // AI Agent Monitoring / ai-agent-tracing → Agent Tracing rename redirects { source: '/platforms/javascript/ai-agent-monitoring/', - destination: '/platforms/javascript/ai-agent-monitoring-browser/', + destination: '/platforms/javascript/agent-tracing-browser/', + }, + { + source: '/platforms/javascript/ai-agent-monitoring/:path*', + destination: '/platforms/javascript/agent-tracing/:path*', + }, + { + source: '/platforms/javascript/ai-agent-monitoring-browser/', + destination: '/platforms/javascript/agent-tracing-browser/', + }, + { + source: '/platforms/javascript/ai-agent-monitoring-browser/:path*', + destination: '/platforms/javascript/agent-tracing-browser/:path*', + }, + { + source: '/platforms/javascript/guides/:guide/ai-agent-monitoring/', + destination: '/platforms/javascript/guides/:guide/agent-tracing/', + }, + { + source: '/platforms/javascript/guides/:guide/ai-agent-monitoring/:path*', + destination: '/platforms/javascript/guides/:guide/agent-tracing/:path*', + }, + { + source: '/platforms/javascript/guides/:guide/ai-agent-monitoring-browser/', + destination: '/platforms/javascript/guides/:guide/agent-tracing-browser/', + }, + { + source: '/platforms/react-native/ai-agent-monitoring/', + destination: '/platforms/react-native/agent-tracing/', + }, + { + source: '/platforms/react-native/ai-agent-monitoring/:path*', + destination: '/platforms/react-native/agent-tracing/:path*', + }, + { + source: '/platforms/php/guides/laravel/ai-monitoring/', + destination: '/platforms/php/guides/laravel/agent-tracing/', + }, + { + source: '/platforms/php/guides/laravel/ai-monitoring/:path*', + destination: '/platforms/php/guides/laravel/agent-tracing/:path*', + }, + // ai-agent-tracing → agent-tracing rename redirects + { + source: '/platforms/javascript/ai-agent-tracing/', + destination: '/platforms/javascript/agent-tracing-browser/', + }, + { + source: '/platforms/javascript/ai-agent-tracing/:path*', + destination: '/platforms/javascript/agent-tracing/:path*', + }, + { + source: '/platforms/javascript/ai-agent-tracing-browser/', + destination: '/platforms/javascript/agent-tracing-browser/', + }, + { + source: '/platforms/javascript/ai-agent-tracing-browser/:path*', + destination: '/platforms/javascript/agent-tracing-browser/:path*', + }, + { + source: '/platforms/javascript/guides/:guide/ai-agent-tracing/', + destination: '/platforms/javascript/guides/:guide/agent-tracing/', + }, + { + source: '/platforms/javascript/guides/:guide/ai-agent-tracing/:path*', + destination: '/platforms/javascript/guides/:guide/agent-tracing/:path*', + }, + { + source: '/platforms/javascript/guides/:guide/ai-agent-tracing-browser/', + destination: '/platforms/javascript/guides/:guide/agent-tracing-browser/', + }, + { + source: '/platforms/react-native/ai-agent-tracing/', + destination: '/platforms/react-native/agent-tracing/', + }, + { + source: '/platforms/react-native/ai-agent-tracing/:path*', + destination: '/platforms/react-native/agent-tracing/:path*', + }, + { + source: '/platforms/php/guides/laravel/ai-agent-tracing/', + destination: '/platforms/php/guides/laravel/agent-tracing/', + }, + { + source: '/platforms/php/guides/laravel/ai-agent-tracing/:path*', + destination: '/platforms/php/guides/laravel/agent-tracing/:path*', }, { source: '/product/dashboards/sentry-dashboards/performance-metrics/', diff --git a/src/components/home.tsx b/src/components/home.tsx index 751fac6cc42ba3..d6378f9ff86223 100644 --- a/src/components/home.tsx +++ b/src/components/home.tsx @@ -364,8 +364,8 @@ export async function Home() { MCP server {' '} with your agents. Debug agents and MCP servers by{' '} - - monitoring your AI features + + observing your AI features .

diff --git a/src/components/sidebar/index.tsx b/src/components/sidebar/index.tsx index b2a5e003694585..b5710881f94233 100644 --- a/src/components/sidebar/index.tsx +++ b/src/components/sidebar/index.tsx @@ -21,8 +21,8 @@ import {SidebarProps} from './types'; // Pages that have different paths on different platforms but are conceptually equivalent const EQUIVALENT_PATHS: Record = { - 'ai-agent-monitoring': 'ai-agent-monitoring-browser', - 'ai-agent-monitoring-browser': 'ai-agent-monitoring', + 'agent-tracing': 'agent-tracing-browser', + 'agent-tracing-browser': 'agent-tracing', }; export const sidebarToggleId = styles['navbar-menu-toggle']; @@ -66,7 +66,7 @@ export async function Sidebar({path, versions}: SidebarProps) { const platformPageForCurrentPath = nodeForPath(rootNode, ['platforms', platform.name, ...currentPathParts]) || - // try equivalent path (e.g., ai-agent-monitoring <-> ai-agent-monitoring-browser) + // try equivalent path (e.g., agent-tracing <-> agent-tracing-browser) (equivalentPath && nodeForPath(rootNode, [ 'platforms', @@ -96,7 +96,7 @@ export async function Sidebar({path, versions}: SidebarProps) { guide.name, ...currentPathParts, ]) || - // try equivalent path (e.g., ai-agent-monitoring <-> ai-agent-monitoring-browser) + // try equivalent path (e.g., agent-tracing <-> agent-tracing-browser) (equivalentPath && nodeForPath(rootNode, [ 'platforms',