Back to catalog / Agent observability
Use event history to trace when agent state changed
Use ordered session events and state deltas to explain agent state transitions instead of guessing from prompts.
Goal
Identify which event in an invocation wrote state, triggered a tool, or ended the run.
Steps
- Assign a searchable session ID for the test run and avoid real secrets or personal data. [session]
- Inspect ordered
Event(author=..., actions.state_delta=...)records; correlate runs by event type, author, and invocation ID. [events] - Correlate tool calls, tool results, and model events to the same run and mark state mutation points. [events]
- Create a minimal diagnostic record and remove sensitive payloads before sharing or retention. [events]
How to verify
The timeline traces input through state deltas, tool execution, and final events while preserving event order.
Troubleshooting
If state and logs disagree, inspect event append and delta application in the session service; do not edit persisted history directly.
Permissions
Prerequisites
- Python 3.11+, google-adk compatible with the pinned revision, and an isolated test environment
Permissions
- Use authorized test data only; isolate sessions and credentials per user; obtain human authorization before external side effects
Limitations
This procedure follows Google ADK at the pinned revision; other versions, models, or remote services may differ in APIs and event semantics. Recheck permissions, retention, and recovery before production.
Pinned upstream source
- Repository
- google/adk-python
- File path
- docs/guides/events/event/index.md
- Pinned commit
e9b74d36140f2594b24c481fb7a3825b2cb01e96- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Main topic
Take a coding Agent change from context to verification