Log agent events for observability and security analysis
user - Input from human usersmodel_input - Data sent to the LLMmodel_output - Responses from the LLMtool - Tool/function calls and resultsenvironment - External system interactionsmemory - Memory read/write operationssystem - System-level eventserror - Error conditions and failures/register-agent-run. This links the event to a specific agent session.Example: "f4f4f4f4-f4f4-f4f4-f4f4-f4f4f4f4f4f4"1678886405.123schema field.Example: "{\"location\":\"London, UK\",\"units\":\"celsius\"}"content field. This enables dynamic validation and understanding of diverse event types.Example: "{\"type\":\"object\",\"properties\":{\"location\":{\"type\":\"string\"},\"units\":{\"type\":\"string\"}}}""e1e1e1e1-e1e1-e1e1-e1e1-e1e1e1e1e1e1"1678886405.456Log Events Immediately
Include Rich Context
Use Detailed Schemas
Handle Errors in Events
Asynchronous Logging
Can I log events out of order?
What happens if schema validation fails?
How detailed should schemas be?
Is there a limit on events per session?