From 45fc847dbbfa3089935cf64e569a7f6d8e64b8c3 Mon Sep 17 00:00:00 2001 From: Braelyn Boynton Date: Wed, 7 Aug 2024 13:19:35 -0700 Subject: [PATCH] decorator page name fix (#337) --- docs/v1/concepts/decorators.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/v1/concepts/decorators.mdx b/docs/v1/concepts/decorators.mdx index 8722dcd1..49425e7a 100644 --- a/docs/v1/concepts/decorators.mdx +++ b/docs/v1/concepts/decorators.mdx @@ -16,11 +16,17 @@ If your implementation uses Classes to denote Agents, this decorator enables aut Learn more about tracking agents [here](/v1/usage/tracking-agents). -## `@track_function()` +## `@record_action()` Sometimes your agent system will use functions that are important to track as [`Actions`](/v1/concepts/events/#actionevent). Adding this decorator above any function will allow every instance of that function call to be tracked and displayed in your [Session](v1/concepts/sessions) Drill-Down on the dashboard. +## `@record_tool()` +Some functions are used as Tools. If you're not using an agent framework that records [`ToolEvents`](/v1/concepts/events/#toolevent) with AgentOps automatically, this decorator will record `ToolEvents` when the function is called. + +Adding this decorator above any function will allow every instance of that function call to be tracked and displayed +in your [Session](v1/concepts/sessions) Drill-Down on the dashboard. + \ No newline at end of file