Explorer¶
After the application is created, the system will centralize each LLM request (from input prompt to output generation) as a log event in the LLM Monitoring Explorer. You can use powerful log query methods to search, filter, and analyze Trace or Span data for a single or all applications.
| Description | |
|---|---|
| Span | Represents a single operation in the LLM application. Each call to the 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, number of Tokens consumed, etc. |
| Trace | A Trace records the complete end-to-end path of an external request (e.g., a user query) executed in the LLM application system. 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 Monitoring Explorer provides multiple 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 number of Tokens, duration, etc.
Based on count, last, first, count_distinct operation modes, filter data under by conditions:
- Top List
- Time Series
- Pie Chart
- Treemap
- Grouped Table Chart
Detail Page¶
On the detail page, the left side displays a single Span and Trace generated by the application, and the right side displays the corresponding preview and attribute information.
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 triggered sensitive word detection but did 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 displays the results generated based on the input.
Attribute Information¶
Relevant field information contained in the current Span or Trace.