A run can represent either a trace (root run) or a child run (~span).
class RunTreeAttachments for the example
The LangSmith client to use.
The dotted order for the run.
This is a string composed of {time}{run-uuid}.* so that a trace can be sorted in the order it was executed.
Example:
The epoch time at which the run ended, if applicable.
Error message, captured if the run faces any issues.
Events like 'start', 'end' linked to the run.
Additional RunTree configuration to pass through.
Optionally, a unique identifier for the run.
Inputs that were used to initiate the run.
Custom name for the root span. If not provided, defaults to the model display name or "generateText"/"streamText".
Outputs produced by the run, if any.
ID of a parent run, if this run is part of a larger operation.
ID of an example that might be related to this run.
Projects to replicate this run to with optional updates.
Specifies the type of run (tool, chain, llm, etc.).
Serialized state of the run for potential future use.
The epoch time at which the run started, if available.
Unique ID assigned to every run within this nested trace. *
Whether to enable tracing.
Additional metadata associated with the example.
Add an event to the run tree.