Audit logs
This page describes what activity Zingle records.
What is recorded today
- Application logs. The services write operational logs (requests, jobs, and errors) to rotating log files, retained for a configurable period (currently 30 days by default). In a Customer VPC deployment, these logs stay in your environment.
- Pull-request history. Pull requests created from a session are retained so the origin of each change is traceable.
- Session history. Studio sessions retain their message history, including the SQL that was generated and run.
- User feedback actions. Explicit user actions on generated changes (such as accepting or reverting) are captured to improve agent behavior.
Traceability of changes
Because every change to your project is made through your Git provider as a pull request attributed to the user who initiated it, your Git provider's own history is an authoritative record of what changed, when, and by whom.
Current limitation
No dedicated audit trail yet
Zingle does not currently provide a dedicated, queryable user-action audit log (a security audit trail of every action across the platform). The records above (application logs, PR history, session history) provide traceability, but a purpose-built audit-log feature is not yet available.