The Open Framework for Building Agents
docs: clarify Agent Runs setup (#3792)
Chad Hietalac2afd743da05
diff --git a/docs/guides/instrumentation/agent-runs.mdx b/docs/guides/instrumentation/agent-runs.mdxindex c4fe50c62..5f80d1563 100644--- a/docs/guides/instrumentation/agent-runs.mdx+++ b/docs/guides/instrumentation/agent-runs.mdx@@ -19,13 +19,6 @@ Agent Runs usage is billed at[Always-on Tracing rates](https://vercel.com/docs/tracing/always-on-tracing#usage-and-pricing)during beta. All plans include 30-day Agent Runs retention during beta.-## Configure Agent Runs--Preview and production deployments export to Vercel Agent Runs by default.-Omitting `agent/instrumentation/agent-runs.ts` preserves that default. Export-`agentRuns(...)` from that file to reconfigure it, or export-`disableInstrumentation()` to disable it.-## Enable tracing on VercelWhen `eve deploy` creates a new Vercel project, it configures 100% trace@@ -47,6 +40,13 @@ Tracing starts as soon as you save the rule. You can also manage samplingrules with [`vercel traces config`](https://vercel.com/docs/cli/traces#manage-trace-sampling-rules).The CLI accepts rates from 1 to 100%; add a 0% rule from the dashboard.+## Configure Agent Runs++Preview and production deployments export to Vercel Agent Runs by default.+Omit `agent/instrumentation/agent-runs.ts` to keep that default. To change it,+default-export `agentRuns(...)` from that file, or default-export+`disableInstrumentation()` to turn off Agent Runs export.+## Filter Agent Runs exports`agentRuns()` accepts one `exportPolicy` object or an array applied in order.