Fact event field reference
This topic is intended for users who need to write custom queries, understand the audit data structure, or integrate with external analysis systems. It describes the fields and common values of the application-side event tables agent-event / agent-event-webtracking and the runtime event table ebpf-event.
All sample values in this topic are anonymized, synthetic, or documentation placeholders that illustrate field forms and data semantics. They do not represent real user data. Sensitive values in actual events may be anonymized, truncated, or summarized on the collection side.
Table overview
Audit fact events form the data foundation of the audit module. They record raw behavioral events during AI Agent execution, including model requests and responses, tool calls and results, session lifecycle, and runtime observation data. Risk detection, audit fact browsing, entity investigation, and token analysis all work based on these event tables.
|
Table |
Description |
|
|
Stores standardized events from application-side AI Agent session logs, reported by Agent applications through the server-side ingestion pipeline. |
|
|
Has an identical field contract to |
|
|
Stores observation events collected by runtime eBPF probes on AI nodes, including model calls, tool executions, process activity, file operations, and network behavior observed at the runtime layer. |
Common fields
The following fields are shared across agent-event, agent-event-webtracking, and ebpf-event.
Event identification
|
Field |
Type |
Description |
|
|
string |
Globally unique event identifier. |
|
|
string |
The event type, which indicates the behavior category described by this record. For valid values, see the Event type enumeration section of this topic. |
|
|
int64 |
The time when the event occurred, as a Unix timestamp in nanoseconds. |
Host and service
|
Field |
Type |
Description |
|
|
string |
SLS LogGroup hostname metadata. Used as the compatible hostname value when |
|
|
string |
SLS ingestion source metadata. Used as the compatible Agent host IP value when |
|
|
string |
Stable identifier of the host or execution environment. |
|
|
string |
Name of the host, pod, container, or execution environment where the Agent runs. |
|
|
string |
IP address of the host where the Agent runs. Audit result tables flatten this value into |
User and Agent identification
|
Field |
Type |
Description |
|
|
string |
Identifier of the user who initiated the request. |
|
|
string |
Agent type identifier, such as |
|
|
string |
Unique identifier of the Agent instance. |
|
|
string |
Human-readable name of the Agent instance. |
Session hierarchy
Agent events are organized in a three-level hierarchy: Session → Turn → Step. These levels represent a conversation, a round of user interaction, and a single reasoning-action cycle respectively.
|
Field |
Type |
Description |
|
|
string |
Unique session identifier corresponding to a complete Agent conversation or task. |
|
|
string |
Unique Turn identifier corresponding to the full interaction from one user input to the Agent's final response. |
|
|
boolean |
Whether this is the starting event of a Turn. Written only when the value is |
|
|
boolean |
Whether this is the ending event of a Turn. Written only when the value is |
|
|
string |
Unique Step identifier corresponding to one ReAct cycle (think → act → observe). |
Model calls
|
Field |
Type |
Description |
|
|
string |
Model service provider identifier, such as |
|
|
string |
Requested model name. |
|
|
string |
Actual model name in the response, which may differ from the requested model. |
|
|
string |
Unique identifier of the model response, returned by the model service. |
|
|
string[] |
Reasons why the model stopped generating. Common values include |
Model input and output content
|
Field |
Type |
Description |
|
|
json |
Incremental input messages that record new messages since the last reconstructable input. This is the primary input content field used in audit analysis and session browsing. |
|
|
json |
Complete message history sent to the model. This field may contain sensitive information and is collected on demand. |
|
|
json |
Model output messages, including roles, text, tool calls, and reasoning content. |
|
|
json |
System instructions or developer instructions, which are prompt content separated from conversation messages. |
|
|
json |
List of tool definitions available in the model request. |
Token usage
|
Field |
Type |
Description |
|
|
int |
Number of input tokens (including cache reads). |
|
|
int |
Number of output tokens. |
|
|
int |
Number of input tokens read from cache, already included in |
|
|
int |
Number of input tokens written to cache, already included in |
|
|
int |
Total token count, equal to |
Tool calls
|
Field |
Type |
Description |
|
|
string |
Tool name, matching the function/tool name in the model call. |
|
|
string |
Tool call identifier generated by the model, used to correlate calls with results. |
|
|
json |
Tool call arguments. This field may contain sensitive information. |
|
|
json |
Tool execution result. This field may contain sensitive information. |
|
|
int |
Tool execution duration in milliseconds. |
|
|
string |
Name of the Skill loaded by the tool (if applicable). |
Error information
|
Field |
Type |
Description |
|
|
string |
Error type identifier, written when an error occurs during the operation. This field does not exist when there is no error. |
|
|
string |
Human-readable description of the error details. |
Tracing
|
Field |
Type |
Description |
|
|
string |
W3C Trace ID (32-character hexadecimal) for distributed trace correlation. |
|
|
string |
Span ID (16-character hexadecimal). |
|
|
string |
Parent Span ID (16-character hexadecimal). |
Application-side supplementary fields
The following fields are used only in agent-event / agent-event-webtracking.
|
Field |
Type |
Description |
|
|
string |
Agent application or service name, used for filtering and attribution by application dimension. |
|
|
string |
Application name (fallback). Used as a supplement when |
Runtime supplementary fields
The following fields are used only in ebpf-event to record process, file, and network behavior observed at the runtime layer.
Event type enumeration
event.name indicates the behavior category of an event and is the most commonly used filter field in queries and analysis.
Application-side event types
Application-side event types use the gen_ai. prefix to describe the semantic behavior of an Agent.
|
event.name |
Description |
|
|
Model request. The Agent sends an inference request to the model service. |
|
|
Model response. The Agent receives an inference result from the model service. |
|
|
Tool call. The Agent executes a tool or function. |
|
|
Tool result. The tool completes execution and returns a result. |
|
|
Sub-Agent invocation. The current Agent calls another Agent. |
|
|
Sub-Agent result. The called Agent returns a result. |
Runtime event types
Runtime event types currently include only gen_ai.* events (model and tool behavior observed at the runtime layer).
|
event.name |
Description |
|
|
Model request observed at the runtime layer. |
|
|
Model response observed at the runtime layer. |
|
|
Tool call observed at the runtime layer. |
|
|
Tool result observed at the runtime layer. |
Common field examples
|
Field |
Example value |
Description |
|
|
|
The specific format is system-generated. External systems only need to use it as a stable ID. |
|
|
|
Indicates the behavior category described by the event. |
|
|
|
Nanosecond timestamp, corresponding to 2024-06-30T12:00:00Z. |
|
|
|
User identifier. The specific format depends on the integration method. |
|
|
|
Agent product type. |
|
|
|
Used to correlate all events within the same session. |
|
|
|
Model service provider. |
|
|
|
Requested model name. |
|
|
|
Name of the called tool. |
|
|
|
Tool call arguments in JSON format. |
|
|
|
Input token count for a single model request. |
|
|
|
Output token count for a single model request. |
Field usage suggestions
|
Scenario |
Recommended fields |
Description |
|
Reconstruct full session interaction |
|
Aggregate events by session and sort them by time to reconstruct the complete behavior timeline of the Agent. |
|
Analyze a single-turn interaction |
|
A Turn corresponds to one user interaction, and a Step corresponds to one reasoning-action cycle. Use them together to understand the Agent's decision chain. |
|
Token consumption statistics |
|
Calculate token usage by model provider and application dimension. |
|
Tool usage analysis |
|
Analyze tool call frequency, execution duration distribution, and failure rate. |
|
Trace back from risk events to original context |
|
High-fidelity security events reference original fact event IDs through |
|
Filter by application or host |
|
Used to aggregate or filter events by application and host dimensions respectively. |
Relationships with other audit data
|
Data |
Relationship |
|
|
Low-fidelity security findings identified from fact events by risk detection rules. They reference fact events as evidence sources. |
|
|
High-fidelity security events elevated from low-fidelity findings. They trace back to original fact events through |
|
|
Intent recognition results generated from application-side fact events by user and session. They trace back to the original user input and session through |
|
Audit facts page |
Browse and query fact events directly, with support for session browsing, token analysis, and behavior analysis. |
|
Risk audit page |
Displays and ranks high-fidelity risk and user intent results derived from fact events. |