Audit logging
Author: joebudiCreated Jul 28, 2026Updated Sep 14, 2026
Goal
Provide complete, privacy-conscious audit and retention controls for agent configuration, execution and knowledge.
Problem
Activity and Agent Logs (#18586 and #17647) provide execution visibility, but GA also requires governance over configuration changes, retention and deletion. Knowledge removal must delete provider-side indexed copies and stop pending processing, while audit and operational records must avoid retaining credentials or unnecessary personal data.
Solution
Define the audit events and lifecycle policies required for agents. Record configuration and protected execution activity, apply explicit retention rules, remove deleted knowledge completely and redact sensitive values throughout audit and operational records.
Potential work
- Audit agent creation and configuration changes
- Record tools used during agent runs
- Record escalations and human decisions
- Define retention for conversations, logs and test results
- Delete indexed knowledge copies when knowledge is removed
- Cancel pending knowledge sync or processing jobs
- Redact credentials and unnecessary personal data
- Verify deletion and retention behaviour across supported knowledge providers
Source: Budibase/budibase