Explorer¶
After an application is successfully created, the system collects each LLM request (from input prompt to output generation) as a log event in the LLM Explorer. You can search, filter, and analyze Trace or Span data for a single application or all applications using powerful log query methods.
| Description | |
|---|---|
| Span | Represents a single operation in an LLM application. Each call to a model, each vector database query, or each API request is an independent Span. It records detailed information about the operation, such as start time, duration, status (success/failure), model used, token consumption, etc. |
| Trace | A Trace records the complete end-to-end path of an external request (e.g., a user query) executed in an LLM application. It is identified by a globally unique ID and organizes all Spans generated during the request into a tree structure with hierarchical and temporal relationships. In short, it may include a series of Spans such as "Receive request > Query database > Call LLM > Return result". |
View Modes¶
Based on lists and charts, the LLM Explorer provides various professional analysis views.
Displays the latest metrics data of all Traces or Spans under a specific application in the current workspace, including input, output, total tokens, duration, etc.
Filters data under by conditions based on count, last, first, count_distinct operation modes:
- Top List
- Time Series
- Pie Chart
- Treemap
- Grouped Table Chart
Details Page¶
On the details page, the left side displays a single Span and Trace generated by the application, while the right side shows the corresponding preview and attribute information.
Related Operations¶
- Search and locate based on the node name
source; - Choose whether to display metrics and scores.
What are metrics and scores?
- Metrics:
durationtime display - Scores: Model quality evaluation scores, descriptions, etc.
Preview¶
Includes node type, node name, execution duration, token consumption, execution status, and execution details.
Status Display¶
Execution Status (status) |
Possible Causes |
|---|---|
| Success: Success | |
| Failure: Error | LLM call timeout, tool return exception, etc. |
| Warning: Warning | Output content triggers sensitive word detection but does not interrupt execution, etc. |
Execution Details¶
Displays the Input and Output in the LLM application. The former contains all elements used to construct the final request sent to the model, while the latter shows the results generated based on the input.
Attribute Information¶
Relevant field information contained in the current Span or Trace.