Workflow Annotations
Enrich your traces by annotating chains and workflows in your app
Traceloop SDK supports several ways to annotate workflows, tasks, agents and tools in your code to get a more complete picture of your app structure.
If you’re using a framework like Langchain, Haystack or LlamaIndex - no need to do anything! OpenLLMetry will automatically detect the framework and annotate your traces.
Workflows and Tasks
Sometimes called a “chain”, intended for a multi-step process that can be traced as a single unit.
Use it as @workflow(name="my_workflow")
or @task(name="my_task")
.
The name
argument is optional. If you don’t provide it, we will use the
function name as the workflow or task name.
You can version your workflows and tasks. Just provide the version
argument
to the decorator: @workflow(name="my_workflow", version=2)
Agents and Tools
Similarily, if you use autonomous agents, you can use the @agent
decorator to trace them as a single unit.
Each tool should be marked with @tool
.
Async methods
In Typescript, you can use the same syntax for async methods.
In Python, you’ll need to switch to an equivalent async decorator.
So, if you’re decorating an async
method, use @aworkflow
, @atask
and so forth.
See also a separate section on using threads in Python with OpenLLMetry.
Decorating Classes (Python only)
While the examples above shows how to decorate functions, you can also decorate classes. In this case, you will also need to provide the name of the method that runs the workflow, task, agent or tool.
Was this page helpful?